index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,255
|
System
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=1
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=602 type=00 soft=0 mtu=1280 expire=1325/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=10791/10800
dec: spi=37f426a1 esp=aes key=16 3671c9303b6295fc73b11765811bdf96
ah=sha1 key=20 41b98cb541dc9c76311ddec4b23584ee35d31915
enc: spi=10aa4d3a esp=aes key=16 cc8529ee16de6e4ac42b0ce506d7cdd1
ah=sha1 key=20 0c2d9edd0fdbe45942cf718ac2ebb4d59c2760c6
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.7.2 npu_lgwy=192.168.202.35 npu_selid=1c dec_npuid=0
enc_npuid=0
c. DC2_VM3:
DC2_VM3 # diagnose vpn tunnel list
list all ipsec tunnel in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=4 192.168.202.35:0->192.168.7.2:0 tun_id=192.168.7.2 tun_
id6=::10.0.0.4 dst_mtu=0 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8712 options
[2208]=npu frag-rfc run_state=0 role=standby accept_traffic=1 overlay_id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=5 ilast=42975982 olast=42975982 ad=/0
stat: rxp=0 txp=0 rxb=0 txb=0
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=1
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=602 type=00 soft=0 mtu=1280 expire=1215/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=10791/10800
dec: spi=37f426a1 esp=aes key=16 3671c9303b6295fc73b11765811bdf96
ah=sha1 key=20 41b98cb541dc9c76311ddec4b23584ee35d31915
enc: spi=10aa4d3a esp=aes key=16 cc8529ee16de6e4ac42b0ce506d7cdd1
ah=sha1 key=20 0c2d9edd0fdbe45942cf718ac2ebb4d59c2760c6
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.7.2 npu_lgwy=192.168.202.35 npu_selid=1c dec_npuid=0
enc_npuid=0
d. DC2_VM4:
DC2_VM4 # diagnose vpn tunnel list
list all ipsec tunnel in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=4 192.168.202.35:0->192.168.7.2:0 tun_id=192.168.7.2 tun_
id6=::10.0.0.4 dst_mtu=0 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8712 options
[2208]=npu frag-rfc run_state=0 role=standby accept_traffic=1 overlay_id=0
FortiOS 7.6.2 Administration Guide 3256
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,256
|
System
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=5 ilast=42975768 olast=42975768 ad=/0
stat: rxp=0 txp=0 rxb=0 txb=0
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=1
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=602 type=00 soft=0 mtu=1280 expire=1433/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=10791/10800
dec: spi=37f426a1 esp=aes key=16 3671c9303b6295fc73b11765811bdf96
ah=sha1 key=20 41b98cb541dc9c76311ddec4b23584ee35d31915
enc: spi=10aa4d3a esp=aes key=16 cc8529ee16de6e4ac42b0ce506d7cdd1
ah=sha1 key=20 0c2d9edd0fdbe45942cf718ac2ebb4d59c2760c6
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.7.2 npu_lgwy=192.168.202.35 npu_selid=1c dec_npuid=0
enc_npuid=0
The IPsec tunnel role=sync-primaryon DC2_VM1 indicates that it is being used to carry IPsec traffic. On
DC2_VM2, DC2_VM3, and DC2_VM4, the IPsec tunnel role=standby indicates that they are in standby for
traffic forwarding.
To test failover scenarios:
1. Verify the sniffer trace on DC2_VM1 before FGCP HA failover:
DC2_VM1 # diagnose sniffer packet any icmp 4
Using Original Sniffing Mode
interfaces=[any]
filters=[icmp]
0.171753 vpn1 in 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.171763 port3 out 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.171941 port3 in 10.10.101.2 -> 10.10.1.2: icmp: echo reply
0.171947 vpn1 out 10.10.101.2 -> 10.10.1.2: icmp: echo reply
Traffic passes through DC2_VM1.
2. Reboot the primary FortiGate, DC2_VM1.
3. Verify the sniffer trace on DC2_VM2 after FGCP HA failover:
DC2_VM2 # diagnose sniffer packet any icmp 4
Using Original Sniffing Mode
interfaces=[any]
filters=[icmp]
0.111107 vpn1 in 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.111118 port3 out 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.111293 port3 in 10.10.101.2 -> 10.10.1.2: icmp: echo reply
0.111298 vpn1 out 10.10.101.2 -> 10.10.1.2: icmp: echo reply
^C
16 packets received by filter
0 packets dropped by kernel
Traffic passes through DC2_VM2.
4. Verify the tunnel list for vpn1_1 on DC2_VM2:
FortiOS 7.6.2 Administration Guide 3257
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,257
|
System
DC2_VM2 # diagnose vpn tunnel list
list all ipsec tunnel in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=4 192.168.202.35:0->192.168.7.2:0 tun_id=192.168.7.2 tun_
id6=::10.0.0.4 dst_mtu=1500 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8840 options[2288]=npu
rgwy-chg frag-rfc run_state=0 role=sync-primary accept_traffic=1 overlay_id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=5 ilast=0 olast=0 ad=/0
stat: rxp=58 txp=31 rxb=4872 txb=2604
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=169
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=3 serial=3
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=602 type=00 soft=0 mtu=1438 expire=10730/0B replaywin=2048
seqno=20 esn=0 replaywin_lastseq=0000003b qat=0 rekey=0 hash_search_len=1
life: type=01 bytes=0/0 timeout=10790/10800
dec: spi=37f426c1 esp=aes key=16 ef61b49078b6ab3e00a4d3a048d779f5
ah=sha1 key=20 ee2e8de9c522d89b6481c37faa73a7bb54163645
enc: spi=10aa4d58 esp=aes key=16 4cb95f12657ca8e269b9f8a25f9b19c1
ah=sha1 key=20 326744c4e5b4a0758397725464593d94ba9390dc
dec:pkts/bytes=116/9744, enc:pkts/bytes=62/7316
npu_flag=00 npu_rgwy=192.168.7.2 npu_lgwy=192.168.202.35 npu_selid=1e dec_npuid=0 enc_
npuid=0
The role has changed to role=sync-primary.
5. Shut down DC2_VM1 and the DC2_VM2 IPsec uplink interface.
6. Verify the sniffer trace on DC2_VM3. As expected, traffic now passes through DC2_VM3:
DC2_VM3 # diagnose sniffer packet any icmp 4
Using Original Sniffing Mode
interfaces=[any]
filters=[icmp]
0.165088 vpn1 in 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.165102 port3 out 10.10.1.2 -> 10.10.101.2: icmp: echo request
0.165294 port3 in 10.10.101.2 -> 10.10.1.2: icmp: echo reply
0.165301 vpn1 out 10.10.101.2 -> 10.10.1.2: icmp: echo reply
^C
14 packets received by filter
0 packets dropped by kernel
7. Verify the tunnel list for vpn1_1 on DC2_VM3:
DC2_VM3 # diagnose vpn tunnel list
list all ipsec tunnel in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=4 192.168.202.35:0->192.168.7.2:0 tun_id=192.168.7.2 tun_
id6=::10.0.0.4 dst_mtu=1500 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8712 options[2208]=npu
frag-rfc run_state=0 role=sync-primary accept_traffic=1 overlay_id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=5 ilast=0 olast=0 ad=/0
FortiOS 7.6.2 Administration Guide 3258
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,258
|
System
stat: rxp=53 txp=53 rxb=4452 txb=4452
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=3 serial=3
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=602 type=00 soft=0 mtu=1438 expire=10347/0B replaywin=2048
seqno=10000155 esn=0 replaywin_lastseq=000001b0 qat=0 rekey=0 hash_search_len=1
life: type=01 bytes=0/0 timeout=10790/10800
dec: spi=37f426c1 esp=aes key=16 ef61b49078b6ab3e00a4d3a048d779f5
ah=sha1 key=20 ee2e8de9c522d89b6481c37faa73a7bb54163645
enc: spi=10aa4d58 esp=aes key=16 4cb95f12657ca8e269b9f8a25f9b19c1
ah=sha1 key=20 326744c4e5b4a0758397725464593d94ba9390dc
dec:pkts/bytes=88/7392, enc:pkts/bytes=88/10384
npu_flag=00 npu_rgwy=192.168.7.2 npu_lgwy=192.168.202.35 npu_selid=1e dec_npuid=0 enc_
npuid=0
The role has changed to role=sync-primary.
Allow IPsec DPD in FGSP members to support failovers
In conjunction with support for FGSP per-tunnel failover for IPsec on page 3244, configuring DPD (dead peer detection)
on an FGSP member is permitted. This allows a failed FGSP member to send out DPD probes during failover to detect
unreachable remote peers and to flush the corresponding tunnels.
Example
In this example, using the same configuration as in FGSP per-tunnel failover for IPsec on page 3244, a tunnel can be
established from one of the remote IPsec clients to one of the FGSP members (DC1_VM1). DPD can be set to onidle, with a configured dpd-retryinterval of 60 seconds. When a client disappears, whether it is due to remote
client failures or server-side routing failures, the FGSP member or gateway (DC1_VM1) will send out DPD probes for
detection. Once the three iterations are complete and no responses are detected, the FGSP member will flush the tunnel
and remove any routing to that peer.
FortiOS 7.6.2 Administration Guide 3259
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,259
|
System
Interface/setting DC1_VM1 DC1_VM2 DC1_VM3 DC1_VM4
port2 192.168.125.254/24 192.168.126.254/24 192.168.127.254/24 192.168.128.254/24
port3 172.31.125.254/24 172.31.126.254/24 172.31.127.254/24 172.31.128.254/24
port4 172.31.1.1/24 172.31.1.2/24 172.31.1.3/24 172.31.1.4/24
lb1 192.168.202.31/32 192.168.202.31/32 192.168.202.31/32 192.168.202.31/32
fgsp-sync Enabled Enabled Enabled Disabled
To configure the FGSP peers (DC1_VM1):
The following steps are to configure DC1_VM1. The other peers have similar configurations
based on the preceding table. In the config vpn ipsec phase1-interface settings, all
peers should have the same local gateway external interface (192.168.202.31). For DC1_
VM4, fgsp-sync is disabled in the VPN tunnel phase 1 settings.
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-interface
edit "vpn1"
set type dynamic
set interface "port2"
set ike-version 2
set local-gw 192.168.202.31
set keylife 90000
set peertype one
set net-device disable
set proposal aes128-sha1
set dpd on-idle
set dhgrp 2
set fgsp-sync enable
set nattraversal disable
set peerid "Nokia_Peer"
set psksecret xxxxx
set dpd-retryinterval 60
FortiOS 7.6.2 Administration Guide 3260
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,260
|
System
next
end
3. Configure the VPN tunnel phase 2 settings:
config vpn ipsec phase2-interface
edit "vpn1"
set phase1name "vpn1"
set proposal aes128-sha1
set keylifeseconds 10800
next
end
To verify the configuration:
1. Once the FGSP members establish peering with each other, verify the standalone peers on DC1_VM1:
DC1_VM1 # diagnose sys ha standalone-peers
Group=1, ID=1
Detected-peers=3
Kernel standalone-peers: num=3.
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: send=0, recv=0
packet-type: send=0, recv=0
Kernel standalone dev_base:
standalone_id=0:
standalone_id=1:
phyindex=0: mac=00:0c:29:22:00:6b, linkfail=1
phyindex=1: mac=00:0c:29:22:00:75, linkfail=1
phyindex=2: mac=00:0c:29:22:00:7f, linkfail=1
phyindex=3: mac=00:0c:29:22:00:89, linkfail=1
phyindex=4: mac=00:0c:29:22:00:93, linkfail=1
phyindex=5: mac=00:0c:29:22:00:9d, linkfail=1
phyindex=6: mac=00:0c:29:22:00:a7, linkfail=1
phyindex=7: mac=00:0c:29:22:00:b1, linkfail=1
phyindex=8: mac=00:0c:29:22:00:bb, linkfail=1
phyindex=9: mac=00:0c:29:22:00:c5, linkfail=1
standalone_id=2:
phyindex=0: mac=00:0c:29:06:4e:d6, linkfail=1
phyindex=1: mac=00:0c:29:06:4e:e0, linkfail=1
phyindex=2: mac=00:0c:29:06:4e:ea, linkfail=1
phyindex=3: mac=00:0c:29:06:4e:f4, linkfail=1
phyindex=4: mac=00:0c:29:06:4e:fe, linkfail=1
phyindex=5: mac=00:0c:29:06:4e:08, linkfail=1
phyindex=6: mac=00:0c:29:06:4e:12, linkfail=1
phyindex=7: mac=00:0c:29:06:4e:1c, linkfail=1
phyindex=8: mac=00:0c:29:06:4e:26, linkfail=1
phyindex=9: mac=00:0c:29:06:4e:30, linkfail=1
standalone_id=3:
phyindex=0: mac=00:0c:29:70:b9:6c, linkfail=1
phyindex=1: mac=00:0c:29:70:b9:76, linkfail=1
FortiOS 7.6.2 Administration Guide 3261
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,261
|
System
phyindex=2: mac=00:0c:29:70:b9:80, linkfail=1
phyindex=3: mac=00:0c:29:70:b9:8a, linkfail=1
phyindex=4: mac=00:0c:29:70:b9:94, linkfail=1
phyindex=5: mac=00:0c:29:70:b9:9e, linkfail=1
phyindex=6: mac=00:0c:29:70:b9:a8, linkfail=1
phyindex=7: mac=00:0c:29:70:b9:b2, linkfail=1
phyindex=8: mac=00:0c:29:70:b9:bc, linkfail=1
phyindex=9: mac=00:0c:29:70:b9:c6, linkfail=1
standalone_id=4:
phyindex=0: mac=00:0c:29:5c:d3:23, linkfail=1
phyindex=1: mac=00:0c:29:5c:d3:2d, linkfail=1
phyindex=2: mac=00:0c:29:5c:d3:37, linkfail=1
phyindex=3: mac=00:0c:29:5c:d3:41, linkfail=1
phyindex=4: mac=00:0c:29:5c:d3:4b, linkfail=1
phyindex=5: mac=00:0c:29:5c:d3:55, linkfail=1
phyindex=6: mac=00:0c:29:5c:d3:5f, linkfail=1
phyindex=7: mac=00:0c:29:5c:d3:69, linkfail=1
phyindex=8: mac=00:0c:29:5c:d3:73, linkfail=1
phyindex=9: mac=00:0c:29:5c:d3:7d, linkfail=1
standalone_id=5:
...
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.
a. DC1_VM1:
DC1_VM1 # diagnose vpn tunnel list name vpn1_1
list ipsec tunnel by names in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=a4 192.168.202.31:0->192.168.1.2:0 tun_id=192.168.1.2 tun_
id6=::10.0.0.15 dst_mtu=1500 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8840 options
[2288]=npu rgwy-chg frag-rfc run_state=0 role=sync-primary accept_traffic=1 overlay_
id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=6 ilast=6 olast=6 ad=/0
stat: rxp=0 txp=0 rxb=0 txb=0
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=20
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=3 add-route
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=682 type=00 soft=0 mtu=1438 expire=10480/0B replaywin=2048
seqno=1 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 7e65d641be6bc52655619ff542c67c61713de523
enc: spi=10aa45b0 esp=aes key=16 65ad3b4849386deb4f3028079a657257
ah=sha1 key=20 b5f1e1c6786f69482b5d271347a69a0cbb83ed58
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.1.2 npu_lgwy=192.168.202.31 npu_selid=b2 dec_npuid=0
enc_npuid=0
FortiOS 7.6.2 Administration Guide 3262
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,262
|
System
b. DC1_VM2:
DC1_VM2 # diagnose vpn tunnel list name vpn1_1
list ipsec tunnel by names in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=a3 192.168.202.31:0->192.168.1.2:0 tun_id=192.168.1.2 tun_
id6=::10.0.0.15 dst_mtu=0 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8712 options
[2208]=npu frag-rfc run_state=0 role=standby accept_traffic=1 overlay_id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=6 ilast=43063501 olast=43063501 ad=/0
stat: rxp=0 txp=0 rxb=0 txb=0
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=3 add-route
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
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 7e65d641be6bc52655619ff542c67c61713de523
enc: spi=10aa45b0 esp=aes key=16 65ad3b4849386deb4f3028079a657257
ah=sha1 key=20 b5f1e1c6786f69482b5d271347a69a0cbb83ed58
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.1.2 npu_lgwy=192.168.202.31 npu_selid=ab dec_npuid=0
enc_npuid=0
c. DC1_VM3:
DC1_VM3 # diagnose vpn tunnel list name vpn1_1
list ipsec tunnel by names in vd 0
------------------------------------------------------
name=vpn1_1 ver=2 serial=ac 192.168.202.31:0->192.168.1.2:0 tun_id=192.168.1.2 tun_
id6=::10.0.0.15 dst_mtu=0 dpd-link=on weight=1
bound_if=6 lgwy=static/1 tun=intf/0 mode=dial_inst/3 encap=none/8712 options
[2208]=npu frag-rfc run_state=0 role=standby accept_traffic=1 overlay_id=0
parent=vpn1 index=1
proxyid_num=1 child_num=0 refcnt=6 ilast=43063499 olast=43063499 ad=/0
stat: rxp=0 txp=0 rxb=0 txb=0
dpd: mode=on-idle on=1 idle=60000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=vpn1 proto=0 sa=1 ref=2 serial=2 add-route
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:10.10.1.0-10.10.1.255:0
SA: ref=3 options=682 type=00 soft=0 mtu=1280 expire=10462/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 7e65d641be6bc52655619ff542c67c61713de523
enc: spi=10aa45b0 esp=aes key=16 65ad3b4849386deb4f3028079a657257
FortiOS 7.6.2 Administration Guide 3263
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,263
|
System
ah=sha1 key=20 b5f1e1c6786f69482b5d271347a69a0cbb83ed58
dec:pkts/bytes=0/0, enc:pkts/bytes=0/0
npu_flag=00 npu_rgwy=192.168.1.2 npu_lgwy=192.168.202.31 npu_selid=b4 dec_npuid=0
enc_npuid=0
4. When a shut down occurs on the VPN client to vpn1_2, verify the IKE debug messages on DC1_VM2. There are
three iterations of DPD probes:
DC1_VM2 # diagnose debug enable
DC1_VM2 # diagnose debug application ike -1
...
ike 0:vpn1_2: link is idle 6 192.168.202.31->192.168.4.2:0 dpd=1 seqno=72 rr=0
ike 0:vpn1_2:171: send IKEv2 DPD probe, seqno 114
ike 0:vpn1_2:158: sending NOTIFY msg
ike 0:vpn1_2:171:158: send informational
ike 0:vpn1_2:171: sent IKE msg (INFORMATIONAL): 192.168.202.31:500->192.168.4.2:500,
len=76, vrf=0, id=87458c81a3be17f9/c8db7d3f2c70e638:00000004
ike 0: comes 192.168.1.2:500->192.168.202.31:500,ifindex=6,vrf=0...
ike 0:vpn1_2: link is idle 6 192.168.202.31->192.168.4.2:0 dpd=1 seqno=72 rr=0
ike 0:vpn1_2:171: send IKEv2 DPD probe, seqno 114
ike 0:vpn1_2:158: sending NOTIFY msg
ike 0:vpn1_2:171:158: send informational
ike 0:vpn1_2:171: sent IKE msg (INFORMATIONAL): 192.168.202.31:500->192.168.4.2:500,
len=76, vrf=0, id=87458c81a3be17f9/c8db7d3f2c70e638:00000004
ike 0: comes 192.168.1.2:500->192.168.202.31:500,ifindex=6,vrf=0....
ike 0:vpn1_2: link is idle 6 192.168.202.31->192.168.4.2:0 dpd=1 seqno=72 rr=0
ike 0:vpn1_2:171: send IKEv2 DPD probe, seqno 114
ike 0: comes 192.168.1.2:500->192.168.202.31:500,ifindex=6,vrf=0....
ike 0:vpn1_2:171: 87458c81a3be17f9/c8db7d3f2c70e638 negotiation of IKE SA failed due to
retry timeout
ike 0:vpn1_2:171: expiring IKE SA 87458c81a3be17f9/c8db7d3f2c70e638
ike 0:vpn1_2: deleting
ike 0:vpn1_2: flushing
ike 0:vpn1_2: deleting IPsec SA with SPI 85700354
ike 0:vpn1_2:vpn1: deleted IPsec SA with SPI 85700354, SA count: 0
ike 0:vpn1_2: sending SNMP tunnel DOWN trap for vpn1
ike 0:vpn1_2: sending tunnel down event for addr 10.10.4.0
ike 0:vpn1_2:vpn1: delete
ike 0:vpn1:152: del route 10.10.4.0/255.255.255.0 tunnel 192.168.4.2 oif vpn1(21) metric
15 priority 1
ike 0:vpn1_2: flushed
ike 0:vpn1_2:171: HA send IKE SA del 87458c81a3be17f9/c8db7d3f2c70e638
ike 0:vpn1_2:171:159: send informational
ike 0:vpn1_2:171: sent IKE msg (INFORMATIONAL): 192.168.202.31:500->192.168.4.2:500,
len=76, vrf=0, id=87458c81a3be17f9/c8db7d3f2c70e638:00000005
ike 0:vpn1_2: delete dynamic
ike 0:vpn1_2: deleted
Standalone configuration synchronization
You can configure synchronization from one standalone FortiGate to another standalone FortiGate (standaloneconfig-sync). With the exception of some configurations that do not sync (settings that identify the FortiGate to the
network), the rest of the configurations are synced, such as firewall policies, firewall addresses, and UTM profiles.
FortiOS 7.6.2 Administration Guide 3264
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,264
|
System
This option is useful in situations when you need to set up FGSP peers, or when you want to quickly deploy several
FortiGates with the same configurations. You can set up standalone-config-sync for multiple members.
standalone-config-sync is an independent feature and should be used with caution as
there are some limitations. We recommend disabling it once the configurations have been
synced over.
Limitations
When standalone configuration synchronization is enabled, there are some limitations, including but not limited to the
following:
l Network interruptions occur during firmware upgrades: when upgrading the firmware, all members in the
standalone-config-sync group are upgraded simultaneously. This creates downtime if the FortiGates are the
only outgoing gateway in the network. We recommend disabling the option before upgrading firmware.
l Some unwanted configurations might be synced: the current design and implementation of standalone-configsync is based on requirements from specific customers. Thus, some users may find that unwanted parts of the
configurations are synced. Should this occur, we recommend disabling the option and modifying those
configurations manually.
l The wrong primary device might be selected accidentally: standalone-config-sync is derived from the HA
primary unit selection mechanism. All members in the group will join the selection process in the same way as a the
HA cluster selection process. It is important to select the correct device as the primary, otherwise the wrong device
could be selected and existing configurations could be overwritten.
Setting up standalone configuration synchronization
Two or more standalone FortiGates should be connected to each other with one or more heartbeat interfaces, either
back-to-back or via a switch. In the following example, the device supplying the configurations is called "conf-prim," and
the devices receiving the configurations are called "conf-secos."
To set up standalone configuration synchronization:
1. Configure the conf-prim device for the group:
config system ha
set password **********
set hbdev ha1 50 ha2 100
set priority 255
set override enable
set standalone-config-sync enable
end
2. Configure the conf-prim device as needed to be functional.
3. Configure the other group members as conf-secos:
config system ha
set password **********
set standalone-config-sync enable
end
FortiOS 7.6.2 Administration Guide 3265
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,265
|
System
4. Wait 10–15 minutes for the configurations to sync over.
5. Verify the synchronization status:
# get system ha status
path=system, objname=ha, tablename=(null), size=5912
HA Health Status:
WARNING: FG201E4Q17900771 has hbdev down;
WARNING: FG201ETK19900991 has hbdev down;
Model: FortiGate-201E
Mode: ConfigSync
Group Name:
Group ID: 0
Debug: 0
Cluster Uptime: 0 days 0:0:51
Cluster state change time: 2019-09-03 17:46:07
Primary selected using:
<2019/09/03 17:46:07> FG201ETK19900991 is selected as the primary because it has the
largest value of override priority.
ses_pickup: disable
override: disable
Configuration Status:
FG201E4Q17900771(updated 3 seconds ago): out-of-sync
FG201ETK19900991(updated 1 seconds ago): in-sync
System Usage stats:
FG201E4Q17900771(updated 3 seconds ago):
sessions=1, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=16%
FG201ETK19900991(updated 1 seconds ago):
sessions=1, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=16%
HBDEV stats:
FG201E4Q17900771(updated 3 seconds ago):
wan2: physical/1000auto, up, rx-bytes/packets/dropped/errors=114918/266/0/0,
tx=76752/178/0/0
ha: physical/00, down, rx-bytes/packets/dropped/errors=0/0/0/0, tx=0/0/0/0
FG201ETK19900991(updated 1 seconds ago):
wan2: physical/1000auto, up, rx-bytes/packets/dropped/errors=83024/192/0/0,
tx=120216/278/0/0
ha: physical/00, down, rx-bytes/packets/dropped/errors=0/0/0/0, tx=0/0/0/0
Secondary: FortiGate-201E, FG201E4Q17900771, HA cluster index = 1
Primary: FortiGate-201E, FG201ETK19900991, HA cluster index = 0
number of vcluster: 1
vcluster 1: work 169.254.0.1
Secondary: FG201E4Q17900771, HA operating index = 1
Primary: FG201ETK19900991, HA operating index = 0
If all members are in-sync, this means all members share the same configurations, except those that should not
be synced. If any members are out-of-sync, this means the member failed to sync with the primary device.
Debugging is similar when a cluster is out of sync.
The following topic provides more information about standalone configuration synchronization:
l Layer 3 unicast standalone configuration synchronization on page 3267
FortiOS 7.6.2 Administration Guide 3266
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,266
|
System
Layer 3 unicast standalone configuration synchronization
Unicast standalone configuration synchronization is supported on layer 3, allowing peers to be synchronized in cloud
environments that do not support layer 2 networking. Configuring a unicast gateway allows peers to be in different
subnets.
Example
In this example, two FortiGates in different subnets are connected through a unicast gateway. Both cluster members use
the same port for the heartbeat interface.
To configure unicast synchronization between peers:
1. Configure FortiGate A:
config system ha
set group-name "testcs"
set password **********
set hbdev "port3" 50
set standalone-config-sync enable
set unicast-status enable
config unicast-peers
edit 1
set peer-ip 10.1.100.72
next
end
set override enable
set priority 200
set unicast-gateway 172.16.200.74
end
2. Configure FortiGate B:
config system ha
set group-name "testcs"
set password **********
set hbdev "port3" 50
set standalone-config-sync enable
set unicast-status enable
config unicast-peers
edit 1
set peer-ip 172.16.200.71
next
end
set override enable
set priority 100
set unicast-gateway 10.1.100.74
end
3. Check the HA status on FortiGate A:
FortiOS 7.6.2 Administration Guide 3267
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,267
|
System
# get system ha status
HA Health Status: OK
Model: FortiGate-VM64
Mode: ConfigSync
Group Name: testcs
Group ID: 0
Debug: 0
Cluster Uptime: 2 days 3:40:25
Cluster state change time: 2021-03-08 12:00:38
Primary selected using:
<2021/03/08 12:00:38> FGVMSLTM00000001 is selected as the primary because its
override priority is larger than peer member FGVMSLTM00000002.
<2021/03/06 11:50:35> FGVMSLTM00000001 is selected as the primary because it's the
only member in the cluster.
ses_pickup: disable
override: enable
Configuration Status:
FGVMSLTM21000151(updated 5 seconds ago): in-sync
FGVMSLTM21000152(updated 5 seconds ago): in-sync
System Usage stats:
FGVMSLTM21000151(updated 5 seconds ago):
sessions=7, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=24%
FGVMSLTM21000152(updated 5 seconds ago):
sessions=5, average-cpu-user/nice/system/idle=0%/0%/0%/100%, memory=23%
HBDEV stats:
FGVMSLTM21000151(updated 5 seconds ago):
port3: physical/1000auto, up, rxbytes/packets/dropped/errors=466060007/1049137/0/0, tx=429538329/953028/0/0
FGVMSLTM21000152(updated 5 seconds ago):
port3: physical/1000auto, up, rxbytes/packets/dropped/errors=48805199/85441/0/0, tx=33470286/81425/0/0
Primary : FGT-71 , FGVMSLTM00000001, HA cluster index = 1
Secondary : FGT-72 , FGVMSLTM00000002, HA cluster index = 0
number of vcluster: 1
vcluster 1: work 0.0.0.0
Primary: FGVMSLTM00000001, HA operating index = 0
Secondary: FGVMSLTM00000002, HA operating index = 1
4. Check the HA checksums on FortiGate A:
# diagnose sys ha checksum cluster
================== FGVMSLTM00000001 ==================
is_manage_primary()=1, is_root_primary()=1
debugzone
global: 4f 2c a2 04 07 57 46 c4 47 28 ca d2 5a c5 98 ee
root: 16 af 5d a4 ac cf a5 4b b7 22 93 ce f9 02 68 bc
all: 6e 28 7f 8a 74 f7 37 43 8f 32 73 68 1e d6 ca cd
checksum
global: 4f 2c a2 04 07 57 46 c4 47 28 ca d2 5a c5 98 ee
root: 16 af 5d a4 ac cf a5 4b b7 22 93 ce f9 02 68 bc
all: 6e 28 7f 8a 74 f7 37 43 8f 32 73 68 1e d6 ca cd
================== FGVMSLTM00000002 ==================
FortiOS 7.6.2 Administration Guide 3268
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,268
|
System
is_manage_primary()=0, is_root_primary()=1
debugzone
global: 4f 2c a2 04 07 57 46 c4 47 28 ca d2 5a c5 98 ee
root: 16 af 5d a4 ac cf a5 4b b7 22 93 ce f9 02 68 bc
all: 6e 28 7f 8a 74 f7 37 43 8f 32 73 68 1e d6 ca cd
checksum
global: 4f 2c a2 04 07 57 46 c4 47 28 ca d2 5a c5 98 ee
root: 16 af 5d a4 ac cf a5 4b b7 22 93 ce f9 02 68 bc
all: 6e 28 7f 8a 74 f7 37 43 8f 32 73 68 1e d6 ca cd
5. Verify that configuration changes on the primary FortiGate are synchronized to the secondary FortiGate:
a. Adjust the administrator timeout value on FortiGate A:
config system global
set admintimeout 100
end
b. Check the debug messages on FortiGate B:
# diagnose debug cli 7
Debug messages will be on for 30 minutes.
# diagnose debug enable
create pid=15639, clictxno=0, last=1615246288
0: conf sys global
0: set admintimeout 100
0: end
VRRP
A Virtual Router Redundancy Protocol (VRRP) configuration can be used as a high availability solution to ensure that a
network maintains connectivity with the internet (or with other networks) even if the default router for the network fails. If
a router or a FortiGate fails, all traffic to this device transparently fails over to another router or FortiGate that takes over
the role of the failed device. If the failed device is restored, it will take over processing the network traffic.
FortiOS supports VRRP versions 2 and 3. VRRP domains can be created, which can include multiple FortiGates and
other VRRP-compatible routers. Different FortiGate models can be added to the same VRRP domain.
FortiOS supports IPv4 and IPv6 VRRP, so IPv4 and IPv6 VRRP virtual routers can be added to the same interface.
FortiGates can quickly and easily integrate into a network that has already deployed VRRP.
Basic VRRP configuration
The most common VRRP application is to provide redundant default routers between an internal network and the
internet. The default routers can be FortiGates or any routers that support VRRP.
Two or more FortiGate interfaces or routers must be configured with the same virtual router ID and IP address so they
can automatically join the same VRRP domain. Priorities must be assigned to each FortiGate interface or router in the
VRRP domain. All of the routers in the VRRP domain should have different priorities. One FortiGate interface or router
must have the highest priority to become the primary router. The other FortiGates or routers in the domain are assigned
lower priorities and become backups. If the primary router fails, VRRP automatically fails over to the router in the domain
with the next highest priority.
FortiOS 7.6.2 Administration Guide 3269
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,269
|
System
To configure VRRP:
1. Add a virtual VRRP router to the internal interface of each FortiGate and/or router. This adds the FortiGates and
routers to the same VRRP domain.
2. Set the VRRP IP address of the domain to the internal network default gateway IP address.
3. Set the priorities.
See Adding IPv4 and IPv6 virtual routers to an interface on page 3270 Single-domain VRRP example on page 3277, and
Multi-domain VRRP example on page 3278 for configuration examples.
During normal operations, all traffic from the internal network to the internet passes through the primary VRRP router.
The primary router also sends VRRP advertisement messages to the backup routers. A backup router will not attempt to
become a primary router while receiving these messages. If the primary router fails, the backup router with the highest
priority becomes the new primary router after a short delay. All packets sent to the default route are now sent to the new
primary router. If the new primary router is a FortiGate, the network continues to benefit from FortiOS security features. If
the new primary router is just a router, traffic continues to flow, but FortiOS security features are unavailable until the
FortiGate is back online.
If the backup router is a FortiGate, during a VRRP failover as the FortiGate begins operating as the new primary router, it
will not have session information for all of the failed over in-progress sessions. So, it would normally not be able to
forward in-progress session traffic.
Adding IPv4 and IPv6 virtual routers to an interface
This topic describes to how to add IPv4 and IPv6 virtual routers to an interface. VRRP can only be configured on physical
or VLAN interfaces. VRRP cannot be configured on hardware switch interfaces where multiple physical interfaces are
combined into a hardware switch interface.
The hello timer for the VRRP dictates the rate at which VRRP advertisements are sent. With this enhanced control, you
can ensure quick failover and high availability where necessary.
IPv4 virtual router
In this example, an IPv4 VRRP router is added to port10 on the FortiGate. The VRRP virtual router has a virtual router ID
of 200, uses IP address 10.31.101.200, and has a priority of 255. Since this is the highest priority in the configuration,
this interface is configured to be the primary router of the VRRP domain.
To configure the interface settings:
config system interface
edit port10
config vrrp
FortiOS 7.6.2 Administration Guide 3270
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,270
|
System
edit 200
set vrip 10.31.101.200
set priority 255
set adv-interval 250
next
end
next
end
IPv6 virtual router
In this example, an IPv6 VRRP router is added to port20 on the FortiGate. The VRRP virtual router has a virtual router ID
of 220, uses IP address 2001:db8:1::12, and has a priority of 255. Since this is the highest priority in the configuration,
this interface is configured to be the primary router of the VRRP domain.
To configure the interface settings:
config system interface
edit port20
config ipv6
set vrip6_link_local <IPv6_address>
config vrrp6
edit 220
set vrip 2001:db8:1::12
set priority 255
set adv-interval 250
next
end
end
next
end
VRRP failover
VRRP routers in a VRRP domain periodically send VRRP advertisement messages to all routers in the domain to
maintain one router as the primary router and the others as backup routers. The primary router has the highest priority. If
the backup routers stop receiving these packets from the primary router, the backup router with the highest priority
becomes the new primary router.
The primary router stops sending VRRP advertisement messages if it fails or becomes disconnected. Up to two VRRP
destination addresses can be configured to be monitored by the primary router. As a best practice, the destination
addresses should be remote addresses. If the primary router is unable to connect to these destination addresses, it
stops sending VRRP advertisement messages, and the backup router with the highest priority becomes the primary
router.
To configure IPv4 VRRP with two destination addresses for monitoring:
config system interface
edit port14
config vrrp
edit 12
set vrdst 10.10.10.20 10.20.20.10
next
FortiOS 7.6.2 Administration Guide 3271
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,271
|
System
end
next
end
To configure IPv6 VRRP with one destination address for monitoring:
config system interface
edit port23
config ipv6
config vrrp6
edit 223
set vrdst 2001:db8:1::12
next
end
end
next
end
IPv4 VRRP active failover
The vrdst-priority option can be used to reduce IPv4 VRRP failover times. This option causes the primary router to
actively signal to the backup routers when the primary router cannot reach its configured destination addresses. The
primary router sends a lower priority for itself in the VRRP advertisement messages. The backup router with the highest
priority becomes the new primary router and takes over traffic processing.
In this example, the primary router is configured to have a priority of 255, so it should always become the primary router.
The vrdst-priority is set to 10. If the primary router cannot connect to the 10.10.10.1 destination address, then the
primary router informs the VRRP group that its priority is now 10.
To set the priority of the virtual router when the destination address is unreachable:
config system interface
edit port10
config vrrp
edit 12
set vrip 10.31.101.200
set priority 255
set vrdst 10.10.10.1
set vrdst-priority 10
next
end
next
end
IPv4 VIP and IP pool failover
The proxy-arp option can be used to map VIPs and IP pool address ranges to each router's VMAC (virtual MAC). After
failover, the IP or ranges configured in the VRRP settings are routed to the new primary router's VMAC. In this example,
a single IP and an address range are added for proxy ARP.
To configure the IP addresses for proxy ARP:
config system interface
edit port5
FortiOS 7.6.2 Administration Guide 3272
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,272
|
System
set vrrp-virtual-mac enable
config vrrp
edit 1
config proxy-arp
edit 1
set ip 192.168.62.100-192.168.62.200
next
edit 2
set ip 192.168.62.225
next
end
next
end
next
end
Changing the advertisement message interval
By default, VRRP advertisement messages are sent once every second. The frequency can be changed with the advinterval option to change the frequency of sending these messages (1 - 255 seconds).
The adv-interval also affects the period of time that a backup VRRP router waits before assuming the primary router
has failed. The waiting period is three times the adv-interval. For example, if the adv-interval is set to 5, then the
backup router waits for up to 15 seconds to receive a VRRP advertisement from the current primary router before taking
over the role as the primary router.
To configure IPv4 VRRP to send advertisement messages every 10 seconds:
config system interface
edit port14
config vrrp
edit 12
set adv-interval 10
next
end
next
end
To configure IPv6 VRRP to send advertisement messages every 20 seconds:
config system interface
edit port23
config ipv6
config vrrp6
edit 223
set adv-interval 20
next
end
next
end
Changing the VRRP startup time
The VRRP startup time is the time a backup or primary VRRP router waits before sending or receiving VRRP
advertisements before potentially changing state (start-time in seconds, 1 - 255, default = 3). This timer is mainly
FortiOS 7.6.2 Administration Guide 3273
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,273
|
System
visible when VRRP-monitored interfaces become up after previously been down. When this occurs, the device will wait
for the time period before considering, and potentially changing its status.
There are some instances when the advertisement messages might be delayed. For example, some switches with
spanning tree enabled may delay some of the advertisement message packets. If backup routers are attempting to
become primary routers even though the primary router has not failed, extend the start time to ensure that the backup
routers wait long enough for the advertisement messages.
To configure the IPv4 VRRP startup time to 10 seconds:
config system interface
edit port14
config vrrp
edit 12
set start-time 10
next
end
next
end
To configure the IPv6 VRRP startup time to 15 seconds:
config system interface
edit port23
config ipv6
config vrrp6
edit 223
set start-time 15
next
end
next
end
VRRP groups
If VRRP routers are added to multiple interfaces of the same FortiGate, each router will be in a different VRRP domain. If
one of the VRRP routers fails, it is useful if all of the VRRP routers added to the FortiGate also fail.
VRRP can only check the routers' status in a single VRRP domain and cannot track the status of routers in other
domains. For multiple VRRP domains on a single FortiGate, only one can switch to being a backup, and the others
remain operating normally. Using VRRP groups resolves this issue.
All the VRRP virtual routers on the FortiGate can be added to a VRRP group. If one of the virtual routers in a VRRP
group switches to the backup, the VRRP group forces all members to switch to backups. All VRRP traffic being
processed by the FortiGate fails over to other devices in the network.
The status of the virtual routers in a VRRP group only changes when one or more of the virtual
routers in the group changes status. A VRRP group should not be used to manually change
the status of the virtual routers in the group.
FortiOS 7.6.2 Administration Guide 3274
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,274
|
System
To configure two IPv4 VRRP routers in a VRRP group:
config system interface
edit port10
config vrrp
edit 200
set vrip 10.31.101.200
set priority 255
set vrgrp 10
next
end
next
edit port20
config vrrp
edit 100
set vrip 10.23.1.223
set priority 20
set vrgrp 10
next
end
next
end
To configure two IPv6 VRRP routers in a VRRP group:
config system interface
edit port11
config ipv6
set vrip6_link_local <IPv6_address>
config vrrp6
edit 220
set vrip 2001:db8:1::12
set priority 255
set vrgrp 90
next
end
end
next
edit port12
config ipv6
set vrip6_link_local <IPv6_address>
config vrrp6
edit 220
set vrip 2001:db8:1::14
set priority 100
set vrgrp 90
next
end
end
next
end
FortiOS 7.6.2 Administration Guide 3275
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,275
|
System
VRRP virtual MACs
The VRRP virtual MAC address (or virtual router MAC address) is a shared MAC address adopted by the primary router.
If the primary router fails, the same virtual MAC address is picked up by the new primary router, allowing all devices on
the network to transparently connect to the default route using the same virtual MAC address. This feature must be
enabled on all members in a VRRP domain.
Each VRRP router has its own virtual MAC address. The last part octet is based on the VRRP router ID using the
following format:
00-00-5E-00-01-<VRID_hex>
Where <VRID_hex> is the VRRP router ID in hexadecimal format in internet standard bit-order. For more information
about virtual MAC formatting, see RFC 3768.
For example:
l If the VRRP router ID is 10, then the virtual MAC is 00-00-5E-00-01-0a.
l If the VRRP router ID is 200, then the virtual MAC is 00-00-5E-00-01-c8.
If the VRRP virtual MAC address feature is disabled (the default setting), the VRRP domain uses the MAC address of the
primary router. On a FortiGate VRRP virtual router, this is the MAC address of the FortiGate interface that the VRRP
router is added to. If the primary fails, when the new primary takes over, it sends gratuitous ARPs to associate the VRRP
router IP address with the MAC address of the new primary (or the FortiGate interface that became the new primary).
When a VRRP virtual MAC address is enabled, the new primary uses the same MAC address as the old primary.
Since devices on the LAN do not have to learn a new MAC address for a new VRRP router in the event of a failover, this
feature can improve network efficiency, especially in large and complex networks.
To enable virtual MAC addresses in IPv4 VRRP:
config system interface
edit <name>
set vrrp-virtual-mac enable
next
end
To enable virtual MAC addresses in IPv6 VRRP:
config system interface
edit <name>
config ipv6
set vrrp-virtual-mac6 enable
end
next
end
Preempt mode
When preempt mode is enabled (the default setting), a higher priority backup router can preempt a lower priority primary
router. This can happen if the primary router fails, the backup router becomes the primary router, and the failed primary
router restarts. Since the restarted router has a higher priority, if preempt mode is enabled, the restarted router replaces
FortiOS 7.6.2 Administration Guide 3276
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,276
|
System
the current primary router becoming the new primary router. If preempt mode is disabled, a restarted router that has a
higher priority would not take over as the primary router.
Based on RFC 3768 Section 5.3.4, "The priority value for the VRRP router that owns the IP
address(es) associated with the virtual router MUST be 255 (decimal). VRRP routers backing
up a virtual router MUST use priority values between 1-254 (decimal)."
Therefore, in cases where preempt mode is disabled, but the priority is set to 255, the
restarted unit will take over as the primary router.
To configure preempt mode in IPv4 VRRP:
config system interface
edit <name>
config vrrp
edit <vrid>
set preempt {enable | disable}
next
end
next
end
To configure preempt mode in IPv6 VRRP:
config system interface
edit <name>
config ipv6
config vrrp6
edit <vrid>
set preempt {enable | disable}
next
end
end
next
end
Single-domain VRRP example
This example consists of a VRRP domain with two FortiGates that connect an internal network to the internet. The
FortiGate port2 interfaces connect to the internal network, and a VRRP virtual router is added to each port2 interface
with VRRP virtual MAC addresses enabled. The internal network default route is 10.31.101.120. Each FortiGate port2
interface has an IP address that is different from the virtual router IP address. Since vrrp-virtual-mac is enabled,
upon failover, the new primary VRRP router will use the same VMAC as the previous router.
FortiOS 7.6.2 Administration Guide 3277
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,277
|
System
To configure the primary FortiGate:
config system interface
edit port2
set vrrp-virtual-mac enable
config vrrp
edit 5
set vrip 10.31.101.120
set priority 255
next
end
next
end
To configure the backup FortiGate:
config system interface
edit port2
set vrrp-virtual-mac enable
config vrrp
edit 5
set vrip 10.31.101.120
set priority 50
next
end
next
end
Multi-domain VRRP example
This example consists of two VRRP domains, and both FortiGates participate in the domains that connect an internal
network to the internet. One FortiGate is the primary router of one domain and the other FortiGate is the primary router of
the other domain. The network distributes traffic between two different default routes (10.31.101.120 and
10.31.101.130). One VRRP domain is configured with one of the default route IP addresses and the other VRRP domain
gets the other default route IP address. During normal operation, both FortiGates process traffic, and the VRRP domains
are used to load balance the traffic between the two FortiGates.
If one of the FortiGates fails, the remaining FortiGate becomes the primary router of both VRRP domains. The network
sends all traffic for both default routes to this FortiGate. The result is a configuration that (under normal operational load)
balances traffic between two FortiGates, but if one of the FortiGates fails, all traffic fails over to the FortiGate that is still
operating.
VRRP virtual MAC address are enabled on both FortiGates' port2 interfaces so that the VRRP domains use their VRRP
virtual MAC addresses.
FortiOS 7.6.2 Administration Guide 3278
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,278
|
System
Device VRRP primary VRRP backup
Virtual router IP ID Priority Virtual router IP ID Priority
FortiGate A 10.31.101.120 50 255 10.31.101.130 100 50
FortiGate B 10.31.101.130 100 255 10.31.101.120 50 50
To configure FortiGate A:
config system interface
edit port2
set vrrp-virtual-mac enable
config vrrp
edit 50
set vrip 10.31.101.120
set priority 255
next
edit 100
set vrip 10.31.101.130
set priority 50
next
end
next
end
To configure FortiGate B:
config system interface
edit port2
set vrrp-virtual-mac enable
config vrrp
edit 50
set vrip 10.31.101.120
set priority 50
next
edit 100
set vrip 10.31.101.130
set priority 255
next
end
next
end
VRRP on EMAC-VLAN interfaces
Virtual Router Redundancy Protocol (VRRP) can be configured on EMAC-VLAN interfaces.
FortiOS 7.6.2 Administration Guide 3279
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,279
|
System
To configure the interfaces:
1. Configure FortiGate A:
config system interface
edit "emac"
set vdom "root"
set ip 172.16.209.1 255.255.255.0
set allowaccess ping https ssh snmp http telnet fgfm
set type emac-vlan
set vrrp-virtual-mac enable
config vrrp
edit 1
set vrip 172.16.209.111
set priority 200
next
end
set snmp-index 61
set interface "port1"
next
end
2. Configure FortiGate B:
config system interface
edit "emac"
set vdom "root"
set ip 172.16.209.2 255.255.255.0
set allowaccess ping https ssh snmp http telnet fgfm
set type emac-vlan
set vrrp-virtual-mac enable
config vrrp
edit 1
set vrip 172.16.209.111
set priority 222
next
end
set snmp-index 32
set interface "port1"
next
end
Check the VRRP information on the FortiGates:
Because FortiGate B has a higher priority, it is the primary device and FortiGate A is the backup.
1. FortiGate A:
# get router info vrrp
Interface: emac, primary IP address: 172.16.209.1
UseVMAC: 1, SoftSW: 0, EmacVlan: 1 BrPortIdx: 0, PromiscCount: 0
HA mode: primary (0:0:1) VRRP master number: 0
VRID: 1 verion: 2
vrip: 172.16.209.111, priority: 200 (200,0), state: BACKUP
adv_interval: 1, preempt: 1, ignore_dft: 0 start_time: 3
master_adv_interval: 100, accept: 1
vrmac: 00:00:5e:00:01:01
FortiOS 7.6.2 Administration Guide 3280
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,280
|
System
vrdst:
vrgrp: 0
2. FortiGate B:
# get router info vrrp
Interface: emac, primary IP address: 172.16.209.2
UseVMAC: 1, SoftSW: 0, EmacVlan: 1 BrPortIdx: 0, PromiscCount: 1
HA mode: primary (0:0:1) VRRP master number: 1
VRID: 1 verion: 2
vrip: 172.16.209.111, priority: 222 (222,0), state: PRIMARY
adv_interval: 1, preempt: 1, ignore_dft: 0 start_time: 3
master_adv_interval: 100, accept: 1
vrmac: 00:00:5e:00:01:01
vrdst:
vrgrp: 0
Ignore VRRP default route
Administrators can choose to exclude the default route from the calculation of available routes to the IPv6 VRRP
destination, to better manage and control the VRRP states. Previously, the VRRP state would be Primary as long as
any route, including the default route, could reach the IPv6 VRRP destination.
config system interface
edit <name>
config ipv6
config vrrp6
edit <id>
set ignore-default-route {enable | disable}
next
end
end
next
end
set ignore-default-route
{enable | disable}
Set the default route to be ignored:
l enable: Ignore the default route when checking the VRRP destination.
l disable: Include the default route when checking the VRRP destination
(default).
Example
In this example, the IPv6 VRRP destination (vrdst6) is set with an IPv6 address of 2000:172:22:20::22, and
ignore-default-route is enabled for the destination. As long as non-default routes exist to the VRRP destination,
the VRRP state is Primary. When only the default route to the VRRP destination exists, the VRRP state changes to
Backup.
To ignore the default route when checking the IPv6 VRRP destination:
1. Enable the default route to be ignored for IPv6 VRRP.
The IPv6 VRRP destination (vrdst6) is set with an IPv6 address of 2000:172:22:20::22, and ignoredefault-route is enabled for the destination.
FortiOS 7.6.2 Administration Guide 3281
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,281
|
System
config system interface
edit "port2"
config ipv6
set vrrp-virtual-mac6 enable
set vrip6_link_local fe80::926c:acff:2222:2222
config vrrp6
edit 100
set vrgrp 100
set vrip6 2000:10:1:100::222
set priority 200
set vrdst6 2000:172:22:20::22
set ignore-default-route enable
next
end
end
next
end
2. Check the route for IPv6 VRRP destination.
The routing table shows an active route through port1 to the IPv6 VRRP destination of 2000:172:22:20::22.
The active route is not a default route.
# get router info6 routing-table 2000:172:22:20::22
Routing entry for 2000:172:22:20::/80
Known via "static", distance 10, metric 0
Last update 00:00:15 ago
via 2000:172:16:200::55, port1
3. Check VRRP group information for IPv6.
The VRRP state is Primary because non-default routes to the IPv6 VRRP destination exist as shown in the
previous step.
# get router info6 vrrp
Interface: port2, primary IPv6 address: 2000:10:1:100::1
link-local IPv6 address: fe80::96f3:92ff:fe15:1ecd
Virtual link-local IPv6 address: fe80::926c:acff:2222:2222
UseVMAC: 1, SoftSW: 0, EmacVlan: 0 BrPortIdx: 0, PromiscCount: 1
HA mode: primary (0:0:1)
VRT primary count: 1
VRID: 100 version: 3
vrip: 2000:10:1:100::222, priority: 200, state: PRIMARY
adv_interval: 1, preempt: 1, ignore_dft: 0, start_time: 3
primary_adv_interval: 100, accept: 1
vrmac: 00:00:5e:00:02:64
vrdst: 2000:172:22:20::22
vrgrp: 100
4. Delete the non-default routes to the IPv6 VRRP destination (vrdst6), and check the routes again.
The routing table shows only the default route (::/0) is available to the IPv6 VRRP destination of
2000:172:22:20::22.
# get router info6 routing-table 2000:172:22:20::22
Routing entry for ::/0
Known via "static", distance 10, metric 0, best
Last update 02:02:09 ago
* via 2000:172:16:200::254, port1
FortiOS 7.6.2 Administration Guide 3282
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,282
|
System
5. Check VRRP group information for IPv6.
The VRRP state is Backup because only the default route is available to the IPv6 VRRP destination as shown in the
previous step.
#get router info6 vrrp
Interface: port2, primary IPv6 address: 2000:10:1:100::1
link-local IPv6 address: fe80::96f3:92ff:fe15:1ecd
Virtual link-local IPv6 address: fe80::926c:acff:2222:2222
UseVMAC: 1, SoftSW: 0, EmacVlan: 0 BrPortIdx: 0, PromiscCount: 0
HA mode: primary (0:0:1)
VRT primary count: 0
VRID: 100 version: 3
vrip: 2000:10:1:100::222, priority: 0, state: BACKUP
adv_interval: 1, preempt: 1, ignore_dft: 1, start_time: 3 but
primary_adv_interval: 100, accept: 1
vrmac: 00:00:5e:00:02:64
vrdst: 2000:172:22:20::22
vrgrp: 100
Session failover
Session failover means that after the primary unit fails, communications sessions resume on the new primary unit with
minimal or no interruption. Two categories of sessions need to be resumed after a failover:
l Sessions passing through the cluster
l Sessions terminated by the cluster
Session failover (also called session-pickup) is not enabled by default for FortiGate. See Session pickup on page 3283
for more information
Using the session-sync-dev option, you can select one or more FortiGate interfaces to use for synchronizing
sessions as required for session pickup. See Improving session sync performance on page 3288 for more information.
After a failover the new primary unit recognizes open sessions that were being handled by the cluster. The sessions
continue to be processed by the new primary unit and are handled according to their last known state.
Session-pickup has some limitations. For example, session failover is not supported for
sessions being scanned by proxy-based security profiles. Session failover is supported for
sessions being scanned by flow-based security profiles; however, flow-based sessions that
fail over are not inspected after they fail over. For more limitations, see Pass-through sessions
on page 3285.
Sessions terminated by the cluster do not failover and have to be restarted. There are some exceptions though,
particularly for IPsec and SSL VPN. For more information, see Terminated sessions on page 3287.
Session pickup
When session-pickup is enabled, the FGCP synchronizes the primary unit's TCP session table to all cluster units. As
soon as a new TCP session is added to the primary unit’s session table, that session is synchronized to all cluster units.
This synchronization happens as quickly as possible to ensure the session tables remain synchronized.
FortiOS 7.6.2 Administration Guide 3283
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,283
|
System
If the primary unit fails, the new primary unit uses its synchronized session table to resume all TCP sessions that were
being processed by the former primary unit, resulting in only minimal interruption. Under ideal conditions, all TCP
sessions should be resumed. However, this is not guaranteed, and under less than ideal conditions, some TCP sessions
may need to be restarted.
To enable session pickup in the GUI:
1. Go to System > HA.
2. Select the Primary FortiGate and click Edit.
3. Under Cluster Settings, enable Session pickup.
4. Click OK to save the setting.
To enable session pickup in the CLI:
config system ha
set session-pickup enable
end
Enabling UDP, ICMP and broadcast packet session failover
By default, the FGCP does not maintain a session table for UDP, ICMP, or broadcast packets, even when session
pickup is enabled. This means that the cluster does not specifically support the failover of these types of packets.
However, it is possible to enable session pickup for UDP and ICMP packets. To do this, you must first enable session
pickup for TCP sessions. After that, you can enable session pickup for connectionless sessions:
config system ha
set session-pickup enable
set session-pickup-connectionless enable
end
This configuration causes the cluster units to synchronize UDP and ICMP session tables and if a failover occurs UDP
and ICMP sessions are maintained.
Enabling multicast session failover
To configure multicast session failover, use the following command to change the multicast TTL timer to a smaller value
than the default. The recommended setting to support multicast session failover is 120 seconds (2 minutes). The default
setting is 600 seconds (10 minutes).
config system ha
set multicast-ttl 120
end
The multicast TTL timer controls how long to keep synchronized multicast routes on the backup unit, ensuring they are
present on the backup unit when it becomes the new primary unit after a failover. If you set the multicast TTL lower, the
multicast routes on the backup unit are refreshed more often, and are therefore more likely to be accurate. However
reducing this time causes route synchronization to happen more often, which could affect performance.
Disabling session pickup
If you leave session pickup disabled, the cluster doesn’t track sessions, and active sessions must be restarted or
resumed after a failover. This is usually handled by TCP/IP communications.
FortiOS 7.6.2 Administration Guide 3284
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,284
|
System
The session-pickup setting does not affect session failover for sessions terminated by the
cluster.
Disabling session pickup can reduce CPU and network bandwidth usage, especially if your cluster is mainly used for
unsynchronized traffic. However, if session pickup is not enabled, sessions won’t resume after a failover, causing a brief
interruption. Most protocols can restart sessions with minimal data loss. For instance, web users can refresh their
browsers to resume browsing, but large file downloads may need to be restarted. Some protocols may require manual
session restarts, like FTP file downloads.
Pass-through sessions
This section contains information about session failover for communication sessions passing through the cluster. In
general, if session pickup is enabled, session failover is supported for most TCP traffic.
Protocol Session failover
Most TCP sessions Supported if session-pickup is enabled. See TCP session failover on page 3286
for more information.
Multicast sessions Supported if multicast session-pickup is enabled. See Enabling multicast session
failover on page 3284 for more information.
IPv6, NAT64, and NAT66 Supported if session-pickup is enabled.
Proxy-based security profile
sessions
Not Supported; sessions have to be restarted.
Proxy-based features require the FortiGate to maintain very large amounts of
internal state information for each session. The FGCP does not synchronize this
internal state information. As a result, proxy-based sessions are not failed over.
Active-active clusters can resume some of these sessions after a failover. See
Resume active-active HA subordinate units sessions after failover on page 3286
for more information.
Flow-based security profile
sessions
Supported if session-pickup is enabled; however, internal state information is not
synchronized so flow-based sessions that fail over are not inspected after they fail
over.
If both flow-based and proxy-based security profile features are applied to a TCP
session, that session will not resume after a failover.
UDP, ICMP, or broadcast
sessions
Supported if connectionless session-pickup is enabled. See Enabling UDP, ICMP
and broadcast packet session failover on page 3284 for more information.
GPRS Tunneling Protocol
(GTP)
Supported with limitations. See FortiOS Carrier GTP session failover on page
3286 for more information.
SIP Supported for active-passive HA only. See SIP session failover on page 3286 for
more information.
SIMPLE or SCCP signal
session
Not supported; sessions have to be restarted.
SSL offloading and HTTP
multiplexing
Not supported; sessions have to be restarted. See SSL offloading and HTTP
multiplexing session failover on page 3286 for more information.
FortiOS 7.6.2 Administration Guide 3285
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,285
|
System
TCP session failover
TCP sessions that are not being processed by security profile features resume after a failover even if these sessions are
accepted by security policies with security profiles. Only TCP sessions that are actually being processed by these
security profile features do not resume after a failover.
l TCP sessions that are not virus scanned, web filtered, spam filtered, content archived, or are not SIP, SIMPLE, or
SCCP signal traffic resume after a failover, even if they are accepted by a security policy with security profile options
enabled. For example, SNMP TCP sessions through the FortiGate resume after a failover because FortiOS does
not apply any security profile options to SNMP sessions.
l TCP sessions for a protocol for which security profile features have not been enabled resume after a failover even if
they are accepted by a security policy with security profile features enabled. For example, if you have not enabled
any antivirus or content archiving settings for FTP, FTP sessions resume after a failover.
SIP session failover
If session pickup is enabled, the FGCP supports SIP session failover (also called stateful failover) for active passive HA.
SIP session failover replicates SIP states to all cluster units. If an HA failover occurs, all in-progress SIP calls (setup
complete) and their RTP flows are maintained and the calls will continue after the failover with minimal or no interruption.
SIP calls being set up at the time of a failover may lose signaling messages. In most cases the SIP clients and servers
should use message retransmission to complete the call setup after the failover has completed. As a result, SIP users
may experience a delay if their calls are being set up when an HA a failover occurs. But in most cases the call setup
should be able to continue after the failover.
FortiOS Carrier GTP session failover
FortiOS Carrier HA supports GTP session failover. Once the GTP tunnel setup is completed, the primary unit
synchronizes the GTP tunnel state across all cluster units. Although HA does not synchronize UDP sessions used by
GTP, the new primary unit retains the GTP tunnel state information after a failover. This allows GTP UDP sessions using
the same tunnel to continue to flow, albeit with certain limitations.
The limitation on packets continuing to flow is that there has to be a security policy to accept the packets. For example, if
the FortiOS Carrier unit has an internal to external security policy, GTP UDP sessions using an established tunnel that
are received by the internal interface are accepted by the security policy and can continue to flow. However, GTP UDP
packets for an established tunnel that are received at the external interface cannot flow until packets from the same
tunnel are received at the internal interface.
If you have bi-directional policies that accept GTP UDP sessions then traffic in either direction that uses an established
tunnel can continue to flow after a failover without interruption.
SSL offloading and HTTP multiplexing session failover
SSL offloading and HTTP multiplexing requires the FortiGate to maintain very large amounts of internal state information
for each session. Sessions accepted by security policies containing virtual IPs or virtual servers with SSL offloading or
HTTP multiplexing enabled do not resume after a failover.
Resume active-active HA subordinate units sessions after failover
In an active-active cluster, subordinate units process sessions. After a failover, all cluster units that are still operating
may be able to continue processing the sessions that they were processing before the failover. These sessions are
FortiOS 7.6.2 Administration Guide 3286
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,286
|
System
maintained because after the failover the new primary unit uses the HA session table to continue to send session
packets to the cluster units that were processing the sessions before the failover. Cluster units maintain their own
information about the sessions that they are processing and this information is not affected by the failover. In this way,
the cluster units that are still operating can continue processing their own sessions without loss of data.
The cluster keeps processing as many sessions as it can. But some sessions can be lost. Depending on what caused
the failover, sessions can be lost in the following ways:
l A cluster unit (subordinate unit) fails. All sessions that were being processed by that cluster unit are lost.
l A link failure occurs. All sessions that were being processed through the network interface that failed are lost.
Terminated sessions
This section contains information about session failover for communication sessions terminated by the cluster. Sessions
terminated by the cluster include management sessions as well as IPsec and SSL VPN, WAN Optimization and so on
between the cluster and a client.
In general, most sessions terminated by the cluster have to be restarted after a failover. There are some exceptions
though. For example, the FGCP provides failover for IPsec and SSL VPN sessions terminated by the cluster.
The session pickup setting does not affect session failover for sessions terminated by the
cluster. Also other cluster settings such as active-active or active-passive mode do not affect
session failover for sessions terminated by the cluster.
Protocol Session failover
Administrative or
management connections
such as connecting to the GUI
or CLI, SNMP, syslog,
communication with
FortiManager, FortiAnalyzer
and so on
Not supported, sessions have to be restarted.
Explicit web proxy, WCCP,
WAN Optimization and Web
Caching
Not supported, sessions have to be restarted. See Explicit web proxy, explicit FTP
proxy, WCCP, WAN optimization and Web Caching session failover on page
3288 for more information.
IPsec VPN tunnels terminating
at the FortiGate
Supported. Security associations (SAs) and related IPsec VPN tunnel data is
synchronized to cluster members. See IPsec VPN SA sync on page 3288 for
more information.
SSL VPN tunnels terminating
at the FortiGate
Partially supported. Sessions are not synchronized and have to be restarted.
Authentication failover and cookie failover is supported for SSL VPN web mode
sessions. Authentication failover is not supported for FortiClient SSL VPN
sessions. See SSL VPN session failover and SSL VPN authentication failover on
page 3288 for more information.
PPTP and L2TP VPN
terminating at the FortiGate
Not supported; sessions have to be restarted. See PPTP and L2TP VPN sessions
on page 3288 for more information.
FortiOS 7.6.2 Administration Guide 3287
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,287
|
System
Explicit web proxy, explicit FTP proxy, WCCP, WAN optimization and Web Caching session
failover
Explicit web proxy, explicit FTP proxy, WCCP, WAN optimization and web caching sessions all require the FortiGate to
maintain very large amounts of internal state information for each session. This information is not maintained and these
sessions do not resume after a failover.
The active-passive HA clustering is recommended for WAN optimization. All WAN optimization sessions are processed
by the primary unit only. Even if the cluster is operating in active-active mode, HA does not load-balance WAN
optimization sessions.
Web cache and byte cache databases are only stored on the primary unit. These databases are not synchronized to the
cluster. So, after a failover, the new primary unit must rebuild its web and byte caches. The new primary unit cannot
connect to a SAS partition that the failed primary unit used.
Rebuilding the byte caches can happen relatively quickly because the new primary unit gets byte cache data from the
other FortiGates that it is participating with in WAN optimization tunnels.
IPsec VPN SA sync
The FGCP synchronizes IPsec SAs between cluster members so that if a failover occurs, the cluster can resume IPsec
sessions without having to establish new SAs. The result is improved failover performance because IPsec sessions are
not interrupted to establish new SAs. Also, establishing a large number of SAs can reduce cluster performance.
SSL VPN session failover and SSL VPN authentication failover
Session failover is not supported for SSL VPN tunnels. However, authentication failover is supported for SSL VPN web
mode sessions. This means that after a failover, SSL VPN web mode sessions can re-establish the SSL VPN session
between the SSL VPN client and the FortiGate without having to authenticate again.
Authentication failover is not supported for FortiClient SSL VPN sessions.
All sessions inside the SSL VPN tunnel that were running before the failover are stopped and have to be restarted. For
example, file transfers that were in progress would have to be restarted. As well, any communication sessions with
resources behind the FortiGate that are started by an SSL VPN session have to be restarted.
To support SSL VPN cookie failover, when an SSL VPN session starts, the FGCP distributes the cookie created to
identify the SSL VPN session to all cluster units.
PPTP and L2TP VPN sessions
PPTP and L2TP VPNs are supported in HA mode. For a cluster you can configure PPTP and L2TP settings and you can
also add security policies to allow PPTP and L2TP pass through. However, the FGCP does not provide session failover
for PPTP or L2TP. After a failover, all active PPTP and L2TP sessions are lost and must be restarted.
Improving session sync performance
Two HA configuration options are available to reduce the performance impact of enabling session-pickup:
l Reducing the number of sessions that are synchronized.
l Using more FortiGate interfaces for session synchronization.
FortiOS 7.6.2 Administration Guide 3288
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,288
|
System
Reducing the number of sessions that are synchronized
When session pickup is enabled, new sessions are synced across cluster units. To reduce the number of synced
sessions, enable the session-pickup-delay option, which only syncs sessions active for more than 30 seconds.
This can reduce syncs for clusters with many short sessions, like HTTP traffic.
Use the following commands to enable a 30-second delay:
config system ha
set session-pickup-delay enable
end
This may result in more sessions not resuming after a failover, but most short sessions can restart with minor
interruption.
Using multiple FortiGate interfaces for session synchronization
The session-sync-dev option allows you to choose one or more FortiGate interfaces for session synchronization,
which is necessary for session pickup. Typically, session synchronization takes place over the HA heartbeat link.
However, with this HA option, only the chosen interfaces are used for session synchronization, not the HA heartbeat link.
If multiple interfaces are selected, the session synchronization traffic is load balanced among the selected interfaces.
Shifting session synchronization away from the HA heartbeat interface can reduce the bandwidth needed for HA
heartbeat traffic, potentially enhancing the cluster’s efficiency and performance. This is particularly true if the cluster is
synchronizing a large volume of sessions. Load balancing session synchronization across multiple interfaces can further
boost performance and efficiency when dealing with a large number of sessions.
To perform cluster session synchronization using the port10 and port12 interfaces:
config system ha
set session-sync-dev port10 port12
end
The interfaces chosen for session synchronization must be interconnected, either directly with the appropriate cable (if
the cluster only contains two units) or through switches. If one of the interfaces becomes disconnected the cluster uses
the remaining interfaces for session synchronization. If all of the session synchronization interfaces become
disconnected, session synchronization reverts back to using the HA heartbeat link. All session synchronization traffic is
between the primary unit and each subordinate unit.
Since large amounts of session synchronization traffic can increase network congestion, it is recommended to isolate
this traffic from your network by using dedicated connections.
SNMP
SNMP enables you to monitor hardware on your network. You can configure the hardware, such as the FortiGate SNMP
agent, to report system information and send traps (alarms or event messages) to SNMP managers. SNMP traps alert
you to events that happen, such as when a log disk is full or a virus is detected.
The FortiGate SNMP implementation is read-only. SNMP v1/v2c and v3 compliant SNMP managers have read-only
access to FortiGate system information through queries, and can receive trap messages from the FortiGate unit. See
SNMP Overview for more information.
FortiOS 7.6.2 Administration Guide 3289
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,289
|
System
l Basic configuration on page 3290
l MIB files on page 3293
l Access control for SNMP on page 3293
l Important SNMP traps on page 3295
l SNMP examples on page 3299
Basic configuration
SNMP configuration has four steps that should be configured in order:
1. Configure interface access
Before a remote SNMP manager can connect to the FortiGate SNMP agent, you must configure one or more
FortiGate interfaces to accept SNMP connections.
2. Configure the SNMP agent
The SNMP agent sends SNMP traps originating on the FortiGate to an external monitoring SNMP manager defined
in an SNMP community. The SNMP manager can monitor the FortiGate system to determine if it is operating
properly or if any critical events are occurring.
The description, location, and contact information for this FortiGate system will be part of the information that the
SNMP manager receives. This information is useful if the SNMP manager is monitoring many devices, and enables
faster responses when the FortiGate system requires attention.
3. Configure SNMP v1/v2c communities
An SNMP community is a grouping of equipment for network administration purposes. A single device can belong to
multiple communities. It is not mandatory if SNMP v3 is configured.
You must add an SNMP community to the FortiGate so that the SNMP manager can receive traps and system
information. Up to three communities can be added.
4. Configure SNMP v3 users
Authentication is used to ensure the identity of users. Privacy allows for the encryption of SNMP v3 messages to
ensure the confidentiality of data. These protocols provide a higher level of security than is available in SNMP
v1/v2c, which use community strings for security. Both authentication and privacy are optional.
To configure SNMP in the GUI:
1. Configure interface access:
a. Go to Network > Interfaces and edit an interface.
b. In the Administrative Access options, enable SNMP.
c. Click OK.
2. Configure the SNMP agent:
a. Go to System > SNMP.
b. Enable SNMP Agent and configure the following:
Description A description of the agent.
Location The location of the FortiGate.
Contact Info A contact or administrator for the SNMP agent or FortiGate.
c. Click Apply.
FortiOS 7.6.2 Administration Guide 3290
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,290
|
System
3. Configure an SNMP v1/v2c community:
a. Go to System > SNMP.
b. In the SNMP v1/v2c table, click Create New.
c. Configure the following:
Community Name The name of the community.
Hosts Enter the IP Address and select the Host Type for each SNMP manager.
Queries Enable or disable v1 and v2c queries, then enter the port numbers that the
SNMP managers in this community use for them.
Traps Enable or disable v1 and v2c traps, then enter the local and remote port
numbers that the SNMP managers in this community use for them.
SNMP Events Enable or disable the events that activate traps in this community.
d. Click OK.
4. Configure an SNMP v3 user:
a. Go to System > SNMP.
b. In the SNMP v3 table, click Create New.
c. Configure the following:
User Name The name of the user.
Security Level Configure the security level:
l No Authentication: No authentication or encryption.
l Authentication: Select the authentication algorithm and password.
l Authentication and Private: Select both the authentication and
encryption algorithms and password.
Hosts The IP Address for each SNMP manager.
Queries Enable or disable queries, then enter the port number that the SNMP
managers use for them.
Traps Enable or disable traps, then enter the local and remote port numbers that
the SNMP managers use for them
SNMP Events Enable or disable the events that activate traps.
d. Click OK.
To configure SNMP in the CLI:
1. Configure the Interface access:
config system interface
edit <interface>
append allowaccess snmp
config ipv6
append ip6-allowaccess snmp
end
next
end
FortiOS 7.6.2 Administration Guide 3291
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,291
|
System
2. Configure the SNMP agent:
config system snmp sysinfo
set status enable
set description <string>
set contact-info <string>
set location <string>
end
3. Configure an SNMP v1/v2c community:
config system snmp community
edit <id>
set name <string>
set status {enable | disable}
config hosts
edit <host_id>
set interface-select-method {auto | sdwan | specify}
set ip <ip/mask>
set source-ip <class_ip>
set ha-direct {enable | disable}
set host-type {any | query | trap}
next
end
set query-v1-port <port_number>
set query-v1-status {enable | disable}
set query-v2c-port <port_number>
set query-v2c-status {enable | disable}
set trap-v1-lport <port_number>
set trap-v1-rport <port_number>
set trap-v1-status {enable | disable}
set trap-v2c-lport <port_number>
set trap-v2c-rport <port_number>
set trap-v2c-status {enable | disable}
set events <events>
next
end
4. Configure an SNMP v3 user:
config system snmp user
edit <user>
set status {enable | disable}
set trap-status {enable | disable}
set trap-lport <port_number>
set trap-rport <port_number>
set queries {enable | disable}
set query-port <port_number>
set notify-hosts <class_ip> ... <class_ip>
set source-ip <class_ip>
set ha-direct {enable | disable}
set interface-select-method {auto | sdwan | specify}
set events <events>
set security-level {no-auth-no-priv | auth-no-priv | auth-priv}
set auth-proto {md5 | sha | sha224 | sha256 | sha384 | sha512}
set auth-pwd <password>
set priv-proto {aes | des | aes256 | aes256cisco}
set priv-pwd <password>
FortiOS 7.6.2 Administration Guide 3292
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,292
|
System
next
end
See SNMP examples on page 3299 for sample configurations.
MIB files
The FortiGate SNMP agent supports Fortinet proprietary MIBs, as well as the parts of RFC 2665 and RFC 1213 that
apply to FortiGate unit configuration.
Your SNMP manager may already include standard and private MIBs in a compiled database that is ready to use. You
must add the Fortinet proprietary MIBs to this database to have access to Fortinet specific information.
MIB file or RFC Description
FORTINET-CORE-MIB.mib The Fortinet core MIB includes all system configuration and trap information that
is common to all Fortinet products.
Your SNMP manager requires this information to monitor Fortinet device settings
and receive traps from the FortiGate SNMP agent.
FORTINET-FORTIGATEMIB.mib
The FortiGate MIB includes all system configuration information and trap
information that is specific to FortiGate units.
Your SNMP manager requires this information to monitor FortiGate settings and
receive traps from the FortiGate SNMP agent.
RFC-1213 (MIB II) The FortiGate SNMP agent supports MIB II groups with the following exceptions:
l No support for the EGP group from MIB II (RFC 1213, section 3.11 and 6.10).
l Protocol statistics returned for MIB II groups (IP/ICMP/TCP/UDP/etc.) do not
accurately capture all Fortinet traffic activity. More accurate information can
be obtained from the information reported by the Fortinet MIB.
RFC-2665 (Ethernet-like MIB) The FortiGate SNMP agent supports Ethernet-like MIB information.
FortiGate SNMP does not support for the dot3Tests and dot3Errors groups.
To download the MIB files:
1. Go to System > SNMP.
2. Click Download FortiGate MIB File and save the file to the management computer.
3. Click Download Fortinet Core MIB File and save the file to the management computer.
Access control for SNMP
Administrators can provide access control to SNMP users and communities based on restricting a MIB view to specific
OID subtrees. They can also define access based on the VDOM. This allows multi-tenant FortiGate deployments to
provide restricted access per VDOM.
l MIB view access control allows the SNMP clients to query specific OIDs that are filtered by the MIB view settings.
l VDOM access control allows the SNMP clients to query data from specific VDOMs that are filtered by the VDOM
settings.
FortiOS 7.6.2 Administration Guide 3293
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,293
|
System
When access control is enabled, the users can only access the information that is allowed by the access control, and all
other information is inaccessible. Administrators have granular control, and can easily restrict specific information based
on access control.
To configure MIB views:
config system snmp mib-view
edit <name>
set include <OIDs>
set exclude <OIDs>
next
end
include <OIDs> Enter the OID subtrees to be included in the view. A maximum of 16 subtrees can
be added.
exclude <OIDs> Enter the OID subtrees to be excluded in the view. A maximum of 64 subtrees can
be added.
To configure access control based on MIB views and VDOMs for SNMP users and communities:
config system snmp user
edit <user>
set mib-view <view>
set vdoms <vdoms>
next
end
config system snmp community
edit <community>
set mib-view <view>
set vdoms <vdoms>
next
end
mib-view <view> Set the SNMP access control MIB view.
vdoms <vdoms> Set the SNMP access control VDOMs.
Example
In this example, two MIB views are created and, with VDOMs, used to control access for SNMP users and communities.
To configure access control for SNMP users and communities:
1. Configure two MIB views:
config system snmp mib-view
edit "view1"
set include "1.3.6.1.2"
next
edit "view2"
set include "1.3.6.1.2.1"
FortiOS 7.6.2 Administration Guide 3294
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,294
|
System
set exclude "1.3.6.1.2.1.2.1" "1.3.6.1.2.1.4.31" "1.3.6.1.2.1.1.9.1"
next
end
2. Add the MIB view and VDOM restrictions to SNMP users:
config system snmp user
edit "v3user"
set mib-view "view1"
next
edit "v3user1"
set vdom "vdom1"
next
edit "v3user2"
set mib-view "view1"
set vdoms "root" "vdom1"
next
end
3. Add the MIB view and VDOM restrictions to SNMP communities:
config system snmp community
edit 1
set name "REGR-SYS"
set vdoms "vdom1"
next
edit 2
set name "REGR-SYS1"
set mib-view "view2"
next
edit 3
set name "REGR-SYS2"
set mib-view "view1"
set vdoms "root" "vdom1"
next
end
Important SNMP traps
Link Down and Link Up traps
This trap is sent when a FortiGate port either goes down or is brought up.
For example, the following traps are generated when the state of port34 is set to down using set status down, and
then brought up using set status up:
NET-SNMP version 5.7.3 2019-01-31 14:11:48 10.1.100.1(via UDP: [10.1.100.1]:162->
[10.1.100.11]:162) TRAP, SNMP v1, community REGR-SYS SNMPv2-MIB::snmpTraps Link Down Trap
(0) Uptime: 0:14:44.95 IF-MIB::ifIndex.42 = INTEGER: 42 IF-MIB::ifAdminStatus.42 = INTEGER:
down(2) IF-MIB::ifOperStatus.42 = INTEGER: down(2) FORTINET-CORE-MIB::fnSysSerial.0 =
STRING: FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING: FortiGate-140D-POE
2019-01-31 14:11:48 <UNKNOWN> [UDP: [10.1.100.1]:162->[10.1.100.11]:162]: DISMAN-EVENTMIB::sysUpTimeInstance = Timeticks: (88495) 0:14:44.95 SNMPv2-MIB::snmpTrapOID.0 = OID: IFMIB::linkDown IF-MIB::ifIndex.42 = INTEGER: 42 IF-MIB::ifAdminStatus.42 = INTEGER: down(2)
IF-MIB::ifOperStatus.42 = INTEGER: down(2) FORTINET-CORE-MIB::fnSysSerial.0 = STRING:
FortiOS 7.6.2 Administration Guide 3295
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,295
|
System
FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING: FortiGate-140D-POE 2019-01-31 14:12:01
10.1.100.1(via UDP: [10.1.100.1]:162->[10.1.100.11]:162) TRAP, SNMP v1, community REGR-SYS
SNMPv2-MIB::snmpTraps Link Up Trap (0) Uptime: 0:14:57.98 IF-MIB::ifIndex.42 = INTEGER: 42
IF-MIB::ifAdminStatus.42 = INTEGER: up(1) IF-MIB::ifOperStatus.42 = INTEGER: up(1) FORTINETCORE-MIB::fnSysSerial.0 = STRING: FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING:
FortiGate-140D-POE
2019-01-31 14:12:01 <UNKNOWN> [UDP: [10.1.100.1]:162->[10.1.100.11]:162]: DISMAN-EVENTMIB::sysUpTimeInstance = Timeticks: (89798) 0:14:57.98 SNMPv2-MIB::snmpTrapOID.0 = OID: IFMIB::linkUp IF-MIB::ifIndex.42 = INTEGER: 42 IF-MIB::ifAdminStatus.42 = INTEGER: up(1) IFMIB::ifOperStatus.42 = INTEGER: up(1) FORTINET-CORE-MIB::fnSysSerial.0 = STRING:
FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING: FortiGate-140D-POE
fgFmTrapIfChange trap
This trap is sent when any changes are detected on the interface. The change can be very simple, such as giving an
IPV4 address.
For example, the user has given the IP address of 1.2.3.4/24 to port 1 and the EMS Manager has detected the following
trap:
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (7975058) 22:09:10.58 SNMPv2-
MIB::snmpTrapOID.0 = OID: FORTINET-FORTIGATE-MIB::fgFmTrapIfChange FORTINET-COREMIB::fnSysSerial.0 = STRING: FG140P3G15800330 IF-MIB::ifName.45 = STRING: port1 FORTINETFORTIGATE-MIB::fgManIfIp.0 = IpAddress: 1.2.3.4 FORTINET-FORTIGATE-MIB::fgManIfMask.0 =
IpAddress: 255.255.255.0 FORTINET-FORTIGATE-MIB::fgManIfIp6.0 = STRING: 0:0:0:0:0:0:0:0
entConfigChange trap
The change to the interface in the previous example has also triggered the ConfChange Trap which is sent along with
the fgFmTrapIfChange trap:
2018-11-15 09:30:23 FGT_A [UDP: [172.16.200.1]:162->[172.16.200.55]:162]: DISMAN-EXPRESSIONMIB::sysUpTimeInstance = Timeticks: (8035097) 22:19:10.97 SNMPv2-MIB::snmpTrapOID.0 = OID:
ENTITY-MIB::entConfigChange
fgTrapDeviceNew trap
This trap is triggered when a new device, like a FortiSwitch, is connected to the FortiGate.
For example, the following scenario has given the device a new trap for adding FortiAP on a PoE interface a FortiGate
140D-POE. The trap has important information about the device name, device MAC address, and when it was last seen.
2018-11-15 11:17:43 UDP/IPv6: [2000:172:16:200::1]:162 [UDP/IPv6: [2000:172:16:200::1]:162]:
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (520817) 1:26:48.17 SNMPv2-
MIB::snmpTrapOID.0 = OID: FORTINET-FORTIGATE-MIB::fgTrapDeviceNew FORTINET-COREMIB::fnSysSerial.0 = STRING: FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING: FGT_A IFMIB::ifIndex.0 = INTEGER: 0 FORTINET-FORTIGATE-MIB::fgVdEntIndex.0 = INTEGER: 0 FORTINETFORTIGATE-MIB::fgDeviceCreated.0 = Gauge32: 5 FORTINET-FORTIGATE-MIB::fgDeviceLastSeen.0 =
Gauge32: 5 FORTINET-FORTIGATE-MIB::fgDeviceMacAddress.0 = STRING: 90:6c:ac:f9:97:a0
2018-11-15 11:17:43 FGT_A [UDP: [172.16.200.1]:162->[172.16.200.55]:162]: DISMAN-EXPRESSIONMIB::sysUpTimeInstance = Timeticks: (520817) 1:26:48.17 SNMPv2-MIB::snmpTrapOID.0 = OID:
FORTINET-FORTIGATE-MIB::fgTrapDeviceNew FORTINET-CORE-MIB::fnSysSerial.0 = STRING:
FG140P3G15800330 SNMPv2-MIB::sysName.0 = STRING: FGT_A IF-MIB::ifIndex.0 = INTEGER: 0
FortiOS 7.6.2 Administration Guide 3296
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,296
|
System
FORTINET-FORTIGATE-MIB::fgVdEntIndex.0 = INTEGER: 0 FORTINET-FORTIGATEMIB::fgDeviceCreated.0 = Gauge32: 5 FORTINET-FORTIGATE-MIB::fgDeviceLastSeen.0 = Gauge32: 5
FORTINET-FORTIGATE-MIB::fgDeviceMacAddress.0 = STRING: 90:6c:ac:f9:97:a0
fgTrapAvOversize trap
The fgTrapAvOversize trap is generated when the antivirus scanner detects an oversized file:
019-01-31 13:22:04 10.1.100.1(via UDP: [10.1.100.1]:162->[10.1.100.11]:162) TRAP, SNMP v1,
community REGR-SYS FORTINET-FORTIGATE-MIB::fgt140P Enterprise Specific Trap (602) Uptime: 1
day, 3:41:10.31 FORTINET-CORE-MIB::fnSysSerial.0 = STRING: FG140P3G15800330 SNMPv2-
MIB::sysName.0 = STRING: FortiGate-140D-POE 2019-01-31 13:22:29 <UNKNOWN> [UDP:
[10.1.100.1]:162->[10.1.100.11]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks:
(9967031) 1 day, 3:41:10.31 SNMPv2-MIB::snmpTrapOID.0 = OID: FORTINET-FORTIGATEMIB::fgTrapAvOversize FORTINET-CORE-MIB::fnSysSerial.0 = STRING: FG140P3G15800330 SNMPv2-
MIB::sysName.0 = STRING: FortiGate-140D-POE
BIOS security level trap
SNMP clients can query the BIOS security level of a FortiGate using the OID 1.3.6.1.4.1.12356.101.4.1.38.
Memory usage traps
Both free memory usage and freeable memory of FortiGate devices can be monitored through the Simple Network
Management Protocol (SNMP). SNMP object identifier (OID) entries are available in Fortinet MIB files to show the
percentage of free memory usage and freeable memory in an SNMP manager:
l 1.3.6.1.4.1.12356.101.4.1.36 .fgSysFreeMemUsage
l 1.3.6.1.4.1.12356.101.4.1.37 .fgSysFreeableMemUsage
The following commands are available to configure memory thresholds to trigger SNMP traps:
config system snmp sysinfo
set trap-free-memory-threshold <integer>
set trap-freeable-memory-threshold <integer>
end
set trap-free-memorythreshold <integer>
Use an integer from 1 to 100 (default 5) to identify what percentage of free
memory usage will trigger an SNMP trap.
SNMP traps are sent when the free memory is lower than the specified threshold.
For example, the free memory threshold is set to 5, and SNMP traps are sent
when free memory is lower than 5%.
set trap-freeable-memorythreshold <integer>
Use an integer from 1 to 100 (default 60) to identify what percentage of freeable
memory will trigger an SNMP trap.
SNMP traps are sent when the freeable memory is higher than the specified
threshold. For example, the freeable memory threshold is set to 60, and
SNMP traps are sent when freeable memory is higher than 60%.
FortiOS 7.6.2 Administration Guide 3297
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,297
|
System
Example
In this example, the SNMP agent is configured to monitor FortiGate memory and send traps. The trap-free-memorythreshold is set to 10, and the trap-freeable-memory-threshold is set to 50. SNMP traps are triggered for
both thresholds because:
l The free memory on the FortiGate is 9%, which is lower than the threshold of 10.
l The freeable memory on the FortiGate is 56%, which is higher than the threshold of 50.
To configure SNMP for monitoring memory usage on FortiGates:
1. Configure the SNMP agent to monitor FortiGate memory usage and freeable memory.
In this example, the trap-free-memory-threshold is set to 10, and the trap-freeable-memorythreshold is set to 50.
config system snmp sysinfo
set status enable
set engine-id <string for local SNMP engine ID>
set description <string>
set contact-info <string>
set location <string>
set trap-high-cpu-threshold 60
set trap-free-memory-threshold 10
set trap-freeable-memory-threshold 50
end
2. Verify that the SNMP manager can successfully query and receive a response on the current memory status of the
FortiGate.
In the following example, the free memory on the FortiGate is reported as 9%, and the freeable memory on the
FortiGate is reported as 56%.
# snmpwalk -v2c -c REGR-SYS 172.16.200.1 1.3.6.1.4.1.12356.101.4.1.36
FORTINET-FORTIGATE-MIB::fgSystemInfo.36.0 = Gauge32: 9
fosqa@pc05:~$ snmpwalk -v2c -c REGR-SYS 172.16.200.1 1.3.6.1.4.1.12356.101.4.1.37
FORTINET-FORTIGATE-MIB::fgSystemInfo.37.0 = Gauge32: 56
3. Use the SNMP manager to monitor memory usage on the FortiGate.
Following is an example of the SNMP trap messages sent when thresholds are surpassed for freeable memory and
free memory usage on FortiGates:
2023-12-08 19:53:14 172.16.200.1(via UDP: [172.16.200.1]:162->[172.16.200.55]:162) TRAP,
SNMP v1, community REGR-SYS
FORTINET-FORTIGATE-MIB::fgModel.1001 Enterprise Specific Trap (102) Uptime: 1
day, 9:49:42.35
FORTINET-CORE-MIB::fnSysSerial.0 = STRING: FG101FTK20006858 SNMPv2-
MIB::sysName.0 = STRING: FGT_A FORTINET-CORE-MIB::fnGenTrapMsg = STRING: freeable
memory percentage is too high
2023-12-08 19:56:33 <UNKNOWN> [UDP: [172.16.200.1]:162->[172.16.200.55]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (12198187) 1 day, 9:53:01.87 SNMPv2-
MIB::snmpTrapOID.0 = OID: FORTINET-CORE-MIB::fnTrapMemThreshold FORTINET-COREMIB::fnSysSerial.0 = STRING: FG101FTK20006858 SNMPv2-MIB::sysName.0 = STRING: FGT_A
FORTINET-CORE-MIB::fnGenTrapMsg = STRING: free memory percentage is too low
FortiOS 7.6.2 Administration Guide 3298
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,298
|
System
SNMP examples
This topic includes examples that incorporate several SNMP settings:
l Example 1: SNMP traps for monitoring interface status using SNMP v3 user on page 3299
l Example 2: SNMP traps and query for monitoring DHCP pool using SNMP v3 user on page 3301
l Example 3: Enabling the INDEX extension on page 3303
l Example 4: Ethernet Statistics Group on page 3305
l Example 5: Enabling non-management VDOMs to send queries using SNMP v3 on page 3306
Example 1: SNMP traps for monitoring interface status using SNMP v3 user
This configuration enables the SNMP manager (172.16.200.55) to receive notifications when a FortiGate port either
goes down or is brought up. The SNMP manager can also query the current status of the FortiGate port.
To configure SNMP for monitoring interface status in the GUI:
1. Configure interface access:
a. Go to Network > Interfaces and edit port1.
b. In the Administrative Access options, enable SNMP.
c. Click OK.
2. Configure the SNMP agent:
a. Go to System > SNMP.
b. Enable SNMP Agent and enter the following:
Description Branch
Location Burnaby
Contact Info Jane Doe
c. Click Apply.
3. Configure an SNMP v3 user:
a. Go to System > SNMP.
b. In the SNMP v3 table, click Create New.
c. Configure the following:
User Name Interface_Status
Security Level Authentication
Authentication Algorithm SHA1
Password *******
Hosts IP Address 172.16.200.55
d. Click OK.
FortiOS 7.6.2 Administration Guide 3299
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,299
|
System
To configure SNMP for monitoring interface status in the CLI:
1. Configure interface access:
config system interface
edit port1
append allowaccess snmp
next
end
2. Configure the SNMP agent:
config system snmp sysinfo
set status enable
set description Branch
set contact-info Jane Doe
set location Burnaby
end
3. Configure an SNMP v3 user:
config system snmp user
edit "Interface_Status"
set notify-hosts 172.16.200.55
set security-level auth-no-priv
set auth-proto sha
set auth-pwd ********************
next
end
Verification
1. Start the packet capture on interface port1 with the filter set to port 162. See Using the packet capture tool on page
828 for more information.
2. Turn off one of the FortiGate interface statuses to down, in this case, port2.
3. Save the packet capture.
The SNMP v3 trap is transmitted from port1 to the SNMP manager. Note that msgAuthenticationParameters
is configured, indicating that authentication is active. The absence of msgPrivacyParameters suggests that
encryption is not configured. This is further confirmed by plaintext in msgData.
FortiOS 7.6.2 Administration Guide 3300
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,300
|
System
4. Verify that the SNMP manager has received the trap. See Important SNMP traps on page 3295 for an example of a
trap.
5. Verify that the SNMP manager can successfully query and receive receive a response on the current status of the
FortiGate ports:
# snmpwalk -v3 -u Interface_Status -l authNoPriv -a SHA -A xxxxxxxx 172.16.200.1
1.3.6.1.2.1.2.2.1.8
iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
iso.3.6.1.2.1.2.2.1.8.3 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.4 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.5 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.6 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.7 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.8 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.9 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.10 = INTEGER: 1
Example 2: SNMP traps and query for monitoring DHCP pool using SNMP v3 user
This configuration enables the SNMP manager (172.16.200.55) to receive DHCP-related notifications from FortiGate.
The SNMP DHCP event contains three traps and one query.
Traps are sent when:
l DHCP server IP pool usage reaches 90%
l DHCP server detect an IP address that is already in use
l DHCP client receives DHCP NAK
SNMP queries are accepted for DHCP lease usage information (OID = 1.3.6.1.4.1.12356.101.23). The query result is
based on the leased out percentage.
To configure SNMP for monitoring DHCP pool in the GUI:
1. Configure interface access:
a. Go to Network > Interfaces and edit port1.
b. In the Administrative Access options, enable SNMP.
c. Click OK.
2. Configure the SNMP agent:
a. Go to System > SNMP.
b. Enable SNMP Agent and enter the following:
Description Branch
Location Burnaby
Contact Info Jane Doe
c. Click Apply.
3. Configure an SNMP v3 user:
FortiOS 7.6.2 Administration Guide 3301
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,301
|
System
a. Go to System > SNMP.
b. In the SNMP v3 table, click Create New.
c. Configure the following:
User Name DHCP_Status
Security Level Authentication
Authentication Algorithm SHA384
Password *******
Private Enabled
Encryption Algorithm AES256
Password *******
Hosts IP Address 172.16.200.55
d. Click OK.
To configure SNMP for monitoring the DHCP pool in the CLI:
1. Configure interface access:
config system interface
edit port1
append allowaccess snmp
next
end
2. Configure the SNMP agent:
config system snmp sysinfo
set status enable
set description Branch
set contact-info Jane Doe
set location Burnaby
end
3. Configure an SNMP v3 user:
config system snmp user
edit "DHCP_Status"
set notify-hosts 172.16.200.55
set security-level auth-priv
set auth-proto sha384
set auth-pwd ********************
set priv-proto aes256
set priv-pwd *********************
next
end
Verification
1. Start the packet capture on interface port1 with the filter set to port 162. See Using the packet capture tool on page
828 for more information.
FortiOS 7.6.2 Administration Guide 3302
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,302
|
System
2. Overload the DHCP server IP pool.
3. Save the packet capture.
The SNMP v3 trap is transmitted from port1 to the SNMP manager. Note that both
msgAuthenticationParameters and msgPrivacyParameters are set up, indicating that authentication and
encryption are active. This is further confirmed by encryptedPDU in msgData.
4. Verify that the SNMP manager has received the trap. See Important SNMP traps on page 3295 for an example of a
trap.
5. Verify that the SNMP manager can successfully query and receive DHCP lease usage information for FortiGate:
# snmpwalk -v3 -u DHCP_Status -l authPriv -a SHA384 -A xxxxxxxx -x AES256 -X xxxxxxxx
172.16.200.1 1.3.6.1.4.1.12356.101.23
iso.3.6.1.4.1.12356.101.23.1.1.0 = INTEGER: 6
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.1 = INTEGER: 0
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.2 = INTEGER: 0
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.3 = INTEGER: 0
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.4 = INTEGER: 0
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.5 = INTEGER: 0
iso.3.6.1.4.1.12356.101.23.2.1.1.2.1.6 = INTEGER: 100
Example 3: Enabling the INDEX extension
In the following example, the same IP address will be set on different ports in two VDOMs. The ipAddrTable SNMP Tree
output will then be reviewed before and after enabling the append-index command.
When the append-index command is enabled:
l VDOM and interface indexes are appended as the INDEX extension in RFC tables.
l In multi-VDOM mode, duplicated IP addresses in different VDOMs will result in multiple
entries in the RFC table.
When the append-index command is disabled:
l VDOM and interface indexes are not appended in RFC tables.
l In multi-VDOM mode, duplicated IP addresses in different VDOMs will only be presented
once in the RFC table.
To enable the INDEX extension:
1. In two different VDOMs, set the same address on two different ports.
config system interface
edit "port3"
set vdom "vdom1"
set ip 10.1.1.1 255.255.255.0
FortiOS 7.6.2 Administration Guide 3303
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,303
|
System
set type physical
set snmp-index 5
next
end
config system interface
edit "port4"
set vdom "root"
set ip 10.1.1.1 255.255.255.0
set type physical
set snmp-index 6
next
end
2. Configure the SNMP information but do not enable the INDEX extension.
config system snmp sysinfo
set status enable
set description "REGR-SYS"
end
3. On your PC, review the ipAddrTable SNMP Tree (OID 1.3.6.1.2.1.4.20). The IP address 10.1.1.1 is only displayed
once.
snmpwalk -v2c -c REGR-SYS 172.16.200.1 1.3.6.1.2.1.4.20
IP-MIB::ipAdEntAddr.10.1.1.1 = IpAddress: 10.1.1.1
IP-MIB::ipAdEntAddr.10.255.1.1 = IpAddress: 10.255.1.1
IP-MIB::ipAdEntAddr.172.16.200.1 = IpAddress: 172.16.200.1
IP-MIB::ipAdEntAddr.192.168.1.99 = IpAddress: 192.168.1.99
IP-MIB::ipAdEntIfIndex.10.1.1.1 = INTEGER: 5
IP-MIB::ipAdEntIfIndex.10.255.1.1 = INTEGER: 39
IP-MIB::ipAdEntIfIndex.172.16.200.1 = INTEGER: 3
IP-MIB::ipAdEntIfIndex.192.168.1.99 = INTEGER: 2
IP-MIB::ipAdEntNetMask.10.1.1.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.10.255.1.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.172.16.200.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.192.168.1.99 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntBcastAddr.10.1.1.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.10.255.1.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.172.16.200.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.192.168.1.99 = INTEGER: 1
IP-MIB::ipAdEntReasmMaxSize.10.1.1.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.10.255.1.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.172.16.200.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.192.168.1.99 = INTEGER: 65535
4. Enable the INDEX extension.
config system snmp sysinfo
set status enable
set description "REGR-SYS"
set append-index enable
end
5. Review the ipAddrTable SNMP Tree (OID 1.3.6.1.2.1.4.20) again. The IP address 10.1.1.1 is now displayed twice.
snmpwalk -v2c -c REGR-SYS 172.16.200.1 1.3.6.1.2.1.4.20
IP-MIB::ipAdEntAddr.10.1.1.1.1 = IpAddress: 10.1.1.1
FortiOS 7.6.2 Administration Guide 3304
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,304
|
System
IP-MIB::ipAdEntAddr.10.1.1.1.2 = IpAddress: 10.1.1.1
IP-MIB::ipAdEntAddr.10.255.1.1.1 = IpAddress: 10.255.1.1
IP-MIB::ipAdEntAddr.172.16.200.1.2 = IpAddress: 172.16.200.1
IP-MIB::ipAdEntAddr.192.168.1.99.1 = IpAddress: 192.168.1.99
IP-MIB::ipAdEntIfIndex.10.1.1.1.1 = INTEGER: 6
IP-MIB::ipAdEntIfIndex.10.1.1.1.2 = INTEGER: 5
IP-MIB::ipAdEntIfIndex.10.255.1.1.1 = INTEGER: 39
IP-MIB::ipAdEntIfIndex.172.16.200.1.2 = INTEGER: 3
IP-MIB::ipAdEntIfIndex.192.168.1.99.1 = INTEGER: 2
IP-MIB::ipAdEntNetMask.10.1.1.1.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.10.1.1.1.2 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.10.255.1.1.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.172.16.200.1.2 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntNetMask.192.168.1.99.1 = IpAddress: 255.255.255.0
IP-MIB::ipAdEntBcastAddr.10.1.1.1.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.10.1.1.1.2 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.10.255.1.1.1 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.172.16.200.1.2 = INTEGER: 1
IP-MIB::ipAdEntBcastAddr.192.168.1.99.1 = INTEGER: 1
IP-MIB::ipAdEntReasmMaxSize.10.1.1.1.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.10.1.1.1.2 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.10.255.1.1.1 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.172.16.200.1.2 = INTEGER: 65535
IP-MIB::ipAdEntReasmMaxSize.192.168.1.99.1 = INTEGER: 65535
Example 4: Ethernet Statistics Group
FortiOS supports the Ethernet Statistics Group for Remote Network Monitoring (RMON), which provides detailed
statistics about the traffic that passes through the Ethernet interface, such as drop events and collisions. This
enhancement enables comprehensive monitoring and management of network performance, helping to ensure optimal
operation and quickly identify any potential issues.
The Ethernet Statistics Group consists of the etherStatsTable .1.3.6.1.2.1.16.1.1 and can be leveraged using the
following:
config system snmp rmon-stat
edit 1
set source <data source of the Ethernet statistics entry>
set owner <owner of the Ethernet statistics entry>
next
end
To enable entries to the Ethernet Statistics Group:
1. Configure the RMON group on the FortiGate:
config system snmp rmon-stat
edit 1
set source "port2"
set owner "test"
next
end
An etherStatsEntry is created in the rmon-statistics table.
2. Query the etherStatsTable .1.3.6.1.2.1.16.1.1 on the SNMP server:
FortiOS 7.6.2 Administration Guide 3305
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,305
|
System
# snmpwalk -v2c -c REGR-SYS 172.16.200.1 etherStatsTable
RMON-MIB::etherStatsIndex.1 = INTEGER: 1
RMON-MIB::etherStatsDataSource.1 = OID: IF-MIB::ifIndex.8
RMON-MIB::etherStatsDropEvents.1 = Counter32: 0
RMON-MIB::etherStatsOctets.1 = Counter32: 39388877 Octets
RMON-MIB::etherStatsPkts.1 = Counter32: 125770 Packets
RMON-MIB::etherStatsBroadcastPkts.1 = Counter32: 0 Packets
RMON-MIB::etherStatsMulticastPkts.1 = Counter32: 84212 Packets
RMON-MIB::etherStatsCRCAlignErrors.1 = Counter32: 0 Packets
RMON-MIB::etherStatsUndersizePkts.1 = Counter32: 0 Packets
RMON-MIB::etherStatsOversizePkts.1 = Counter32: 0 Packets
RMON-MIB::etherStatsFragments.1 = Counter32: 0 Packets
RMON-MIB::etherStatsJabbers.1 = Counter32: 0 Packets
RMON-MIB::etherStatsCollisions.1 = Counter32: 0 Collisions
RMON-MIB::etherStatsPkts64Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsPkts65to127Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsPkts128to255Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsPkts256to511Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsPkts512to1023Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsPkts1024to1518Octets.1 = Counter32: 0 Packets
RMON-MIB::etherStatsOwner.1 = STRING: "test"
RMON-MIB::etherStatsStatus.1 = INTEGER: valid(1)
Example 5: Enabling non-management VDOMs to send queries using SNMP v3
Although non-management and management VDOMs can perform queries using SNMP v3, this example shows how to
enable non-management VDOMs to send queries.
PC1 connects to the port on FortiGate for the non-management VDOM, and SNMP v3 queries from non-management
VDOMs are enabled. PC5 connects to the port on FortiGate for the management VDOM. With this configuration,
SNMP queries are performed by both the non-management and the management VDOMs
To enable non-management VDOM SNMPv3 queries:
1. On FortiGate, enable non-management VDOM queries:
config system snmp sysinfo
set status enable
set engine-id-type text
set engine-id ''
set description ''
set contact-info ''
set location ''
set trap-high-cpu-threshold 80
set trap-low-memory-threshold 80
set trap-log-full-threshold 90
set trap-free-memory-threshold 5
FortiOS 7.6.2 Administration Guide 3306
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,306
|
System
set trap-freeable-memory-threshold 60
set append-index disable
set non-mgmt-vdom-query enable
end
2. Check the SNMP information:
This example uses the SNMP walk application to confirm that both management and non-management VDOMs are
performing SNMP queries to PC1 and PC5.
pc01:~$ snmpwalk -v3 -u v3user 10.1.100.1 1.3.6.1.4.1.12356.101.5.1.2.1.1.1
FORTINET-FORTIGATE-MIB::fgFwPolID.1.0 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fgFwPolID.1.1 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fgFwPolID.2.0 = INTEGER: 0
pc05~$ snmpwalk -v3 -u v3user 172.16.200.1 1.3.6.1.4.1.12356.101.5.1.2.1.1.1
FORTINET-FORTIGATE-MIB::fgFwPolID.1.0 = INTEGER: 0
FORTINET-FORTIGATE-MIB::fgFwPolID.1.1 = INTEGER: 1
FORTINET-FORTIGATE-MIB::fgFwPolID.2.0 = INTEGER: 0
Replacement messages
FortiOS has replacement messages that are HTML and text files. These messages can be customized to meet user
requirements. The content can be modified, and images can be added.
Modifying replacement messages
The Replacement Messages page has two views. Simple View (the default view) shows the most commonly used
replacement messages. Extended View shows the entire list and all replacement message categories.
To modify a replacement message in the GUI:
1. Go to System > Replacement Messages.
2. Select a replacement message and click Edit.
If the message you want to edit is not visible, click Extended View in the upper right-hand corner of the top menu.
FortiOS 7.6.2 Administration Guide 3307
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,307
|
System
3. Edit the HTML code.
The message is visible on the left alongside the HTML code on the right. The message view updates in real-time as
you edit the content.
When adding a variable to the code, right-click and select Insert Tag or type %% to view a list of the available
variables, or start typing the variable name then press Enter or TAB to auto-complete the variable name.
4. Click Save.
Click Restore Defaults to return to the original message and code base.
To modify a replacement message in the CLI:
For example, to modify the Traffic Quota Limit Exceeded Page message:
config system replacemsg traffic-quota "per-ip-shaper-block"
set buffer "<html>
<head>
<title>
FortiOS 7.6.2 Administration Guide 3308
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,308
|
System
Traffic Quota Control
</title>
</head>
<body>
<font size=2>
<table width=\"100%\">
<tr>
<td bgcolor=#3300cc align=\"center\" colspan=2>
<font color=#ffffff>
<b>
Traffic blocked because exceeded session quota
</b>
</font>
</td>
</tr>
</table>
<br>
<br>
Traffic blocked because it exceeded the per IP shaper session quota. Please contact
the system administrator.
<br>
%%QUOTA_INFO%%
<br>
<br>
<hr>
</font>
</body>
</html>"
set header http
set format html
end
Replacement message images
Images can be added to replacement messages on:
l Disclaimer pages
l Login pages
l Declined disclaimer pages
l Login failed pages
l Login challenge pages
l Keepalive pages
The supported image formats are GIF, JPEG, TIFF, and PNG. The maximum file size
supported is 24 KB.
FortiOS 7.6.2 Administration Guide 3309
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,309
|
System
Adding images to replacement messages
To add images to replacement messages in the GUI:
1. Go to System > Replacement Messages.
2. In the top menu, click Manage Images.
3. Click Create New.
4. Enter a name for the image.
5. Click Upload Image and locate the file.
6. Click OK.
The file is now visible in the list.
7. Return to the replacement message list and edit a message.
8. Right-click in the message code where you want to add the image, and select Insert Image.
9. Select the image from the list then press Enter, or double-click on the image to add it to the message.
10. Click Save.
To add images to replacement messages in the CLI:
1. Add the image to the FortiGate:
config system replacemsg-image
edit <image_name>
set image-type {gif | jpg | tiff | png}
set image-base64 <string>
next
end
2. Edit the replacement message, and include %%IMAGE:<image name>%% in the code to add the image.
FortiOS 7.6.2 Administration Guide 3310
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,310
|
System
Replacement message groups
Replacement message groups allow users to customize replacement messages for individual policies and profiles.
There are two types of replacement message groups:
Type Usage Customizable categories
utm Used with UTM settings in firewall policies. l admin
l alertmail
l custom-message
l fortiguard-wf
l ftp
l http
l icap
l mail
l nac-quar
l spam
l sslvpn
l traffic-quota
l utm
l webproxy
auth Used with authentication pages in firewall
policies.
l auth
l webproxy
The messages added to a group do not need to be customized. The message body content, header type, and format will
use the default values if not customized.
To make replacement message groups visible in the GUI:
config system global
set gui-replacement-message-groups enable
end
In the following example, two replacement message groups are created. The UTM message group includes custom
mail-related messages and is assigned to an email filter profile. The authentication message group has a custom
authentication success message that is applied to a proxy-based firewall policy that has an assigned email filter profile.
To create replacement message groups in the GUI:
1. Create the Security replacement message group:
a. Go to System > Replacement Message Groups.
b. Click Create New.
c. For Name, enter newutm.
d. In the Comments field, enter UTM message group.
e. For Group Type, select Security.
FortiOS 7.6.2 Administration Guide 3311
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,311
|
System
f. Click OK.
2. Customize the replacement messages in the newutm group:
a. Go to System > Replacement Message Groups.
b. Edit the newutm group.
c. Select the Partial Email Block Message.
d. Edit the message and click Save.
e. Select the ASE Block Message.
f. Edit the message and click Save.
3. Create the Authentication replacement message group:
a. Go to System > Replacement Message Groups.
b. Click Create New.
c. For Name, enter newauth.
d. In the Comments field, enter Authentication message group.
e. For Group Type, select Authentication.
f. Click OK.
4. Apply the newutm replacement message group to an email filter profile in the CLI:
config emailfilter profile
edit "newmsgs"
set replacemsg-group "newutm"
next
end
FortiOS 7.6.2 Administration Guide 3312
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,312
|
System
5. Apply the newauth replacement message group and the email filter profile to a firewall policy in the CLI:
config firewall policy
edit 1
...
set replacemsg-override-group "newauth"
set inspection-mode proxy
set emailfilter-profile "newmsgs"
...
next
end
To create replacement message groups in the CLI:
1. Create the replacement message groups:
config system replacemsg-group
edit "newutm"
set comment "UTM message group"
set group-type utm
config mail
edit "partial"
set buffer "Fragmented emails are blocked, sorry."
next
end
config spam
edit "smtp-spam-ase"
set buffer "This message has been blocked because ASE reports it as
spam. You\'re welcome."
next
end
next
edit "newauth"
set comment 'Authentication message group'
set group-type auth
config auth
edit "auth-success-msg"
set buffer "Welcome to the firewall. Your authentication has been
accepted, please reconnect."
next
end
next
end
2. Apply the message group to the email filter:
config emailfilter profile
edit "newmsgs"
set replacemsg-group "newutm"
next
end
3. Apply the email filter and message group to the policy:
config firewall policy
edit 1
...
set replacemsg-override-group "newauth"
FortiOS 7.6.2 Administration Guide 3313
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,313
|
System
set inspection-mode proxy
set emailfilter-profile "newmsgs"
...
next
end
FortiGuard
FortiGuard services comprise of signature packages and querying services that provide content, web and device
security. It is delivered via various types of FortiGuard servers that are part of the FortiGuard Distribution Network (FDN).
FortiGuard service subscriptions can be purchased and registered to your FortiGate unit. The FortiGate must be
connected to the Internet in order to automatically connect to the FDN to validate the license and download FDN updates
or perform real-time queries.
To view FDN support contract information, go to System > FortiGuard. The Licensed widgets show the status of your
FortiGate’s entitlements and breaks down the status of each service.
License Information widget
The service entitlements and the license statuses are listed on the System > FortiGuard > Subscriptions tab. Upon
expanding each entitlement, the corresponding definitions associated with the service are listed.
The following table list the available FortiGuard services and entitlements with a brief description.
Entitlement FortiGuard service description
Advanced Malware Protection
AI Malware Detection Model
AntiVirus Definitions
AntiVirus Engine
Mobile Malware
Outbreak Prevention
The Advanced Malware Protection service includes various engines, databases,
and definitions used in the AV profile.
In order to download updated AV definitions, at least 1 policy
with a security profile that has Antivirus scanning must be
enabled.
SeeAntivirus on page 1761 for details.
Attack Surface Security
IoT Detection Definitions
Outbreak Package
Definitions
Security Rating & CIS
Compliance
The Attack Surface Security service includes:
l Running all the built-in free and paid security rating rules
l Displaying CIS compliance information within security ratings
l IoT Detection and IoT Query
Data Loss Prevention (DLP)
Signatures
DLP Signatures
The Data Loss Prevention service offers a database of predefined DLP patterns
such as data types, dictionaries, and sensors that are used in the DLP profile.
Email Filtering Email Filtering includes spam and DNS filtering by FortiGuard.
FortiOS 7.6.2 Administration Guide 3314
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,314
|
System
Entitlement FortiGuard service description
Intrusion Prevention System
(IPS)
IPS Definitions
IPS Engine
Malicious URLs
Botnet IPs
Botnet Domains
The IPS service includes engines, databases, and definitions used in the IPS and
application control profiles.
In order to download updated IPS definitions, at least 1 policy
with a security profile that has IPS scanning must be enabled.
See Intrusion prevention on page 1960 and Application control on page 1923 for
details.
Operational Technology (OT)
Security Service
OT Threat Definitions
OT Detection Definitions
OT Virtual Patching
Signatures
The OT Security service includes OT-related threat definitions used in IPS and
application control profiles. It also includes OT Detection Definitions and Virtual
Patching Signatures used in the virtual patching profile.
URL, DNS & Video Filtering
Blocked Certificates
DNS Filtering
Video Filtering
The Web Security service includes:
l FortiGuard categories used in web filter profiles
l Malicious certificates used in SSL/SSH inspection profiles
l FortiGuard categories used in DNS filter profiles
l FortiGuard categories used in video filter profiles
SD-WAN Network Monitor SD-WAN Underlay Bandwidth and Quality Monitoring service
SD-WAN Overlay as a Service SD-WAN Overlay as a Service
FortiSASE SPA Service
Connection
SD-WAN Connector for FortiSASE Secure Private Access
FortiSASE Secure Edge
Management
Allows the FortiGate to act as the FortiSASE Secure Edge
FortiGate Cloud FortiGate Cloud management, analysis, and log retention services
FortiAnalyzer Cloud
SoCaaS
FortiAnalyzer Cloud service
The SoCaaS entitlement includes cloud-based managed log monitoring, incident
triage, and SOC escalation services.
FortiManager Cloud FortiManager Cloud service
FortiToken Cloud FortiToken Cloud service
Firmware, VM, and base
subscriptions
Application Control
Signatures
Device & OS Identification
FortiGate Virtual Patch
Signatures
The FortiCare support entitlement includes firmware and general updates that
come with various default signatures and definitions:
l Application control signatures used in application control profiles
l Device & OS identification used for device detection and asset management
l Virtual patch signatures used in local-in policies
l Inline CASB application definitions used in inline CASB profiles
l ISDB destinations that can be applied in various policies and rules
FortiOS 7.6.2 Administration Guide 3315
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,315
|
System
Entitlement FortiGuard service description
Inline-CASB Application
Definitions
Internet Service Database
Definitions
PSIRT Package Definitions
Support
FortiCloud Account
Enhanced Support
l PSIRT vulnerability definitions used in security ratings
FortiConverter Hosted Service FortiConverter service
Licenses widget
On the Dashboard > Status page, the Licenses widget lists the status of major entitlements. Licensed entitlement icons
are green, and unlicensed entitlement icons are orange.
The following topics contain more information:
l Anycast on page 3317
l Connection and OCSP stapling on page 3317
l Configuring FortiGuard updates on page 3319
l Using a proxy server to connect to the FortiGuard Distribution Network on page 3319
l Manual updates on page 3320
l Automatic updates on page 3321
l Scheduled updates on page 3322
l Sending malware statistics to FortiGuard on page 3323
l Update server location on page 3324
l Filtering on page 3325
l Online security tools on page 3326
l Anycast and unicast services on page 3326
l Using FortiManager as a local FortiGuard server on page 3327
l Cloud service communication statistics on page 3330
l IoT detection service on page 3332
l FortiAP query to FortiGuard IoT service to determine device details on page 3336
l FortiGate Cloud / FDN communication through an explicit proxy on page 3337
FortiOS 7.6.2 Administration Guide 3316
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,316
|
System
l FDS-only ISDB package in firmware images on page 3338
l Licensing in air-gap environments on page 3339
l License expiration on page 3340
l FortiGate StateRamp support on page 3342
Anycast
FortiGuard servers use Anycast addresses in order to optimize and distribute traffic across many servers. Anycast is the
default access mode for FortiGates when connecting to FortiGuard which by default utilizes HTTPS and port 443.
Each type of FortiGuard servers and services have a FortiGuard domain name that resolves to a single Anycast IP
address. Regardless of where the FortiGate is located, the resolution is still the same. Fortinet maintains the network in
the background to ensure routes to the FortiGuard servers are optimized. In the below diagram, several servers have the
same Anycast IP, but the FortiGate will connect to the one with the least hops.
Connection and OCSP stapling
When the FortiGate connects to a FortiGuard server, it is important for it to validate the server is indeed a real FortiGuard
server. Hence, FortiGuard servers provide the following security:
l The domain name of each FortiGuard service is the common name in that service's certificate, which is signed by a
third-party intermediate CA.
l The FortiGuard server also applies Online Certificate Status Protocol (OCSP) stapling check, in which it attaches a
time-stamped OCSP status of the server certificate from the OCSP server to the TLS response.
This ensures FortiGate can validate the FortiGuard server certificate efficiently during the TLS handshake.
The following illustrates the connection process:
FortiOS 7.6.2 Administration Guide 3317
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,317
|
System
FortiGate will only complete the TLS handshake with an anycast server when abort conditions are not met. Abort
conditions include:
l The CN in the server's certificate does not match the domain name resolved from the DNS.
l The OCSP status is revoked or unknown.
l The issuer-CA is revoked by the root-CA.
To configure the anycast FortiGuard access mode:
config system fortiguard
set fortiguard-anycast enable
end
If FortiGuard is not reachable via Anycast, choose between the following options to work around this issue:
1. Switch to other Anycast servers:
config system fortiguard
set fortiguard-anycast enable
set fortiguard-anycast-source aws
end
2. Disable Anycast and use HTTPS:
config system fortiguard
set fortiguard-anycast disable
set protocol https
set port 8888
end
3. Disable Anycast and use UDP:
config system fortiguard
set fortiguard-anycast disable
set protocol udp
FortiOS 7.6.2 Administration Guide 3318
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,318
|
System
set port 53
end
Configuring FortiGuard updates
To configure FortiGuard updates:
1. Go to the System > FortiGuard > FortiGuard settings tab.
2. In the FortiGuard updates section, configure the options for connecting and downloading definition files:
Immediately download
updates
The option can be enabled on 2U and larger hardware models when the
FortiGuard are servers are connected in anycast mode.
The FortiGate forms a secure, persistent connection with FortiGuard to get
notifications of new updates through an HTTPS connection. The FortiGate
uses the fds_notify daemon to wait for the notification, then makes another
connection to the FortiGuard server to download the updates.
Scheduled Updates Enable to schedule updates to be sent to the FortiGate at the specified time or
automatically. See Scheduled updates on page 3322 and Automatic updates
on page 3321.
Improve IPS quality Enable to send information to the FortiGuard servers when an attack occurs.
This can help keep the FortiGuard database current as attacks evolve, and
improve IPS signatures.
Use extended IPS signature
package
Enable to use the extended IPS database, that includes protection from legacy
attacks, along with the regular IPS database that protects against the latest
common and in-the-wild attacks.
AntiVirus PUP/PUA Enable antivirus grayware checks for potentially unwanted applications.
Update server location The FortiGuard update server location. See Update server location on page
3324 for details.
3. Click Apply.
Using a proxy server to connect to the FortiGuard Distribution Network
You can configure FortiOS to use a proxy server to connect to the FortiGuard Distribution Network (FDN).
FortiOS 7.6.2 Administration Guide 3319
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,319
|
System
Proxy tunneling is supported only for registration, AV, and IPS updates. For FortiGate virtual
machines, proxy tunneling can also be used for license validation. For web filtering or spam
filtering, UDP protocol is used on ports 53 or 8888. UDP protocol traffic cannot be directed
over a proxy server, even if you are using versions of FortiOS that support web filtering over
port 443.
Consider the following before configuring FortiOS to use a proxy server to connect to FDN:
l FortiOS connects to the proxy server using the HTTP CONNECT method. For information about the HTTP
CONNECT method, see RFC 2616.
l The proxy server must not inspect the HTTPS traffic used for FortiOS communication.
l FortiOS sends to the proxy server an HTTP CONNECT request that specifies the IP address and port required for
the FDN connection. Authentication information is optional for the request.
l FortiOS or the proxy server must be configured to use DNS servers that resolve the addresses of FDN servers to
support AV and IPS updates.
l The proxy server establishes the connection to FDN and passes information between FortiOS and FDN.
Use the following syntax to configure a proxy server in the CLI:
config system autoupdate tunneling
set address <proxy_address>
set port <proxy_port>
set username <username>
set password <password>
set status {enable | disable}
end
In the following example, a proxy server with IP address 10.1.1.1 is configured to listen on port TCP/3128 without
authentication.
To configure a proxy server:
config system autoupdate tunneling
set address 10.1.1.1
set port 3128
set status enable
end
Alternatively, in a closed network without direct internet connection for web filtering or spam filtering, you can use
FortiManager as a local FortiGuard server. FortiManager supports allowing FortiOS to retrieve its updates and ratings
through FortiManager. See Using FortiManager as a local FortiGuard server on page 3327.
Manual updates
In order to download updated AV definitions, at least 1 policy with a security profile that has
Antivirus scanning must be enabled. To download updated IPS definitions, at least 1 policy
with a security profile that has IPS scanning must be enabled.
When needed, FortiGuard Distribution Network (FDN) updates can be manually uploaded.
FortiOS 7.6.2 Administration Guide 3320
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,320
|
System
To manually update the signature definitions files:
1. Log in to the Fortinet Support website.
2. Go to Support > Service Updates.
3. Select your OS Version from the dropdown list.
4. Locate your device in the table, and download the signature definitions files.
5. On the FortiGate, go to System > FortiGuard.
6. In the License Information table, locate and expand the definitions that you are updating.
7. From the Actions menu in the rightmost column, select Upgrade Database.
8. In the pane that opens, click Upload, locate the downloaded definitions file on your computer, then click Open.
The download may take a few minutes to complete.
9. Click OK.
AV and IPS manual updates
To execute the update:
# execute restore ips tftp nids-720-19.261.pkg 172.16.200.55
To verify the manual AV and IPS package updates:
# diagnose debug app updated -1
# diagnose debug enable
Security levels are pre-configured on the BIOS. See BIOS-level signature and file integrity
checking on page 3390 and Real-time file system integrity checking on page 3394 for more
information.
Automatic updates
In order to download updated AV definitions, at least 1 policy with a security profile that has
Antivirus scanning must be enabled. To download updated IPS definitions, at least 1 policy
with a security profile that has IPS scanning must be enabled.
The default auto-update schedule for FortiGuard packages is automatic. The update interval is calculated based on the
model and percentage of valid subscriptions, within one hour.
For example, if a FortiGate 501E has 78% valid contracts, then based on this device model, the update schedule is
calculated to be every 10 minutes. If you verify the system event logs (ID 0100041000), they are generated
approximately every 10 minutes.
FortiOS 7.6.2 Administration Guide 3321
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,321
|
System
To configure automatic updates in the GUI:
1. Go to System > FortiGuard
2. In the FortiGuard Updates section, enable Scheduled Updates and select Automatic.
3. Click Apply.
To configure scheduled updates in the CLI:
config system autoupdate schedule
set status enable
set frequency automatic
end
Scheduled updates
In order to download updated AV definitions, at least 1 policy with a security profile that has
Antivirus scanning must be enabled. To download updated IPS definitions, at least 1 policy
with a security profile that has IPS scanning must be enabled.
Scheduling updates ensures that the virus and IPS definitions are downloaded to your FortiGate on a regular basis.
Updating definitions can cause a brief disruption in traffic that is currently being scanned while the FortiGate unit applies
the new signature database. Updates should be scheduled during off-peak hours when network usage is at a minimum
to ensure that network activity will not be affected by downloading the definitions files.
A schedule of once a week means any urgent updates will not be pushed until the scheduled
time. If an urgent update is required, click the Update Licenses & Definitions Now button to
manually update the definitions.
To configure scheduled updates in the GUI:
1. Go to System > FortiGuard
2. In the FortiGuard Updates section, enable Scheduled Updates.
3. Configure the update schedule:
FortiOS 7.6.2 Administration Guide 3322
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,322
|
System
4. Click Apply.
To configure scheduled updates in the CLI:
config system autoupdate schedule
set status enable
set frequency {every | daily | weekly}
set time <hh:mm>
set day <day_of_week>
end
Sending malware statistics to FortiGuard
FortiGate devices periodically send encrypted antivirus, IPS, botnet IP list, and application control statistics to
FortiGuard. Included with these data is the IP address and serial number of the FortiGate, and the country that it is in.
This information is never shared with external parties, Fortinet Privacy Policy.
The malware statistics are used to improve various aspects of FortiGate malware protection. For example, antivirus data
allow FortiGuard to determine what viruses are currently active. Signatures for those viruses are kept in the Active AV
Signature Database that is used by multiple Fortinet products.Inactive virus signatures are moved to the Extended AV
Signature Database (see Configuring FortiGuard updates on page 3319). When events for inactive viruses start
appearing in the malware data, the signatures are moved back into the AV Signature Database.
The FortiGate and FortiGuard servers go through a 2-way SSL/TLS 1.2 authentication before any data is transmitted.
The certificates used in this process must be trusted by each other and signed by the Fortinet CA server.
The FortiGate only accepts data from authorized FortiGuard severs. Fortinet products use DNS to find FortiGuard
servers and periodically update their FortiGate server list. All other servers are provided by a list that is updated through
the encrypted channel.
Malware statistics are accumulated and sent every 60 minutes by default.
To configure sharing this information, use the following CLI command:
config system global
set fds-statistics {enable | disable}
set fds-statistics-period <minutes>
end
FortiOS 7.6.2 Administration Guide 3323
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,323
|
System
The submission of malware data is in accordance with the Fortinet Privacy Policy.
There is no sensitive or personal information included in these submissions. Only malware
statistics are sent.
Fortinet uses the malware statistics collected in this manner to improve the performance of the
FortiGate services and to display statistics on the Fortinet Support website for customers
registered FortiGate devices.
Fortinet may also publish or share statistics or results derived from this malware data with
various audiences. The malware statistics shared in this way do not include any customer
data.
Update server location
Administrators can specify the location of the FortiGuard update server used by FortiGate. You can can set the location
to only servers in the USA, only servers in the European Union (EU), or to servers with the lowest latency.
In EU locations, it can be required that certain traffic is only handled by servers located in the EU. By setting the update
server location to EU only, the FortiGate will use EU domains to resolve to EU servers for FortiGuard traffic to update,
URL rating, and IoT servers.
Server location Anycast domain name Non-Anycast FQDN addresses
EU only euupdate.fortinet.net
euguardservice.fortinet.net
US only usupdate.fortinet.net
usguardservice.fortinet.net
usupdate.fortiguard.net
UDP: usservice.fortiguard.net
HTTPS: ussecurewf.fortiguard.net
Lowest latency
(automatic)
globalupdate.fortinet.net
globalguardservice.fortinet.net
update.fortiguard.net
UDP: service.fortiguard.net
HTTPS: securewf.fortiguard.net
On hardware FortiGate devices, the default is Lowest latency locations. On VM devices, the default is US only.
FortiOS 7.6.2 Administration Guide 3324
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,324
|
System
To configure the update server location in the GUI:
1. Go to the System > FortiGuard > FortiGuard settings tab.
2. In the FortiGuard updates section, set Update server location to Lowest latency locations, US only, or EU only.
3. Click Apply.
To configure the update server location in the CLI:
config system fortiguard
set update-server-location {automatic | usa | eu}
end
Filtering
Web filtering is used to block access to harmful, inappropriate, and dangerous web sites (see FortiGuard filter on page
1822).
Email filtering is used to detect and block spam messages (see FortiGuard-based filters on page 2010).
To configure filtering in the GUI:
1. Go to System > FortiGuard
2. In the Filtering section configure the settings as needed:
Web Filter Cache Enable/disable web filter cache, and set the amount of time that the FortiGate
will store a blocked IP address or URL locally. After the time expires, the
FortiGate contacts the FDN to verify the address.
Email Filter Cache Enable/disable email filter cache, and set the amount of time that the FortiGate
will store an email address locally.
FortiGuard filtering services The protocol and port used to contact the FortiGuard servers. These options
can be changed in the CLI.
Filtering service availability The status of the filtering service. Click Test Connectivity if the filtering service
is not available.
Request re-evaluation of a
URL's category
Click to re-evaluate a URL category rating on the FortiGuard web filter service.
FortiOS 7.6.2 Administration Guide 3325
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,325
|
System
3. Click Apply.
To configure filtering in the CLI:
config system fortiguard
set protocol {https | udp}
set port {443 | 53 | 8888}
set antispam-force-off {enable | disable}
set antispam-cache {enable | disable}
set antispam-cache-ttl <integer>
set antispam-cache-mpercent <percent>
set antispam-timeout <integer>
set webfilter-force-off {enable | disable}
set webfilter-cache {enable | disable}
set webfilter-cache-ttl <integer>
set webfilter-timeout <integer>
end
When anycast is enabled (by default) the protocol is HTTPS and the port is 443.
Online security tools
FortiGuard Labs provides a number of online security tools, including but not limited to:
l URL lookup
Enter a website address to see if it has been rated and what category and classification it is filed as. If you find a site
that has been wrongly categorized, use this page to request that the site be re-evaluated:
https://www.fortiguard.com/webfilter
l Threat Encyclopedia
Browse FortiGuard Labs extensive encyclopedia of threats. Search for viruses, botnet C&C, IPS, endpoint
vulnerabilities, and mobile malware: https://www.fortiguard.com/encyclopedia
l Application Control
Browse FortiGuard Labs extensive encyclopedia of applications: https://www.fortiguard.com/appcontrol
Anycast and unicast services
The following services are accessed by FortiGate:
FortiOS 7.6.2 Administration Guide 3326
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,326
|
System
Service Non-Anycast FQDN addresses Anycast Domain name
FortiGuard Object download update.fortiguard.net globalupdate.fortinet.net
Querying service (web-filtering, antispam ratings) over HTTPS
securewf.fortiguard.net globalguardservice.fortinet.net
Querying service (web-filtering, antispam ratings) over UDP
service.fortiguard.net Service only in Unicast
Device info Collection Service only in Anycast globaldevcollect.fortinet.net
Device info Query Service only in Anycast globaldevquery.fortinet.net
FortiGate Cloud logging logctrl1.fortinet.com globallogctrl.fortinet.net
FortiGate Cloud management mgrctrl1.fortinet.com globalmgrctrl.fortinet.net
FortiGate Cloud messaging msgctrl1.fortinet.com globalmsgctrl.fortinet.net
FortiGate Cloud sandbox aptctrl1.fortinet.com globalaptctrl.fortinet.net
FortiCare registration directregistration.fortinet.com globalregistration.fortinet.net
Secure DNS sdns.fortinet.net globalsdns.fortinet.net
FortiCloud FortiClient forticlient.fortinet.net globalfctupdate.fortinet.net
FortiMobile Tokens directregistration.fortinet.com globalftm.fortinet.net
EMS cloud forticlient-emsproxy.forticloud.com Service only in Unicast
DDNS ddns.fortinet.net globalddns.fortinet.net
GeoIP gip.fortinet.net globalgip.fortinet.net
IP blocklist ipbl.fortinet.net N/A
Using FortiManager as a local FortiGuard server
FortiManager can provide a local FortiGuard server with port 443 access.
Anycast FortiGuard settings force the rating process to use port 443, even with an override server. Using a unique
address in the same subnet as the FortiManager access IP address, the FortiManager can provide local FortiGuard
updates and rating access with a dedicated IP address and port 443.
On FortiManager, use the Bind to IP addresses for the update and rating services over
TCP/443.
The Bind to IP address does not need to be configured for update services if the default port
was not changed to TCP/443. See Configuring network interfaces in the FortiManager
Administration Guide for more information.
FortiOS 7.6.2 Administration Guide 3327
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,327
|
System
To use a FortiManager as a local FortiGuard server in the GUI:
1. Go to the System > FortiGuard > FortiGuard settings tab.
2. In the Override FortiGuard servers table, click Create New. The Create New Override FortiGuard Server pane
opens.
3. Select the server address type: IPv4, IPv6, or FQDN.
4. Enter the FortiManager address in the Address field.
5. Select the type of server: AntiVirus & IPS Updates, Filtering, or Both.
6. Click OK.
7. Click Create New again to add a second override FortiManager for Filtering.
8. Click OK, then click Apply.
To use a FortiManager as a local FortiGuard server in the CLI:
config system central-management
set type fortimanager
set fmg "172.18.37.148"
config server-list
edit 1
set server-type update
set server-address 172.18.37.150
next
edit 2
set server-type rating
set server-address 172.18.37.149
next
end
set fmg-update-port 443
set include-default-servers enable
end
When fmg-update-port is set to 443, the update process will use port 443 to connect to the override update server,
which is the local FortiGuard server in the FortiManager. If this is not set, the update process will use port 8890, and the
server address setting has to be the FortiManager access IP address. Override FortiGuard services come from the
server list that is the local FortiGuard server in the FortiManager, and use the traditional, non-OCSP TLS handshake. If
override servers in the FortiManager are not available, the default FortiGuard servers are connected, and the anycast
OCSP TLS handshake is used.
The FortiManager IP address used in set server-address (for example, set server-address
172.18.37.149) corresponds to the Bind to IP setting configured on the FortiManager interface.
FortiOS 7.6.2 Administration Guide 3328
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,328
|
System
HA considerations
When FortiGate and FortiManager units are both in high availability (HA) clusters, and FortiGate is using FortiManager
as an update server, you must configure the following secondary IP addresses:
l Configure secondary IP addresses for the service on both FortiManager units in the HA cluster
l Configure FortiGate to use the secondary FortiManager IP addresses.
In this example, the primary FortiManager unit is configured to use the secondary IP address of 10.4.1.204 for the
rating service, and the secondary FortiManager unit is configured to use the secondary IP address of 10.4.1.205 for
the rating service. FortiGate is configured to use the secondary IP addresses on FortiManager.
To configure FortiManager units in an HA cluster as web filter rating servers:
1. On the primary FortiManager in the HA cluster, configure a secondary IP address for the rating service:
The set rating-service-ip is set to the secondary IP address for the rating query.
config system interface
edit "port1"
set ip 10.4.1.104 255.255.0.0
set allowaccess ping https ssh snmp http webservice
set serviceaccess fgtupdates fclupdates webfilter-antispam
set rating-service-ip 10.4.1.204 255.255.0.0
set type physical
next
end
2. On the secondary FortiManager in the HA cluster, configure a secondary IP address for the rating service:
The set rating-service-ip is set to the secondary IP address for the rating query.
config system interface
edit "port1"
set ip 10.4.1.105 255.255.0.0
set allowaccess ping https ssh snmp http webservice
set serviceaccess fgtupdates fclupdates webfilter-antispam
set rating-service-ip 10.4.1.205 255.255.0.0
set type physical
next
end
3. On both the primary and secondary FortiManager units in the HA cluster, enable web filter query:
config fmupdate service
set query-webfilter enable
end
4. On both the primary and secondary FortiManager units in the HA cluster, enable all web filter logs:
config fmupdate web-spam fgd-setting
set wf-log all
end
5. As needed, run the diagnose debug application fgdsvr 255 command.
For additional details, use shell and run bash$ tail -f /var/log/fgdsvr.log to display the incoming
URL queries.
FortiOS 7.6.2 Administration Guide 3329
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,329
|
System
To configure FortiGate:
1. On FortiGate, configure central management to use the secondary FortiManager IP addresses for the rating
service:
The set rating-service-ip is set to the secondary IP address on the primary and secondary FortiManager
units in the HA cluster.
config system central-management
set type fortimanager
config server-list
edit 1
set server-type update
set server-address 10.4.1.104
next
edit 3
set server-type update
set server-address 10.4.1.105
next
edit 2
set server-type rating
set server-address 10.4.1.204
next
edit 4
set server-type rating
set server-address 10.4.1.205
next
end
set include-default-servers disable
end
2. Disable Anycast:
config system fortiguard
set fortiguard-anycast disable
end
3. As needed, run the following diagnose commands:
l Run diagnose debug app urlfilter -1 to show the rating query response.
l Run diagnose debug rating to show the rating service information.
Cloud service communication statistics
Fortinet service communications statistics are displayed on the FortiGuard page. The statistics correspond with the
output from diagnose sys service-communication. The traffic volume values in the GUI are the sums of data
from the last 24 hours.
To view Fortinet service communications statistics:
1. Go to the System > FortiGuard > FortiGuard settings tab.
The Fortinet service communications statistics are displayed on the right side of the screen:
FortiOS 7.6.2 Administration Guide 3330
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,330
|
System
2. Enter the following CLI command:
# diagnose sys service-communication
FortiCare:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The last 7 days(in bytes): 0 0 0 0 0 0 0
FortiGuard Download:
The last 1 hour(in bytes): 0 648 3024 0 0 3056744 0 0 3024 0 0 3336
The last 24 hours(in bytes): 3066776 2960576 47616 71768 102384 68864 48224 82368 95376
70984 68048 75360 75112 83496
69848 51640 128360 20437472 99456 104384 48376 143024 25238104 73992
The last 7 days(in bytes): 6758344 120704952 0 0 0 0 0
FortiGuard Query:
The last 1 hour(in bytes): 0 10731 1622 0 0 1622 0 0 1622 0 0 1980
The last 24 hours(in bytes): 17577 21819 18521 18961 17309 16925 16937 18321 18614
17763 16266 17207 17775 17360 18076
18496 18704 18848 18600 17923 17686 17935 29384 31393
The last 7 days(in bytes): 216220 267569 0 0 0 0 0
FortiCloud Log:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The last 7 days(in bytes): 0 0 0 0 0 0 0
FortiSandbox Cloud:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The last 7 days(in bytes): 0 0 0 0 0 0 0
FortiGuard.com:
The last 1 hour(in bytes): 0 0 1647 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 1647 428908 1647 318 1647 102859 318 318 1647 102859 318
318 318 104188 318 318 1647 1028
59 318 318 318 104188 318 1647
The last 7 days(in bytes): 642804 1100822 0 0 0 0 0
SDNS Service:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The last 7 days(in bytes): 0 0 0 0 0 0 0
FortiToken Registration:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
FortiOS 7.6.2 Administration Guide 3331
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,331
|
System
The last 7 days(in bytes): 0 0 0 0 0 0 0
SMS Service:
The last 1 hour(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0
The last 24 hours(in bytes): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
The last 7 days(in bytes): 0 0 0 0 0 0 0
IoT detection service
Internet of Things (IoT) detection is part of the Attack Surface Security Rating service that allows FortiGate to:
l Download an IoT Detection signature package (IOTD), which is used to detect and extract metadata of IoT devices
l Query FortiGuard IoT Query service for devices that are not detected by the local Device Database (CIDB) or by the
IoT Detection signatures
l Query the FortiGuard vulnerability lookup server to look up vulnerabilities for a device
The service allows the FortiGate to accurately detect and identify connected IoT devices and to identify vulnerabilities
that apply to these devices.
Applications
A subscription to the IoT detection service provides many practical applications.
Device information Enable the FortiGate to obtain updated device information, store the information
in the asset inventory, and display the information in various places, such as the
Dashboard > Asset and Identities widget.
Vulnerability information Enable the FortiGate to query and display vulnerabilities associated with a device
on the Asset and Identities widget.
Allow managed FortiSwitch and
FortiAP devices to query device
info
Device detection is effective when devices are connected on an interface. As
such, when devices are connected to managed FortiSwitch and FortiAP devices,
they can utilize IoT detection to gather information about the connected devices.
See FortiAP query to FortiGuard IoT service to determine device details on page
3336 for more information. See also FortiSwitch Devices Managed by
FortiOS guide.
Perform NAC on IoT devices with
vulnerabilities
NAC policies can be configured to detect devices with different levels of
vulnerabilities and assign these devices dynamically to a quarantine VLAN.
See OT and IoT virtual patching on NAC policies on page 2137.
Perform IoT Vulnerability rating
check in Security Rating
Using the Security Fabric > Security Rating feature, perform a FortiGuard IoT
Vulnerability check to identify devices with detected vulnerabilities.
Detect and log IoT devices in
Application Control
IoT signatures are used in application control to detect and log IoT devices. In
Security Profiles > Application Signatures, filter on the IoT category to see the list
of IoT application signatures. Alternatively, view the signatures using the following
command:
# get application name status | grep IoT -B2 -A10
FortiOS 7.6.2 Administration Guide 3332
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,332
|
System
Device detection
When device detection is enabled on an interface, FortiGate will perform passive scanning on incoming traffic to collect
information about devices such as their MAC address, IP address, Operating System, Hostname, username, endpoint
tags and interface in which it entered . The firewall is able to scan different protocols to obtain basic device information.
FortiGates by default comes with a built-in local Device Database (CIDB) containing information about known devices
which can be used to obtain more detailed information.
When the CIDB cannot identify the device, FortiGate can utilize the IoT Query service by sending some device
information to the FortiGuard collection server. If a new device is detected, FortiGate obtains the results from the
FortiGuard query for more information about the device.
Device detection is intended for devices directly connected to your LAN and DMZ ports. Since the IoT detection service
relies on device detection, the device must be on the same Layer 2 network as the FortiGate.
Configurations
This feature requires an Attack Surface Security Rating service license.
FortiGate device requirements:
The FortiGate device must be:
l Registered with FortiCare
l Connected to an anycast FortiGuard server
How the service works:
1. Enable Device Detection on an interface.
2. FortiGate uses the interface to detect device traffic flow.
3. Upon detecting traffic from an unknown device, FortiGate sends the device data to the FortiGuard collection server.
4. The collection server returns data about the new device to the FortiGuard query server.
5. If the device signature does not appear in the local Device Database (CIDB) or some fields are not complete,
FortiGate queries FortiGuard for more information about the device.
To view the latest device information in the GUI, go to Dashboard > Assets & Identities and expand the Assets widget.
For more information, see Asset Identity Center page on page 3528.
FortiOS 7.6.2 Administration Guide 3333
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,333
|
System
To debug the IoT daemon in the CLI:
1. Enable iotd real-time debugs to collect information about the communication between FortiGate and the FortiGuard
server:
# diagnose debug application iotd -1
# diagnose debug enable
2. Optionally, disable the local device database to force all queries to go to FortiGuard.
# diagnose cid sigs disable
3. View the debug output.
FortiGate sends the device data to the FortiGuard collection server:
# [iotd] recv request from caller size:61
[iotd] service:collect hostname: ip: fd:-1 request tlv_len:41
[iotd] txt(.....y...w.....Jasons-iPhone6....579=23..)
[iotd] hex
(02010007017903060f77fc0203000e4a61736f6e732d6950686f6e6536020400083537393d32330cff)
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip: fd:-1 got server
hostname
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip:173.243.138.29 fd:-1
got server ip
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip:173.243.138.29 fd:13
socket created
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip:173.243.138.29 fd:13
FortiOS 7.6.2 Administration Guide 3334
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,334
|
System
connecting
[iotd] fd:13 monitor event:pollout
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip:173.243.138.29 fd:13
build req packet
[iotd] service:collect hostname:globaldevcollect.fortinet.net ip:173.243.138.29 fd:13
collect resp:1(pending)
The FortiGuard collection server returns new device data to the FortiGuard query server:
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 got
query resp
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 id:0
total_len:48 header_len:16 tlv_len:32 confidence:100 mac:f8:87:f1:1f:ab:95
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:32 type:1 len:6
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 got
tlv category:'Mobile'
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:24 type:2 len:6
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 got
tlv sub_category:'Mobile'
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:16 type:3 len:5
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 got
tlv vendor:'Apple'
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:9 type:4 len:0
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:7 type:5 len:3
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 got
tlv os:'iOS'
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17
remaining_len:2 type:6 len:0
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 send
query response to caller size:48
[iotd] txt(............d0 ...Mobile..Mobile..Apple....iOS..)
[iotd] hex
(f887f11fab950000000000006430200001064d6f62696c6502064d6f62696c6503054170706c65040005036
94f530600)
[iotd] service:query hostname:globaldevquery.fortinet.net ip:173.243.140.16 fd:17 read
resp:0(good)
4. Upon completion of the FortiGuard query, the query server returns the device information including the information
source (src fortiguard).
# diagnose user device list
vd root/0 f8:87:f1:1f:ab:95 gen 26 req OUA/34
created 503s gen 23 seen 102s lan gen 7
ip 192.168.1.110 src arp
hardware vendor 'Apple' src fortiguard id 0 weight 100
type 'Mobile' src fortiguard id 0 weight 100
family 'Mobile' src fortiguard id 0 weight 100
os 'iOS' src fortiguard id 0 weight 100
host 'Jasons-iPhone6' src dhcp
FortiOS 7.6.2 Administration Guide 3335
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,335
|
System
Using FortiManager as an override server for IoT query services
FortiGate can use FortiManager as an override server for IoT query services. The FortiManager must be running 7.2.1 or
later.
All IoT daemon query and collected data can be sent to a FortiManager, instead of directly to FortiGuard. This is useful
when there are strict policies controlling the kind of traffic that can go to the internet.
To send all IoT daemon query and collected data to a FortiManager:
config system central-management
config server-list
edit 1
set server-type vpatch-query iot-collect
set server-address <x.x.x.x>
next
end
end
server-type vpatch-query
iot-collect
Set the FortiGuard service types:
l vpatch-query: Virtual patch query server.
l iot-collect: IoT device collection server.
server-address <x.x.x.x> Enter the IPv4 address of the FortiManager.
FortiAP query to FortiGuard IoT service to determine device details
A FortiAP collects packets from devices and queries FortiGuard with the help of the FortiGate. Device detection results
are reported back to the FortiGate where this information is displayed. Querying the FortiGuard service requires an
Attack Surface Security Rating service license.
The following attributes can be configured in wireless-controller setting:
Attribute Description
device-weight <integer> Set the device upper limit of confidence (0 - 255, default = 1, 0 = disable).
device-holdoff <integer> Set the device lower limit of creation time, in minutes (0 - 60, default = 5).
device-idle <integer> Set the device upper limit of idle time, in minutes (0 - 14400, default = 1440).
To query the FortiGuard IoT service:
config wireless-controller setting
...
set device-weight 1
set device-holdoff 5
set device-idle 1440
...
end
# diagnose user device list
vd root/0 54:27:1e:e6:26:3d gen 89 req OUA/34
FortiOS 7.6.2 Administration Guide 3336
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,336
|
System
created 70s gen 86 seen 2s port29 gen 28
ip 10.29.1.214 src mac
hardware vendor 'Asustek compute' src fortiguard id 0 weight 21
type 'Home & Office' src fortiguard id 0 weight 21
family 'Computer' src fortiguard id 0 weight 21
os 'Linux' src dhcp id 822 weight 128
host 'test-wifi' src dhcp
FortiGate Cloud / FDN communication through an explicit proxy
Explicit proxy communication to FortiGate Cloud and FortiGuard servers from FortiGate is enabled. A proxy server can
be configured in the FortiGuard settings so that all FortiGuard connections under the forticldd process can be
established through the proxy server.
Not all FortiGuard services are supported by these proxy settings. For example, web filter
service traffic to FortiGuard will not be directed to the configured proxy.
To configure a proxy server and communicate with FortiGate Cloud though it:
1. Configure FortiGate B as a proxy server:
config firewall proxy-policy
edit 1
set proxy explicit-web
set dstintf "wan1"
set srcaddr "all"
set dstaddr "all"
set service "webproxy"
set action accept
set schedule "always"
set logtraffic all
set users "guest1"
next
end
config user local
edit "guest1"
set type password
set passwd 123456
next
end
config authentication scheme
edit "local-basic"
set method basic
set user-database "local-user-db"
next
end
config authentication rule
FortiOS 7.6.2 Administration Guide 3337
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,337
|
System
edit "local-basic-rule"
set srcaddr "all"
set ip-based disable
set active-auth-method "local-basic"
next
end
2. Configure a firewall policy on FortiGate B to allow FortiGate A to get DNS resolution:
config firewall policy
edit 1
set name "dns"
set srcintf "port18"
set dstintf "wan1"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "DNS"
set fsso disable
set nat enable
next
end
3. Configure the FortiGuard proxy settings on FortiGate A:
config system fortiguard
set proxy-server-ip 10.2.2.2
set proxy-server-port 8080
set proxy-username "guest1"
set proxy-password 123456
end
4. On FortiGate A, log in to FortiGate Cloud to activate the logging service:
execute fortiguard-log login <username> <password>
5. On FortiGate A, view the forticldd debug message to see the connection to the log controller through the proxy
server:
# diagnose test application forticldd 1
FDS-only ISDB package in firmware images
FortiOS firmware images include Fortinet objects in the built-in Internet Service Database (ISDB).
# diagnose firewall internet-service list
List internet service in kernel(global):
Internet Service Database Kernel Table: size 14974 bytes, Entry size 5844 bytes, number of
index table entries 165 number of IP range table entries 0
Group(0): Weight(15), number of entries(162)
......
This lightweight ISDB package allows firewall rules and policy routes that use ISDB to access FortiGuard servers to
continue working after upgrading FortiOS. For example, the following policy will work after an upgrade:
config firewall policy
edit 440
FortiOS 7.6.2 Administration Guide 3338
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,338
|
System
set name "Fortinet Updates"
set srcintf "port25"
set dstintf "port1"
set srcaddr "FortiAnalyzer" "FortiAuthenticator" "Tesla Management Interface"
"BackupFortinet" "SipFW" "ConnectVPNMgmt"
set internet-service enable
set internet-service-id 1245187 1245326 1245324 1245325 1245193 1245192 1245190
1245185
set action accept
set schedule "always"
set logtraffic all
set fsso disable
next
end
After the FortiGate reboots after a firmware update, an automatic update will run in five minutes so that the FortiGate can
get the ISDB, whether or not scheduled update is enabled.
# diagnose autoupdate versions | grep Internet -A 6
Internet-service Full Database
---------
Version: 7.02217 signed
Contract Expiry Date: n/a
Last Updated using manual update on Thu Mar 10 12:06:58 2022
Last Update Attempt: Thu Mar 10 12:07:27 2022
Licensing in air-gap environments
In the Operational Technology industry, industrial equipment is critical and must not be connected to the internet.
However, the equipment is still required to be protected by a firewall in this air-gap environment. Without a gateway to
FortiGuard in air-gap environments, FortiGuard packages, such as AntiVirus and IPS, must be manually uploaded to the
FortiGate. FortiGate licenses can be downloaded from FortiCloud and uploaded manually to the FortiGate.
Manual licensing for air-gap environments is supported on FortiGate hardware appliances and
FortiGate virtual machine (VM) appliaces running FortiOS 7.2.0 or later. When running on a
Virtual appliance, the VM licensing still needs to connect to a licensing FortiManager or
FortiGuard server. See VM license on page 3985 for details
To manually upload FortiGate licenses in the GUI:
1. Register the FortiGuard license on FortiCloud. See Registration for more information.
2. Download the product entitlement file in FortiCloud:
a. Go to Products > Product List.
b. Select the serial number of the FortiGate. The product page opens.
c. In the License & Key section, click Get The License File. The file downloads to your device in the format
FG201E*********ProductEntitlement.lic.
3. In FortiOS, go to System > FortiGuard. Currently, the status for all services is Pending.
4. Click Upload License File. The file explorer opens.
5. Navigate to the product entitlement file and click Open.
FortiOS 7.6.2 Administration Guide 3339
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,339
|
System
The license file uploads to the FortiGate. This operation does not require reboot. Once the upload is complete, the
FortiGate shows that it is registered and licensed.
6. Click Apply.
To manually upgrade the AntiVirus Database in the GUI:
1. Download the static upgrade file from FortiCloud:
a. Go to support.fortinet.com.
b. Go to Download > Download FortiGuard Service Updates > FortiGate.
c. Select the FortiOS version from the OS Version dropdown.
d. Select the file from the appropriate FortiGate product model section. The file downloads to your device.
2. In FortiOS, go to System > FortiGuard and expand the Advanced Malware Protection section to view the current
licenses.
3. Click Upgrade Database. The Anti-Virus Database Upgrade pane opens.
4. Click Upload. The file explorer opens.
5. Navigate to the static upgrade file and click Open.
6. Click OK.
7. Click Apply.
The AntiVirus Database is upgraded.
To manually upload FortiGate licenses in the CLI:
# execute restore manual-license {ftp | tftp} <license file name> <server> [args]
License expiration
The FortiGate will still function as a firewall if any or all of the FortiGuard licenses are expired. Valid FortiGuard licenses
are required to receive database and signature updates, and to perform real-time or near-real-time security lookups to
detect and quickly adjust your security posture for newly discovered attacks.
FortiGuard services are designed to be continuous. Any lapses in the service will require
coverage back to the contract expiration date. For more information, see FortiCare/FortiGuard
Renewal Continuous Service Policy.
License type Expiration impact
Firmware & General Updates Application Control Signatures, Device & OS Identification, FortiGate Virtual
Patch Signatures, Inline-CASB Application Definitions, Internet Service Database
Definitions, and PSIRT Package Definitions continue to work, but the databases
are not updated and no new signatures are added.
For example, if application control is used in a firewall policy that has an internet
service applied to the source or destination addresses, then the policy will
continue to inspect matching traffic using the FortiGate's existing application
control signatures and ISDB definitions.
FortiOS 7.6.2 Administration Guide 3340
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,340
|
System
License type Expiration impact
Application Control Signatures, Device & OS Identification, FortiGate Virtual
Patch Signatures, Inline-CASB Application Definitions, Internet Service Database
Definitions, and PSIRT Package Definitions are included in the base services that
are included with all FortiCare support contracts See FortiGuard Security
Services for details.
Intrusion Prevention IPS scanning continues to work, but the IPS databases are not updated and no
new signatures are added.
For example, if an IPS sensor with Block malicious URLs enabled is used in a
firewall policy, then the policy will continue to inspect matching traffic using the
FortiGate's existing IPS signatures and malicious URLs database.
An active IPS license is critical for stopping sophisticated and zero-day attacks, as
FortiGuard IPS provides near-real-time intelligence with thousands of intrusion
prevention rules to detect and block known and zero-day threats.
For more information, see Intrusion prevention on page 1960.
Botnet IPs/Domains IPS sensors and DNS Filter profiles with Botnet C&C configured continue to work,
but the Botnet IPs and Botnet Domain databases are not updated and no new
signatures are added.
While Botnet IPs and Domain are listed in the Intrusion Prevention category, they
are actually part of the Firmware & General Updates contract.
For more information, see Botnet C&C domain blocking on page 1896 and IPS
with botnet C&C IP blocking on page 1984.
AntiVirus Antivirus scanning continues to work, but the antivirus database is not updated
and no new signatures are added.
For more information, see Antivirus on page 1761.
Web and DNS Filtering Category-based Web and DNS filtering stops working, as URLs and domains are
sent to FortiGuard in real-time to determine the category.
By default, all web and DNS traffic is dropped. If allowing website or DNS
requests when a rating error occurs is enabled, then all web and DNS traffic
passes through without filtering.
If static URL or domain filtering is applied in a filter profile, those filters continue to
work.
Configurations where only specific URLs and domains are allowed and all others
are blocked continue to work, but this is not a scalable solution blocking websites
or performing category filtering.
For more information, see FortiGuard filter on page 1822 and FortiGuard
category-based DNS domain filtering on page 1893.
Email Filtering Spam filtering stops working, as it queries the FortiGuard spam filtering server in
real-time to check spammer IP addresses and emails (except those that are
locally configured), phishing URLs, spam URLs, spam email checksums, and
spam submissions. Anti-spam signatures are not updated.
Profile options based on local spam filtering continue to work.
For more information, see Email filter on page 2001.
FortiOS 7.6.2 Administration Guide 3341
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,341
|
System
License type Expiration impact
Outbreak Prevention Outbreak prevention stops working, as it uses real-time lookups to the FortiGuard
Global Threat Intelligence database.
For more information, see FortiGuard outbreak prevention on page 1811.
Security Rating & CIS
Compliance
Paid security rating checks stop working. CIS security control mappings are also
disabled.
The Security Rating & CIS Compliance component of the Attack Surface Security
Rating entitlement is required to run paid security rating checks across all of the
devices in the Security Fabric. They allow rating scores to be submitted to and
received from FortiGuard for network ranking. Without the Security Rating
entitlement, only built-in security rating rules can be run. PSIRT-related
vulnerability rules depend on the Firmware license support.
For more information, see Security rating on page 3592.
Operational Technology (OT)
Threat Definitions
OT Security Services signatures continue to work, but the database attack
definitions are not updated and no new signatures are added.
OT Security Services include application control and IPS signatures for OT
applications and protocols.
For example, if an IPS sensor enabled with OT Security Service signatures is
used in a firewall policy, then the policy will continue to inspect matching traffic
using the FortiGate's existing OT threat definition IPS signatures.
For more information, see OT threat definitions on page 1972.
FortiGate StateRamp support
A StateRamp FortiGate SKU entitles the FortiGate to use dedicated FortiGuard servers located in the United States. It
also entitles customers to access their support tickets through a dedicated FortiCare service located in the United
States.
When you purchase a StateRamp FortiGate, you will receive a FortiGate that automatically boots up in StateRamp
mode. It will contact the dedicated FortiGuard server to learn the rest of its entitlement.
All FortiGuard services that are supported by the StateRamp device are United States-based and use a specific FQDN.
The FortiGuard servers only support connections through Anycast. Any un-used cloud services are disabled on the
FortiGate.
Supported FortiGuard services
The following table lists supported FortiGuard services:
Feature or service FQDN IP address
FortiGate firmware upgrade
Contract / License Update
update.fortinetgov.com 23.249.62.6
FortiGuard Query guardservice.fortinetgov.com 23.249.62.16
FortiOS 7.6.2 Administration Guide 3342
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,342
|
System
Feature or service FQDN IP address
Video Query videoquery.fortinetgov.com 23.249.62.18
SDNS sdns.fortinetgov.com 23.249.62.53
Geo IP address Database gip.fortinetgov.com 23.249.62.16
Device Query devquery.fortinetgov.com 23.249.62.16
Default DNS server 23.249.63.52 / 23.249.63.53
Default NTP server time-a-g.nist.gov time-b-g.nist.gov 129.6.15.28 129.6.15.29
Unsupported FortiGuard services
The following lists the unsupported FortiGuard services:
l FortiCare server connection
l Central management to FortiManager or FortiGuard
l Logging to FortiAnalyzer
l FortiSandbox (FSA) and FSA Cloud configuration
l FortiGuard DDNS service
l FortiSwitch authorization
l FortiExtender pre-authorization
l Regular FortiGuard NTP setting
l Local FortiClient EMS
l FortiClient EMS cloud
l Product API: Device vulnerability on GUI device assets
l Security fabric CSF: Configured as root
l Security fabric CSF: Configured as leaf
l Alert email - User must configure their own email server
l FortiNDR
l Email Filter query to RBL_SERVER (dnsbl.sorbs.net)
l FortiToken server connection
l Logging to FortiGate Cloud server
l SD-WAN overlay
l Activating FortiGate Cloud account
l Regular FortiGuard DNS setting
l FortiAP pre-authorization
l Security rating under Security Fabric
l Attack Surface Security Rating
The following lists FortiGuard services that are subject to limitations:
l Security Rating, FortiSwitch, FortiAP, FortiClient, FortiExplorer, and FortiNAC related automation stitch, trigger, or
action
FortiOS 7.6.2 Administration Guide 3343
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,343
|
System
Blocking unsupported features on StateRamp devices
When trying to enable services that are not supported on StateRamp devices, an error will be returned in the GUI and
CLI. Likewise, some features are hidden in the GUI if they are disabled for StateRamp devices.
In the following example, the user attempts to enable FortiAnalyzer on a StateRamp FortiGate which is an unsupported
service on StateRamp devices.
To view StateRamp device unsupported feature errors:
1. In the CLI, verify that the device has a StateRamp license:
# get system status
Version: FortiGate-1101E v7.2.6,build4553,230821 (interim)
Security Level: 1
Firmware Signature: un-certified
...
License Status: StateRAMP
2. Test configuring the unsupported feature in the GUI:
a. In the GUI, go to Security Fabric > Fabric Connectors.
b. Edit Logging & Analytics.
c. Attempt to enable FortiAnalyzer.
An error is displayed and the Switch Controller feature is hidden.
3. Test configuring the unsupported feature in the CLI:
a. Attempt to enable FortiAnalyzer.
config log fortianalyzer setting
set status enable
Cannot enable FortiAnalyzer logging when StateRAMP license is used.
node_check_object fail! for status enable
value parse error before 'enable'
Command fail. Return code -39
An error is displayed.
FortiOS 7.6.2 Administration Guide 3344
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,344
|
System
Feature visibility
Feature visibility is used to control which features are visible in the GUI. This allows features that are not in use to be
hidden. Some features are also invisible by default and must be made visible before they can be configure in the GUI.
The visibility of a feature does not affect its functionality or configuration. Invisible features can still be configured using
the CLI.
To change the visibility of features:
1. Go to System > Feature Visibility.
2. Change the visibility of the features as required.
For information about what settings each option affects, click on the + icon to the right of the feature name.
Changes are listed on the right side of the content pane.
3. Click Apply.
Certificates
FortiOS leverages certificates in multiple areas, such as VPNs, administrative access, and deep packet inspection. This
section contains topics about uploading certificates and provides examples of how certificates may be used to encrypt
and decrypt communications, and represent the identity of the FortiGate. This sections assumes the reader has a high
level understanding of the public key infrastructure (PKI) system, particularly how entities leverage trusted certificate
authorities (CAs) to verify the authenticating party, and how public and private certificate keys work to secure
communications.
The certificates feature is hidden by default in FortiOS. In the GUI, go to System > Feature Visibility and enable
Certificates.
For additional capabilities and enhanced certificate management, please review the FortiAuthenticator Administration
Guide and Cookbook.
The following topics provide information about certificates:
l Automatically provision a certificate on page 3346
l Generate a new certificate on page 3350
l Regenerate default certificates on page 3351
l Import a certificate on page 3352
l Generate a CSR on page 3354
l CA certificate on page 3357
l Remote certificate on page 3357
l Certificate revocation list on page 3358
l Export a certificate on page 3359
l Uploading certificates using an API on page 3359
l Enrollment over Secure Transport for automatic certificate management on page 3379
The following topics provide examples of how to use certificates:
FortiOS 7.6.2 Administration Guide 3345
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,345
|
System
l Procuring and importing a signed SSL certificate on page 3364
l Microsoft CA deep packet inspection on page 3366
l Administrative access using certificates on page 3371
l Creating certificates with XCA on page 3371
l Basic site-to-site VPN with digital certificate on page 2254
l Configuring FortiClient EMS on page 3462
l SSL VPN with certificate authentication on page 2658
l SSL VPN with LDAP-integrated certificate authentication on page 2664
l Configuring certificates for SAML SSO on page 3580
l Protecting an SSL server on page 2150
l Using the default certificate for HTTPS administrative access on page 3068
Automatically provision a certificate
The Automated Certificate Management Environment (ACME), as defined in RFC 8555, is used by the public Let's
Encrypt certificate authority (https://letsencrypt.org) to provide free SSL server certificates. The FortiGate can be
configured to use certificates that are managed by Let's Encrypt, and other certificate management services, that use the
ACME protocol. The server certificates can be used for secure administrator log in to the FortiGate.
l The FortiGate must have a public IP address and a hostname in DNS (FQDN) that resolves to the public IP address.
l The configured ACME interface must be public facing so that the FortiGate can listen for ACME update requests. It
must not have any VIPs, or port forwarding on port 80 (HTTP) or 443 (HTTPS).
l The Subject Alternative Name (SAN) field is automatically filled with the FortiGate DNS hostname. It cannot be
edited, wildcards cannot be used, and multiple SANs cannot be added.
ACME certificates do not support loopback interfaces.
This example shows how to import an ACME certificate from Let's Encrypt, and use it for secured remote administrator
access to the FortiGate.
FortiOS 7.6.2 Administration Guide 3346
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,346
|
System
To generate a certificate using ACME and Let’s Encrypt:
1. Go to System > Certificates and click Create/Import > Certificate.
2. Click Use Let's Encrypt.
3. Set Certificate name to an appropriate name for the certificate. This is what is referenced when using the certificate
in FortiGate configurations.
4. Set Domain to the public FQDN of the FortiGate.
5. Set Email to a valid email address. The email is not used during the enrollment process.
6. Click Create.
7. Set the ACME interface, on which the ACME client will listen for challenges in order to provision and renew
certificates. The challenge is how the certificate signing request is validated by Let's Encrypt.
8. Click OK. Let's Encrypt provisions the certificate and the certificate is added to the certificate list in the Local
Certificates section.
FortiOS 7.6.2 Administration Guide 3347
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,347
|
System
9. Click View Details to verify that the FortiGate's FQDN is in the certificate's Subject: Common Name (CN).
To import an ACME certificate in the CLI:
1. Set the interface that the FortiGate communicates with Let's Encrypt on:
config system acme
set interface "port1"
end
2. Make sure that the FortiGate can contact the Let's Encrypt enrollment server:
# execute ping acme-v02.api.letsencrypt.org
PING ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com (172.65.32.248): 56 data bytes
64 bytes from 172.65.32.248: icmp_seq=0 ttl=60 time=2.0 ms
64 bytes from 172.65.32.248: icmp_seq=1 ttl=60 time=1.7 ms
64 bytes from 172.65.32.248: icmp_seq=2 ttl=60 time=1.7 ms
64 bytes from 172.65.32.248: icmp_seq=3 ttl=60 time=2.1 ms
64 bytes from 172.65.32.248: icmp_seq=4 ttl=60 time=2.0 ms
--- ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.7/1.9/2.1 ms
3. Configure the local certificate request:
config vpn certificate local
edit "acme-test"
set enroll-protocol acme2
set acme-domain "test.ftntlab.de"
set acme-email "techdoc@fortinet.com"
next
By enabling this feature you declare that you agree to the Terms of Service at
https://acme-v02.api.letsencrypt.org/directory
Do you want to continue? (y/n)y
end
4. Verify that the enrollment was successful:
# get vpn certificate local details acme-test
path=vpn.certificate, objname=local, tablename=(null), size=2632
== [ acme-test ]
Name: acme-test
FortiOS 7.6.2 Administration Guide 3348
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,348
|
System
Subject: CN = test.ftntlab.de
Issuer: C = US, O = Let's Encrypt, CN = R3
Valid from: 2021-03-11 17:43:04 GMT
Valid to: 2021-06-09 17:43:04 GMT
Fingerprint: 9A:03:0F:41:29:D7:01:45:04:F3:16:C0:BD:63:A2:DB
Serial Num: 03:d3:55:80:d2:e9:01:b4:ca:80:3f:2e:fc:24:65:ad:7c:0c
ACME details:
Status: The certificate for the managed domain has been renewed successfully and
can be used (valid since Thu, 11 Mar 2021 17:43:04 GMT).
Staging status: Nothing in staging
5. Check the ACME client full status log for the CN domain:
# diagnose sys acme status-full test.ftntlab.de
{
"name": "test.ftntlab.de",
"finished": true,
"notified": false,
"last-run": "Thu, 11 Mar 2021 18:43:02 GMT",
"valid-from": "Thu, 11 Mar 2021 17:43:04 GMT",
"errors": 0,
"last": {
"status": 0,
"detail": "The certificate for the managed domain has been renewed successfully and
can be used (valid since Thu, 11 Mar 2021 17:43:04 GMT). A graceful server restart now
is recommended.",
"valid-from": "Thu, 11 Mar 2021 17:43:04 GMT"
},
"log": {
"entries": [
{
"when": "Thu, 11 Mar 2021 18:43:05 GMT",
"type": "message-renewed"
},
...
{
"when": "Thu, 11 Mar 2021 18:43:02 GMT",
"type": "starting"
}
]
}
}
To exchange the default FortiGate administration server certificate for the new public Let's Encrypt
server certificate in the GUI:
1. Go to System > Settings.
2. Set HTTPS server certificate to the new certificate.
FortiOS 7.6.2 Administration Guide 3349
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,349
|
System
3. Click Apply.
4. Log in to the FortiGate using an administrator account from any internet browser. There should be no warnings
related to non-trusted certificates, and the certificate path should be valid.
To exchange the default FortiGate administration server certificate for the new public Let's Encrypt
server certificate in the CLI:
config system global
set admin-server-cert "acme-test"
end
When you log in to the FortiGate using an administrator account there should be no warnings related to non-trusted
certificates, and the certificate path should be valid.
Generate a new certificate
The FortiGate can generate a certificate using a pre-loaded, self-signed CA certificate: Fortinet_CA_SSL, instead of
generating a CSR and providing it to a CA for signing. It is recommended that a server certificate from a well-known and
trusted CA is used.
To generate a new certificate:
1. Go to System > Certificates and select Create/Import > Certificate.
2. Click Generate Certificate.
3. Set Certificate name to the name of the certificate. This is what is referenced when using the certificate in FortiGate
configurations.
4. Set the Common name (CN) for the certificate. The common name should match the FQDN or IP of the primary
SSL-VPN interface.
5. Optionally, set the Subject alternative name.
6. Click Download CA Certificate to download the CA certificate so that it can be installed or imported to all the
machines that need to trust this certificate.
FortiOS 7.6.2 Administration Guide 3350
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,350
|
System
7. Click Create.
8. After the certificate is created, click Download Certificate to download the certificate. Click View Details to review the
certificate details.
9. Click OK.
Regenerate default certificates
The FortiGate includes default certificates that are generated the first time that the FortiGate is booted up. In some
circumstances, it can be necessary to regenerate these certificates, such as when they are nearing expiry, or if the key
becomes compromised.
To regenerate default certificates:
# execute vpn certificate local generate default-gui-mgmt-cert
# execute vpn certificate local generate default-ssl-ca
# execute vpn certificate local generate default-ssl-ca-untrusted
# execute vpn certificate local generate default-ssl-key-certs
# execute vpn certificate local generate default-ssl-serv-key
FortiOS 7.6.2 Administration Guide 3351
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,351
|
System
default-gui-mgmt-cert Regenerate the default GUI management admin-server (Fortinet_GUI_Server)
certificate.
default-ssl-ca Regenerate the default CA certificate (Fortinet_CA_SSL) used by SSL
Inspection.
default-ssl-ca-untrusted Regenerate the default untrusted CA certificate (Fortinet_CA_Untrusted) used by
SSL Inspection.
default-ssl-key-certs Regenerate the default RSA, DSA, ECDSA, and EdDSA key certificates for SSL
resign:
l Fortinet_SSL_DSA1024
l Fortinet_SSL_DSA2048
l Fortinet_SSL_ECDSA256
l Fortinet_SSL_ECDSA384
l Fortinet_SSL_ECDSA521
l Fortinet_SSL_ED448
l Fortinet_SSL_ED25519
l Fortinet_SSL_RSA1024
l Fortinet_SSL_RSA2048
l Fortinet_SSL_RSA4096
default-ssl-serv-key Regenerate the default server key (Fortinet_SSL) used by SSL Inspection.
Import a certificate
You can upload a certificate to the FortiGate that was generated on its own. This is typical of wildcard certificates
(*.domain.tld) where the same certificate is used across multiple devices (FGT.domain.tld, FAZ.domain.tld, and so on),
but can also be used for individual certificates as long as the information provided to the signing CA matches that of the
FortiGate.
Any certificate uploaded to a VDOM is only accessible to that VDOM. Any certificate uploaded to the Global VDOM is
globally accessible by all VDOMs.
A signed certificate that is created using a CSR that was generated by the FortiGate does not include a private key, and
can be imported to the FortiGate from a the management computer or a TFTP file server.
There are three options:
l Local certificate on page 3352
l PKCS #12 certificate on page 3353
l Certificate on page 3353
Local certificate
This option allows you to upload a single file and no key. Use it when you have created a CSR on the FortiGate
(Generate a CSR on page 3354), as the key is generated as part of the CSR process and remains on the FortiGate. You
must upload a .CER file.
FortiOS 7.6.2 Administration Guide 3352
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,352
|
System
To import a local certificate in the GUI:
1. Go to System > Certificates and select Create/Import > Certificate.
2. Click Import Certificate.
3. Set Type to Local Certificate.
4. Click Upload, and locate the certificate on the management computer.
5. Click Create, then click OK on the confirmation page.
To import a local certificate in the CLI:
execute vpn certificate local import tftp <filename> <tftp_IP> cer
PKCS #12 certificate
This option takes a specific certificate file type that contains the private key. The certificate is encrypted and a password
must be supplied with the certificate file. PKCS #12 certificates are .PFX files.
To import a PKCS #12 certificate in the GUI:
1. Go to System > Certificates and select Create/Import > Certificate.
2. Click Import Certificate.
3. Set Type to PKCS #12 Certificate.
4. Click Upload, and locate the certificate on the management computer.
5. Enter the password, then confirm the password.
6. Optionally, customize the Certificate name.
7. Click Create, then click OK on the confirmation page.
To import a PKCS #12 certificate in the CLI:
execute vpn certificate local import tftp <filename> <tftp_IP> p12 <password>
Certificate
This option is intended for certificates that were generated without using the FortiGate’s CSR. Because the certificate
private key is being uploaded, a password is required. This option is similar to PKCS #12 certificate, but the certificate
and key file are separate files, usually .CER and .PEM files.
FortiOS 7.6.2 Administration Guide 3353
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,353
|
System
To import a certificate in the GUI:
1. Go to System > Certificates and select Create/Import > Certificate.
2. Click Import Certificate.
3. Set Type to Certificate.
4. In the Certificate field, click Upload, and locate the certificate on the management computer.
5. In the Key file field, click Upload, and locate the key file on the management computer.
6. Enter the password, then confirm the password.
7. Optionally, customize the Certificate name.
8. Click Create, then click OK on the confirmation page.
To import a certificate that requires a private key to a VDOM, or when VDOMs are disabled:
config vpn certificate {local | ca | remote | ocsp-server | crl}
Refer to the FortiOS CLI Reference for detailed options for each certificate type (local, CA, remote, OSCP server, CRL).
To import a global certificate that requires a private key when VDOMs are enabled:
config certificate {local | ca | remote | crl}
This command is only available when VDOMs are enabled. For details, see the FortiOS CLI Reference.
Generate a CSR
Certificate signing requests (CSRs) are used to generate a certificate which is then signed by a CA to create a chain of
trust. The CSR includes details about the FortiGate and its public key. A CSR is not strictly necessary; some CAs allow
you to provide the details of the FortiGate manually, but a CSR helps streamline the process.
FortiOS 7.6.2 Administration Guide 3354
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,354
|
System
To generate a CSR in the GUI:
1. Go to System > Certificates and select Create/Import > Generate CSR.
2. Enter the following information:
Certificate Name Enter the certificate name; this is how it will appear in the Local Certificates
list.
Subject Information Specify an ID type: host IP address, domain name (FQDN), or email
address.
Optional Information Although listed as optional, we recommended entering the information for
each field in this section.
If you are generating a CSR for a third-party CA, you need to insure that
these values reflect those listed for your company or organization at said
certificate authority. If you are generating a certificate for a Microsoft CA,
you need to check with the administrator regarding these values.
Organization Unit Enter the name of the organizational unit under which the certificate will be
issued.
Organization Enter the overall name of the organization.
Locality(City) Enter the city where the SSL certificate is located.
State / Province Some issuers will reject a CSR that has an abbreviated state or province,
so enter the full name of the state or province.
Country / Region Enable the option and select the country from the dropdown.
E-Mail Enter the email address of the technical contact for the SSL certificate that
is being requested.
Subject Alternative
Name
This field allows multiple domains to be used in an SSL certificate. Select
from email addresses, IP addresses, URIs, DNS names, and so on.
FortiOS 7.6.2 Administration Guide 3355
Fortinet Inc.
|
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.