index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,955
|
WAN optimization
Example configuration
To configure tunnel sharing for HTTP traffic in a WAN optimization profile:
config wanopt profile
edit default
config http
set tunnel-sharing {express-shared | private | shared}
end
next
end
Transparent mode
WAN optimization is transparent to users. This means that with WAN optimization in place, clients connect to servers in
the same way as they would without WAN optimization. However, servers receiving packets after WAN optimization see
different source addresses depending on whether or not transparent mode is selected for WAN optimization. If
transparent mode is selected, WAN optimization keeps the original source address of the packets, so servers appear to
receive traffic directly from clients. Routing on the server network should be configured to route the traffic back to the
client network.
Some protocols, for example CIFS, may not function as expected if transparent mode is not
selected. In most cases, for CIFS WAN optimization you should select transparent mode and
confirm the server network can route traffic as described to support transparent mode.
If transparent mode is not selected, the source address of the packets received by servers is changed to the address of
the server-side FortiGate unit interface that sends the packets to the servers. So servers appear to receive packets from
the server-side FortiGate unit. Routing on the server network is simpler in this case because client addresses are not
involved. All traffic appears to come from the server-side FortiGate unit and not from individual clients.
Do not confuse WAN optimization transparent mode with FortiGate transparent mode. WAN
optimization transparent mode is similar to source NAT. FortiGate's transparent mode is a
system setting that controls how the FortiGate unit (or a VDOM) processes traffic.
Configuring transparent mode
You can configure transparent mode by selecting Transparent in a WAN optimization profile. The profile is added to an
active WAN optimization policy.
When you configure a passive WAN optimization policy you can accept or override the active policy transparent setting.
From the GUI you can do this by setting the Passive option as follows:
l Default: Use the transparent setting in the WAN optimization profile added to the active policy (client-side
configuration).
l Transparent: Override the active policy transparent mode setting and impose transparent mode. Packets exiting the
FortiGate keep their original source addresses.
l Non-transparent: Override the active policy transparent mode setting and impose non-transparent mode. Packets
FortiOS 7.6.2 Administration Guide 3956
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,956
|
WAN optimization
exiting the FortiGate have their source address changed to the address of the server-side FortiGate unit interface
that sends the packets to the servers.
To configure a passive wan optimization policy in the CLI:
config firewall policy
edit <policy ID>
set srcintf <Incoming interface>
set wanopt-passive-opt {default | transparent | non-transparent}
next
end
Protocol optimization
Protocol optimization techniques optimize bandwidth use across the WAN. These techniques can improve the efficiency
of communication across the WAN optimization tunnel by reducing the amount of traffic required by communication
protocols. You can apply protocol optimization to CIFS, FTP, HTTP, MAPI, and general TCP sessions. You can apply
general TCP optimization to MAPI sessions.
FortiGate supports WAN optimization for SMBv1, SMBv2, and SMBv3 (unencrypted only)
protocols.
For example, CIFS provides file access, record locking, read/write privileges, change notification, server name
resolution, request batching, and server authentication. CIFS requires many background transactions to successfully
transfer a single file. This is usually not a problem across a LAN. However, across a WAN, latency and bandwidth
reduction can slow down CIFS performance.
When you select the CIFS protocol in a WAN optimization profile, the FortiGate units at both ends of the WAN
optimization tunnel use a number of techniques to reduce the number of background transactions that occur over the
WAN for CIFS traffic.
If a policy accepts a range of different types of traffic, you can set Protocol to TCP to apply general optimization
techniques to TCP traffic. However, applying this TCP optimization is not as effective as applying more protocol-specific
optimization to specific types of traffic. TCP protocol optimization uses techniques such as TCP SACK support, TCP
window scaling and window size adjustment, and TCP connection pooling to remove TCP bottlenecks.
Byte caching
Byte caching breaks large units of application data (for example, a file being downloaded from a web page) into small
chunks of data, labeling each chunk of data with a hash of the chunk and storing those chunks and their hashes in a
database. The database is stored on a WAN optimization storage device. Then, instead of sending the actual data over
the WAN tunnel, the FortiGate unit sends the hashes. The FortiGate unit at the other end of the tunnel receives the
hashes and compares them with the hashes in its local byte caching database. If any hashes match, that data does not
have to be transmitted over the WAN optimization tunnel. The data for any hashes that does not match is transferred
over the tunnel and added to that byte caching database. Then the unit of application data (the file being downloaded) is
reassembled and sent to its destination.
The stored byte caches are not application specific. Byte caches from a file in an email can be used to optimize
downloading that same file or a similar file from a web page.
FortiOS 7.6.2 Administration Guide 3957
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,957
|
WAN optimization
The result is less data transmitted over the WAN. Initially, byte caching may reduce performance until a large enough
byte caching database is built up.
To enable byte caching, select Byte Caching in a WAN optimization profile.
Byte caching cannot determine whether or not a file is compressed (for example a zip file), and caches compressed and
non-compressed versions of the same file separately.
Dynamic data chunking for byte caching
Dynamic data chunking can improve byte caching by improving detection of data chunks that are already cached in
changed files or in data embedded in traffic using an unknown protocol. Dynamic data chunking can only be enabled
from the CLI and is available for HTTP, CIFS and FTP.
Dynamic data chunking is disabled by default and prefer-chunking is set to fix.
To enable dynamic data chunking for HTTP in the default WAN optimization profile:
config wanopt profile
edit default
config http
set prefer-chunking dynamic
end
next
end
Cache service and video caching
Two features that can only be configured in the CLI include cache service and video caching.
Cache service
The config wanopt cache-service command is used to configure cache-service clusters between multiple
FortiGates. The result is that the cache-service daemons of the different FortiGates can collaborate for serving web
cache entries.
See config wanopt cache-service in the CLI Reference guide for more configuration information.
Video caching
The config wanopt content-delivery-network-rule command configures web-caching, including the videocache matching rules.
See config wanopt content-delivery-network-rule in the CLI Reference guide for more configuration information.
FortiOS 7.6.2 Administration Guide 3958
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,958
|
WAN optimization
Manual and active-passive
You can create manual (peer-to-peer) and active-passive WAN optimization configurations.
There are a few key differences between manual and active-passive mode:
l For manual mode, the tunnels are always up which makes it more resource extensive as compared to activepassive.
l The performance of active-passive mode is lower than manual mode for the new connection.
l The active-passive mode can be used to deploy tunnel dynamically using Authentication groups set to accept Any
peers which eliminates the need of defining peers manually. This is not possible with manual mode.
This setting is only recommended when you do not know the peer host IDs or IP addresses
of the peers that will use this authentication group. This setting is most often used with
FortiGate units that do not have static IP addresses, for example units that use DHCP.
l For manual mode, traffic shaping cannot be applied to traffic on the server-side. See Traffic shaping on page 3962
for more information.
Manual (peer to peer) configurations
Manual configurations allow for WAN optimization between one client-side FortiGate unit and one server-side FortiGate
unit. Manual WAN optimization requires a manual WAN optimization firewall policy on the client-side FortiGate unit and a
WAN optimization proxy policy on the server-side FortiGate unit.
In a manual mode configuration, the client-side peer can only connect to the named server side peer. When the clientside peer initiates a tunnel with the server-side peer, the packets that initiate the tunnel include extra information so that
the server-side peer can determine that it is a peer-to-peer tunnel request. This extra information is required because the
server-side peer does not require a WAN optimization firewall policy; however, you need to add the client peer host ID
and IP address to the server-side FortiGate unit peer list. See Manual (peer-to-peer) WAN optimization configuration
example on page 3966 for a sample configuration.
Active-passive configurations
Active-passive WAN optimization requires an active WAN optimization firewall policy on the client-side FortiGate unit
and a passive WAN optimization firewall policy on the server-side FortiGate unit. The server-side FortiGate unit also
requires a WAN optimization proxy policy.
You can use the passive policy to control WAN optimization address translation by specifying transparent mode or nontransparent mode. You can also use the passive policy to apply security profiles, web caching, and other FortiGate
features at the server-side FortiGate unit. For example, if a server-side FortiGate unit is protecting a web server, the
passive policy could enable web caching.
A single passive policy can accept tunnel requests from multiple FortiGate units as long as the server-side FortiGate unit
includes their peer IDs and all of the client-side FortiGate units include the server-side peer ID. See Active-passive WAN
optimization configuration example on page 3970 for a sample configuration.
The WAN optimization proxy policy can only be added from the CLI and policies with proxy
set to wanopt do not appear on the GUI.
FortiOS 7.6.2 Administration Guide 3959
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,959
|
WAN optimization
Monitoring performance
Using WAN Opt. & Cache widgets, you can confirm that a FortiGate unit is optimizing traffic and view estimates of the
amount of bandwidth saved. These include peers manually added to the configuration as well as discovered peers.
To add WAN Opt. & Cache widgets go to Dashboard > Status > Add Widget > WAN Opt. & Cache and add WAN Opt.
Monitor and Peer Monitor.
Wan Opt. Monitor
The Wan Opt. Monitor shows how WAN optimization is reducing the amount of traffic on the WAN for each WAN
optimization protocol by showing the amount of WAN and LAN traffic. If WAN optimization is being effective, the amount
of WAN traffic should be lower than the amount of LAN traffic.
Peer Monitor
The Peer Monitor lists all of the WAN optimization peers that a FortiGate unit can perform WAN optimization with.
System and feature operation with WAN optimization
This section contains the following information:
l HA on page 3961
l Memory usage on page 3961
l Distributing WAN optimization processing on page 3961
l Distributing WAN optimization to multiple CPU cores on page 3962
l Identity policies and load balancing on page 3962
l Traffic shaping on page 3962
FortiOS 7.6.2 Administration Guide 3960
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,960
|
WAN optimization
HA
You can configure WAN optimization on a FortiGate HA cluster. The recommended best practice HA configuration for
WAN optimization is active-passive mode. When the cluster is operating, 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.
You can also form a WAN optimization tunnel between a cluster and a standalone FortiGate unit or between two
clusters.
In a cluster, only the primary unit stores the byte cache database. This database is not synchronized to the subordinate
units. So, after a failover, the new primary unit must rebuild its byte cache. Rebuilding the byte cache can happen
relatively quickly because the new primary unit gets byte cache data from the other FortiGate unit that it is participating
with in WAN optimization tunnels.
Memory usage
To accelerate and optimize disk access and to provide better throughput and less latency, FortiOS WAN optimization
uses provisioned memory to reduce disk I/O and increase disk I/O efficiency. In addition, WAN optimization requires a
small amount of additional memory per session for comprehensive flow control logic and efficient traffic forwarding.
When WAN optimization is enabled you will see a reduction in available memory. The reduction increases when more
WAN optimization sessions are being processed. If you are thinking of enabling WAN optimization on an operating
FortiGate unit, make sure its memory usage is not maxed out during high traffic periods.
In addition to using the system dashboard to see the current memory usage you can use the get test wad 2
command to see how much memory is currently being used by WAN optimization.
Distributing WAN optimization processing
The wad-worker balancing algorithm supports a more balanced dispersal of traffic to the wad processes even if the
bulk of the traffic is coming from a small set of sources or single source.
By default, dispatching traffic to WAD workers is based on source affinity. This may negatively affect performance when
users have another explicit proxy in front of the FortiGate. Source affinity causes the FortiGate to process the traffic as if
it originated from the single (or small set of ) IP address of the outside proxy. This results in the use of one, or a small
number, of WAD processes.
By disabling wad-source-affinity the traffic is balanced over all of the WAD processes. The WAD dispatcher will
not assign the traffic based on the source IP address, but will assign the traffic to available workers in a round-robin
fashion.
To configure WAD source affinity:
config system global
set wad-source-affinity {enable | disable}
end
FortiOS 7.6.2 Administration Guide 3961
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,961
|
WAN optimization
Handling the traffic by different WAD workers results in losing cached related benefits of using
source affinity, as there is the memory cache on the current wad worker and if a new
connection is handled by another worker, the cache will not be hit.
This is explained by the warning message that appears when it is disabled:
WARNING: Disabling this option results in some features to be
unsupported. IP-based user authentication, disclaimer messages, security
profile override, authentication cookies, MAPI scanning, and some video
caches such as YouTube are not supported.
Do you want to continue? (y/n)
Distributing WAN optimization to multiple CPU cores
By default WAN optimization is handled by half of the CPU cores in a FortiGate unit. For example, if your FortiGate unit
has 4 CPU cores, by default two will be used for WAN optimization. You can use the following command to change the
number of CPU cores that are used.
config system global
set wad-worker-count <number>
end
The wad-worker-count can be between 1 and the total number of CPU cores in your FortiGate unit. Adding more
cores may enhance WAN optimization but reduce the performance of other FortiGate systems.
Identity policies and load balancing
WAN optimization and firewall policies compatibility varies depending on the type of policy:
l WAN optimization is not compatible with firewall load balancing.
l WAN optimization is compatible with source and destination NAT options in firewall policies (including firewall virtual
IPs). If a virtual IP is added to a policy, the traffic that exits the WAN optimization tunnel has its destination address
changed to the virtual IPs mapped to IP address and port.
l WAN optimization is compatible with user identity-based and device identity security policies. If a session is allowed
after authentication or device identification the session can be optimized.
Traffic shaping
Traffic shaping works for WAN optimization traffic that is not in a WAN optimization tunnel. So traffic accepted by a WAN
optimization policy on a client-side FortiGate unit can be shaped on ingress. However, when the traffic enters the WAN
optimization tunnel, traffic shaping is not applied.
In manual mode:
l Traffic shaping works as expected on the client-side FortiGate unit.
l Traffic shaping cannot be applied to traffic on the server-side FortiGate unit.
In active-passive mode:
FortiOS 7.6.2 Administration Guide 3962
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,962
|
WAN optimization
l Traffic shaping works as expected on the client-side FortiGate unit.
l If transparent mode is enabled in the WAN optimization profile, traffic shaping also works as expected on the serverside FortiGate unit.
l If transparent mode is not enabled, traffic shaping works partially on the server-side FortiGate unit.
Best practices
WAN optimization and explicit proxy best practices include:
l WAN optimization tunnel sharing is recommended for similar types of WAN optimization traffic. However, tunnel
sharing for different types of traffic is not recommended. For example, aggressive and non-aggressive protocols
should not share the same tunnel.
l Active-passive HA is the recommended HA configuration for WAN optimization.
l Configure WAN optimization authentication with specific peers. Accepting any peer is not recommended as this can
be less secure.
Example topologies
All FortiGate WAN optimization topologies consist of two FortiGate units operating as WAN optimization peers
intercepting and optimizing traffic crossing the WAN between the private networks.
The following topics cover a few of the example topologies:
l In-path WAN optimization topology on page 3963
l Out-of-path WAN optimization topology on page 3964
l Topology for multiple networks on page 3964
In-path WAN optimization topology
FortiGate units can be deployed as typical security devices that protect private networks connected to the WAN and also
perform WAN optimization. The WAN optimization configuration intercepts traffic to be optimized as it passes through
the FortiGate unit and uses a WAN optimization tunnel with another FortiGate unit to optimize the traffic that crosses the
WAN.
You can add web caching to any WAN optimization topology when users on a private network communicate with web
servers located across the WAN on another private network.
FortiOS 7.6.2 Administration Guide 3963
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,963
|
WAN optimization
Out-of-path WAN optimization topology
In an out-of-path topology, one or both of the FortiGate units configured for WAN optimization are not directly in the main
data path. Instead, the out-of-path FortiGate unit is connected to FortiGate units in the data path, and the device is
configured to redirect sessions to be optimized to the out-of-path FortiGate unit. The FortiGate units in the data path use
a method such as policy routing to redirect traffic to be optimized to the out-of-path FortiGate units. The out-of-path
FortiGate units establish a WAN optimization tunnel between each other and optimize the redirected traffic.
One of the benefits of out-of-path WAN optimization is that out-of-path FortiGate units only perform WAN optimization
and do not have to process other traffic. An in-path FortiGate unit configured for WAN optimization also has to process
other non-optimized traffic on the data path.
Topology for multiple networks
As shown below, you can create multiple WAN optimization configurations between many private networks. Whenever
WAN optimization occurs, it is always between two FortiGate units, but you can configure any FortiGate unit to perform
WAN optimization with any of the other FortiGate units that are part of your WAN.
You can also configure WAN optimization between FortiGate units with different roles on the WAN. FortiGate units
configured as security devices and for WAN optimization can perform WAN optimization as if they are single-purpose
FortiGate units just configured for WAN optimization. The WAN optimization configuration is the same for FortiGate units
deployed as security devices and for single-purpose WAN optimization FortiGate units. The only differences would result
from the different network topologies.
FortiOS 7.6.2 Administration Guide 3964
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,964
|
WAN optimization
Configuration examples
The following pages are used in the WAN optimization configuration examples demonstrated in the subsequent
sections:
l WAN Opt. & Cache > Profiles: Configure the default WAN optimization profile to optimize HTTP traffic on client side.
l WAN Opt. & Cache > Peers: Change the Host ID and add Peer Host ID and IP address on both client and server
side.
l WAN Opt. & Cache > Authentication Groups: Add an authentication group for the authentication purpose on both
client and server side. (Optional)
l Policy & Objects > Firewall Policy: Add a WAN optimization firewall policy on the client side or on both client and
server side depending on the WAN optimization configuration. See the examples for more information.
FortiOS 7.6.2 Administration Guide 3965
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,965
|
WAN optimization
A WAN optimization firewall policy is a firewall policy running in Proxy-based inspection
mode with WAN Optimization enabled. A WAN optimization firewall policy cannot be
configured with inspection mode set to Flow-based.
The following topics provide instructions on different WAN optimization configuration examples:
l Manual (peer-to-peer) WAN optimization configuration example on page 3966
l Active-passive WAN optimization configuration example on page 3970
l Secure tunneling configuration example on page 3975
l Testing and troubleshooting the configuration on page 3980
Manual (peer-to-peer) WAN optimization configuration example
Please ensure that the Prerequisites on page 3950 are met before proceeding with the
configuration example.
See Manual (peer to peer) configurations on page 3959 for conceptual information.
This example configuration includes a client-side FortiGate unit called Client-Fgt with a WAN IP address of
172.20.34.12. This unit is in front of a network with IP address 172.20.120.0. The server-side FortiGate unit is called
Server-Fgt with a WAN IP address of 192.168.30.12. This unit is in front of a web server network with IP address
192.168.10.0.
This example customizes the default WAN optimization profile on the client-side FortiGate unit and adds it to the WAN
optimization firewall policy. You can also create a new WAN optimization profile.
General configuration steps
This section breaks down the configuration for this example into smaller procedures:
1. Configure the client-side FortiGate unit:
l Add peers.
l Configure the default WAN optimization profile to optimize HTTP traffic.
l Add a manual WAN optimization firewall policy.
2. Configure the server-side FortiGate unit:
l Add peers.
l Add a WAN optimization proxy policy.
FortiOS 7.6.2 Administration Guide 3966
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,966
|
WAN optimization
Configuring manual WAN optimization from the GUI
Use the following steps to configure the example configuration from the GUI:
To configure the client-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the client-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Client-Fgt
c. Click OK.
2. Create the server-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Server-Fgt
IP address 192.168.30.12
c. Click OK.
3. Go to WAN Opt. & Cache > Profiles and edit the default profile:
a. Select the default profile and click Edit.
b. Under Protocol Options, edit HTTP.
c. Set Status to Enable and click Apply.
d. Click OK.
4. Go to Policy & Objects > Firewall Policy to add a manual WAN optimization firewall policy to the client-side FortiGate
unit that accepts traffic to be optimized:
a. Click Create New.
b. Enter a Name and configure the following settings:
Incoming Interface port2
Outgoing Interface port3
Source all
Destination all
Schedule always
Service ALL
Action ACCEPT
c. Set Inspection Mode to Proxy-based.
FortiOS 7.6.2 Administration Guide 3967
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,967
|
WAN optimization
d. Enable WAN Optimization and configure the following settings:
WAN Optimization Manual
Profiles default
Peers Server-Fgt
e. Click OK to save the policy.
To configure the server-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the server-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Server-Fgt
c. Click OK.
2. Create the client-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Client-Fgt
IP address 172.20.34.12
c. Click OK.
3. Enter the following CLI command to add a WAN optimization proxy policy to accept WAN optimization tunnel
connections:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Configuring basic WAN optimization from the CLI
Use the following steps to configure the example configuration from the CLI.
To configure the client-side FortiGate unit:
1. Change the Host ID of the client-side FortiGate:
FortiOS 7.6.2 Administration Guide 3968
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,968
|
WAN optimization
config wanopt settings
set host-id Client-Fgt
end
2. Add the Host ID of the server-side FortiGate:
config wanopt peer
edit Server-Fgt
set ip 192.168.30.12
next
end
3. Edit the default WAN optimization profile and enable HTTP WAN optimization:
config wanopt profile
edit default
config http
set status enable
end
next
end
4. Add a WAN optimization firewall policy to accept the traffic to be optimized:
config firewall policy
edit 0
set srcintf port2
set dstintf port3
set srcaddr all
set dstaddr all
set action accept
set service ALL
set schedule always
set inspection-mode proxy
set wanopt enable
set wanopt-profile default
set wanopt-detection off
set wanopt-peer Server-Fgt
next
end
When you set the detection mode to off, the policy becomes a manual mode WAN optimization firewall, which is
reflected on the GUI.
To configure the server-side FortiGate unit:
1. Change the Host ID of the server-side FortiGate:
config wanopt settings
set host-id Server-Fgt
end
2. Add the Host ID of the client-side FortiGate:
config wanopt peer
edit Client-Fgt
set ip 172.20.34.12
next
end
FortiOS 7.6.2 Administration Guide 3969
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,969
|
WAN optimization
3. Add a WAN optimization proxy policy:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Active-passive WAN optimization configuration example
Please ensure that the Prerequisites on page 3950 are met before proceeding with the
configuration example.
See Active-passive configurations on page 3959 for conceptual information.
This example configuration includes a client-side FortiGate unit called Client-Fgt with a WAN IP address of
172.30.120.1. This unit is in front of a network with IP address 172.20.120.0. The server-side FortiGate unit is called
Server-Fgt and has a WAN IP address of 192.168.20.1. This unit is in front of a web server network with IP address
192.168.10.0.
General configuration steps
This section breaks down the configuration for this example into smaller procedures:
1. Configure the client-side FortiGate unit:
l Add peers.
l Add a WAN optimization profile to optimize CIFS, FTP, and HTTP traffic.
l Add an active WAN optimization firewall policy.
2. Configure the server-side FortiGate unit:
l Add peers.
l Add a passive WAN optimization firewall policy.
l Add a WAN optimization proxy policy.
FortiOS 7.6.2 Administration Guide 3970
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,970
|
WAN optimization
Configuring active-passive WAN optimization from the GUI
Use the following steps to configure the example configuration from the GUI.
To configure the client-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the client-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Client-Fgt
c. Click OK.
2. Create the server-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Server-Fgt
IP address 192.168.20.1
c. Click OK.
3. Go to WAN Opt & Cache > Profiles to add a WAN optimization profile to optimize CIFS, HTTP, and FTP traffic:
a. Select Create New.
b. Enter the profile name:
Name Custom-wan-opt-pro
c. In the Protocol Options section:
i. Edit CIFS.
ii. Set Status to Enable.
iii. Click Apply.
iv. Repeat these steps to edit and enable FTP and HTTP.
d. Click OK.
4. Go to Policy & Objects > Firewall Policy to add an active WAN optimization firewall policy:
a. Click Create New.
b. Enter a Name and configure the following settings:
Incoming Interface port2
Outgoing Interface port3
Source all
Destination all
Schedule always
Service HTTP
FTP
FortiOS 7.6.2 Administration Guide 3971
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,971
|
WAN optimization
SMB
Action ACCEPT
c. Set Inspection Mode to Proxy-based.
d. Enable WAN optimization and configure the following settings:
WAN Optimization Active
Profile Custom-wan-opt-pro
e. Click OK.
To configure the server-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the server-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Server-Fgt
c. Click OK.
2. Create the client-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Client-Fgt
IP address 172.30.120.1
c. Click OK.
3. Go to Policy & Objects > Firewall Policy to add a passive WAN optimization firewall policy:
a. Click Create New.
b. Enter a Name and configure the following settings:
Incoming Interface port4
Outgoing Interface port5
Source all
Destination all
Schedule always
Service ALL
Action ACCEPT
c. Set Inspection Mode to Proxy-based.
FortiOS 7.6.2 Administration Guide 3972
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,972
|
WAN optimization
d. Enable WAN Optimization and configure the following settings:
WAN Optimization Passive
Passive Option Default
e. Click OK.
4. Add a WAN optimization proxy policy from the CLI:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Configuring basic active-passive WAN optimization from the CLI
Use the following steps to configure the example configuration from the CLI.
To configure the client-side FortiGate unit:
1. Change the Host ID of the client-side FortiGate:
config wanopt settings
set host-id Client-Fgt
end
2. Add the Host ID of the server-side FortiGate:
config wanopt peer
edit Server-Fgt
set ip 192.168.20.1
next
end
3. Add a WAN optimization profile to optimize CIFS, HTTP, and FTP traffic:
config wanopt profile
edit Custom-wan-opt-pro
config cifs
set status enable
end
config http
set status enable
end
config ftp
set status enable
end
next
end
FortiOS 7.6.2 Administration Guide 3973
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,973
|
WAN optimization
4. Add an active WAN optimization firewall policy:
config firewall policy
edit 0
set srcintf port2
set dstintf port3
set srcaddr all
set dstaddr all
set action accept
set service HTTP FTP SMB
set schedule always
set inspection-mode proxy
set wanopt enable
set wanopt-detection active
set wanopt-profile Custom-wan-opt-pro
next
end
To configure the server-side FortiGate unit:
1. Change the Host ID of the server-side FortiGate:
config wanopt settings
set host-id Server-Fgt
end
2. Add the Host ID of the client-side FortiGate:
config wanopt peer
edit Client-Fgt
set ip 172.30.120.1
next
end
3. Add a passive WAN optimization firewall policy:
config firewall policy
edit 0
set srcintf port4
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set service ALL
set schedule always
set inspection-mode proxy
set wanopt enable
set wanopt-detection passive
set wanopt-passive-opt default
next
end
4. Add a WAN optimization proxy policy:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
FortiOS 7.6.2 Administration Guide 3974
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,974
|
WAN optimization
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Secure tunneling configuration example
Please ensure that the Prerequisites on page 3950 are met before proceeding with the
configuration example.
See Secure tunneling on page 3955 for conceptual information.
This example configuration includes a client-side FortiGate unit called Client-Fgt with a WAN IP address of
172.30.120.1. This unit is in front of a network with IP address 172.20.120.0. The server-side FortiGate unit is called
Server-Fgt and has a WAN IP address of 192.168.20.1. This unit is in front of a web server network with IP address
192.168.10.0.
General configuration steps
This section breaks down the configuration for this example into smaller procedures:
1. Configure the client-side FortiGate unit:
l Add peers.
l Add an authentication group.
l Add an active WAN optimization firewall policy.
2. Configure the server-side FortiGate unit:
l Add peers.
l Add the same authentication group.
l Add a passive WAN optimization firewall policy.
l Add a WAN optimization proxy policy.
Configuring WAN optimization with secure tunneling from the GUI
Use the following steps to configure the example configuration from the GUI.
FortiOS 7.6.2 Administration Guide 3975
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,975
|
WAN optimization
To configure the client-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the client-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Client-Fgt
c. Click OK.
2. Create the server-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Server-Fgt
IP address 192.168.20.1
c. Click OK.
3. Go to WAN Opt. & Cache > Authentication Groups to add the authentication group to be used for secure tunneling:
a. Click Create New and configure the following settings:
Name Auth-Secure-Tunnel
Authentication Method Pre-shared key
Pre-shared key ********
Accept peer(s) Defined Peers Only
b. Click OK.
4. Go to WAN Opt. & Cache > Profiles to add a WAN optimization profile that enables secure tunneling and includes
the authentication group:
a. Click Create New.
b. Enter a Name:
Name Secure-wan-opt-pro
c. Enable Authentication group:
Authentication group Auth-Secure-Tunnel
d. In the Protocol Options section, edit HTTP:
i. Set Status to Enable.
ii. Click Apply.
iii. Set SSL Secure Tunneling to Enable.
iv. Click Apply.
e. Click OK.
5. Go to Policy & Objects > Firewall Policy to add an active WAN optimization firewall policy:
a. Click Create New.
b. Enter a Name and configure the following settings:
FortiOS 7.6.2 Administration Guide 3976
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,976
|
WAN optimization
Incoming Interface port2
Outgoing Interface port3
Source all
Destination all
Schedule always
Service HTTP
Action ACCEPT
c. Set Inspection Mode to Proxy-based.
d. Enable WAN Optimization and configure the following settings:
WAN Optimization Active
Profile Secure-wan-opt-pro
e. Click OK.
To configure the server-side FortiGate unit:
1. Go to WAN Opt. & Cache > Peers and change the Host ID of the server-side FortiGate unit:
a. Click Change. The Host ID pane opens.
b. Enter a new Host ID:
Host ID Server-Fgt
c. Click OK.
2. Create the client-side FortiGate unit peer:
a. Select Create New. The New WAN Optimization Peer opens.
b. Configure the following settings:
Peer Host ID Client-Fgt
IP address 172.30.120.1
c. Click OK.
3. Go to WAN Opt. & Cache > Authentication Groups to add the authentication group to be used for secure tunneling:
a. Click Create New and configure the following settings:
Name Auth-Secure-Tunnel
Authentication Method Pre-shared key
Pre-shared key ********
Accept peer(s) Defined Peers Only
b. Click OK.
4. Go to Policy & Objects > Firewall Policy to add an passive WAN optimization firewall policy:
FortiOS 7.6.2 Administration Guide 3977
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,977
|
WAN optimization
a. Click Create New.
b. Enter a Name and configure the following settings:
Incoming Interface port4
Outgoing Interface port5
Source all
Destination all
Schedule always
Service ALL
Action ACCEPT
c. Set Inspection Mode to Proxy-based.
d. Enable WAN Optimization and configure the following settings:
WAN Optimization Passive
Passive Option Default
e. Click OK.
5. Add a WAN optimization proxy policy from the CLI:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Configuring WAN optimization with secure tunneling from the CLI
Use the following steps to configure the example configuration from the CLI.
To configure the client-side FortiGate unit:
1. Change the Host ID of the client-side FortiGate:
config wanopt settings
set host-id Client-Fgt
end
2. Add the Host ID of the server-side FortiGate:
config wanopt peer
edit Server-Fgt
set ip 192.168.20.1
FortiOS 7.6.2 Administration Guide 3978
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,978
|
WAN optimization
next
end
3. Add a new authentication group to be used for secure tunneling:
config wanopt auth-group
edit Auth-Secure-Tunnel
set auth-method psk
set peer-accept defined
set psk ********
next
end
4. Add a WAN optimization profile that enabled secure tunneling and includes the authentication group, enables HTTP
protocol optimization, and enables secure tunneling for HTTP traffic:
config wanopt profile
edit Secure-wan-opt-pro
set auth-group Auth-Secure-Tunnel
config http
set status enable
set secure-tunnel enable
end
next
end
5. Add an active WAN optimization firewall policy that enables secure tunneling:
config firewall policy
edit 0
set srcintf port2
set dstintf port3
set srcaddr all
set dstaddr all
set action accept
set service HTTP
set schedule always
set inspection-mode proxy
set wanopt enable
set wanopt-detection active
set wanopt-profile Secure-wan-opt-pro
next
end
To configure the server-side FortiGate unit:
1. Change the Host ID of the server-side FortiGate:
config wanopt settings
set host-id Server-Fgt
end
2. Add the Host ID of the client-side FortiGate:
config wanopt peer
edit Client-Fgt
set ip 172.30.120.1
next
end
FortiOS 7.6.2 Administration Guide 3979
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,979
|
WAN optimization
3. Add an authentication group to be used for secure tunneling:
config wanopt auth-group
edit Auth-Secure-Tunnel
set auth-method psk
set peer-accept defined
set psk ********
next
end
4. Add a passive WAN optimization firewall policy:
config firewall policy
edit 0
set srcintf port4
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set service ALL
set schedule always
set inspection-mode proxy
set wanopt enable
set wanopt-detection passive
set wanopt-passive-opt default
next
end
5. Add a WAN optimization proxy policy:
config firewall proxy-policy
edit 0
set proxy wanopt
set dstintf port5
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service ALL
next
end
Testing and troubleshooting the configuration
To test the configuration attempt, start a web browsing session between the client network and the web server network.
For example, from a PC on the client network browse to the IP address of a web server on the web server network, for
example http://192.168.10.13. Even though this address is not on the client network, you should be able to connect to
this web server over the WAN optimization tunnel.
If you can connect, the WAN Opt. Monitor widget should show the protocol that has been optimized (in this case HTTP)
and the Peer Monitor widget displays the Peer information. To add the WAN Opt. Monitor and the Peer Monitor, go to
Dashboard > Status > Add Widget > WAN Opt. & Cache and add WAN Opt. Monitor and Peer Monitor. See Monitoring
performance on page 3960 for more information.
If you cannot connect, try the following to diagnose the problem:
FortiOS 7.6.2 Administration Guide 3980
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,980
|
WAN optimization
l Review your configuration and make sure all details such as address ranges, peer names, and IP addresses are
correct.
l Check routing on the FortiGate units and on the client and web server networks to make sure packets can be
forwarded as required. The FortiGate units must be able to communicate with each other, routing on the client
network must allow packets destined for the web server network to be received by the client-side FortiGate unit, and
packets from the server-side FortiGate unit must be able to reach the web servers. See Routing concepts on page
446 for more information.
You can use get and diagnose commands to display information about how WAN optimization is operating.
Example output
The command output for the client-side FortiGate unit shows 10 tunnels all created by the manual WAN optimization
configuration:
# diagnose wad tunnel list
Tunnel: id=100 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=100 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=348 bytes_out=384
Tunnel: id=99 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=99 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=348 bytes_out=384
Tunnel: id=98 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=98 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=348 bytes_out=384
Tunnel: id=39 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=39 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1068 bytes_out=1104
Tunnel: id=7 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=7 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnel: id=8 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=8 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnel: id=5 type=manual
vd=0 shared=no uses=0 state=2
FortiOS 7.6.2 Administration Guide 3981
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,981
|
WAN optimization
peer name=Server-Fgt id=5 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnel: id=4 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=4 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnel: id=1 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=1 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnel: id=2 type=manual
vd=0 shared=no uses=0 state=2
peer name=Server-Fgt id=2 ip=192.168.30.12
SSL-secured-tunnel=no auth-grp=
bytes_in=1228 bytes_out=1264
Tunnels total=10 manual=10 auto=0
The command output shows three tunnels all created by the active-passive WAN optimization configuration:
# diagnose wad tunnel list
Tunnel: id=22 type=auto
vd=0 shared=no uses=1 state=2
peer name=Server-Fgt id=42 ip=192.168.20.1 (best guess)
SSL-secured-tunnel=no auth-grp=
bytes_in=56693 bytes_out=10831
Tunnel: id=24 type=auto
vd=0 shared=no uses=1 state=2
peer name=Server-Fgt id=44 ip=192.168.20.1 (best guess)
SSL-secured-tunnel=no auth-grp=
bytes_in=14833 bytes_out=3896
Tunnel: id=26 type=auto
vd=0 shared=no uses=1 state=2
peer name=Server-Fgt id=46 ip=192.168.20.1 (best guess)
SSL-secured-tunnel=no auth-grp=
bytes_in=481 bytes_out=176
Tunnels total=3 manual=0 auto=3
The command output shows a tunnel created by active passive WAN optimization configuration with secure tunneling:
# diagnose wad tunnel list
Tunnel: id=3 type=auto
vd=0 shared=no uses=1 state=2
peer name=Server-Fgt id=49 ip=192.168.20.1 (best guess)
SSL-secured-tunnel=yes auth-grp=Auth-Secure-Tunnel
bytes_in=95810 bytes_out=39597
FortiOS 7.6.2 Administration Guide 3982
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,982
|
WAN optimization
Tunnels total=1 manual=0 auto=1
Unlike manual mode, for active-passive configurations, each session will negotiate an activepassive tunnel so an open session is required the display the corresponding output above.
For example, continuous data transfer such as uploading or downloading will display tunnel
output in the active-passive configuration, which is in contrast to manual mode where tunnels
are always open and ready to use.
FortiOS 7.6.2 Administration Guide 3983
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,983
|
VM
This section contains topics on deploying FortiGate-VM:
l Amazon Web Services on page 3984
l Microsoft Azure on page 3984
l Google Cloud Platform on page 3984
l OCI on page 3985
l AliCloud on page 3985
l Private cloud on page 3985
l VM license on page 3985
l Permanent trial mode for FortiGate-VM on page 3992
l Adding VDOMs with FortiGate v-series on page 3995
l PF and VF SR-IOV driver and virtual SPU support on page 3998
l Using OCI IMDSv2 on page 4000
l FIPS cipher mode for AWS, Azure, OCI, and GCP FortiGate-VMs on page 4002
l Cloud-init on page 4004
l TPM support for FortiGate-VM on page 4007
Amazon Web Services
See the FortiOS 7.6.2 AWS Administration Guide.
Microsoft Azure
See the FortiOS 7.6.2 Azure Administration Guide.
For Azure vWAN deployments, see:
l Azure vWAN NGFW Deployment Guide
l Azure vWAN SD-WAN NGFW Deployment Guide
Google Cloud Platform
See the 7.6.2 FortiOS GCP Administration Guide.
FortiOS 7.6.2 Administration Guide 3984
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,984
|
VM
OCI
See the 7.6.2 FortiOS OCI Administration Guide.
AliCloud
See the 7.6.2 FortiOS AliCloud Administration Guide.
Private cloud
See FortiGate Private Cloud in the document library.
VM license
You can access FortiGate VM License from Dashboard > Status in the Virtual Machine widget. Click the device license
and select FortiGate VM License.
FortiGate VM License displays the following information:
Field Description
License status Displays one of the following statuses:
l Valid: VM can connect and validate the license against a FortiManager or
FortiGuard server. All features are available.
l Validation overdue: VM cannot connect and validate against a FortiManager
or FortiGuard server. A check is made against how many days the warning
status is continuous. If the number is less than 30 days, the status does not
change. You may be seeing this status because the network environment
does not allow the FortiGate-VM to connect to the FortiGuard server within
30 days.
l 30 day Grace Period: license is expired but within the 30-day grace period.
Check the expiration date for evaluation or term-based licenses.
l Duplicate copy: license is a duplicate copy. FortiGuard returns code 401 and
FortiOS sets the license status as an invalid copy. FortiGate firewall policy
continues to work during this state. If the FortiGate keeps the duplicate copy
status for more than 24 hours, the status changes to invalid.
As you cannot access Dashboard > Status in the Virtual Machine widget when the
license is in one of the following statuses, they do not display in the License status
field:
l Invalid: VM cannot connect and validate against a FortiManager or
FortiGuard server. A check is made against how many days the warning
FortiOS 7.6.2 Administration Guide 3985
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,985
|
VM
Field Description
status is continuous. If the number is 30 days or more, the status changes to
invalid. This status also occurs if the duplicate copy status persists for more
than 24 hours. FortiOS restricts GUI access until you upload a valid license.
Firewall policies do not work. FortiGuard downloads are unavailable. When
the status is invalid, upon login, FortiOS redirects you to the VM license
upload page.
Reasons for having an invalid status include:
l The VM license is expired and has passed the grace period.
l Another VM has been already validated with FortiGuard using the same
license. See Technical Note: VM License activation for details about
duplicated VM instances.
l Pending: temporary state where the VM attempts to validate its license. The
GUI displays a loading page with the message License is being validated by
FortiGuard.
Allocated vCPUs Number of allocated and total allowable vCPUs
Allocated RAM Amount of allocated RAM. There are no RAM restrictions.
Expires on Expiry date (value depends on the type of license)
This information is visible in the CLI by running get system status. See CLI troubleshooting.
Uploading a license file
After you submit an order for a FortiGate-VM, Fortinet sends a license registration code to the email address that you
entered in the order form. Use this code on the FortiCloud portal to register the FortiGate-VM.
Once you have registered the VM, you can download the license file in .LIC format. In FortiGate VM License, click
Upload. The system prompts you to reboot and validate the license with the FortiGuard server. Once validated, your
FortiGate-VM is fully functional.
The VM license window may also appear immediately after logging in if you are running a VM with an evaluation license
that has expired.
In cases where the GUI is inaccessible, you can upload the license using secure copy (SCP).
For information about injecting FortiFlex licenses, see Injecting the FortiFlex license.
To upload the license using SCP:
1. Enable SCP:
config system global
set admin-scp enable
end
FortiOS 7.6.2 Administration Guide 3986
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,986
|
VM
2. Enable SSH in the administrative access for the interface where the transfer will take place:
config system interface
edit <interface>
append allowaccess ssh
next
end
3. On your computer, upload the VM license. This example is for Linux:
scp <filename> <admin-user>@<FortiGate_IP>:vmlicense
VM license types
FortiGate-VM offers perpetual licensing (normal series and V-series) and annual subscription licensing (S-series). SKUs
are based on the number of vCPUs (1, 2, 4, 8, 16, 32, or unlimited).
FortiGate-VM has a permanent trial license. See Permanent trial mode for FortiGate-VM on page 3992.
The FortiFlex program allows qualified enterprise and MSSP customers to create as many VM entitlements as required.
Resource consumption is based upon predefined points that are calculated on a daily basis. See Program guide.
Feature VM-Series Trial V-series S-series FortiFlex
Licensing
and support
The VM base
is perpetual.
You must
purchase
separately
FortiGuard
and
FortiCare
services on
an annual
basis. See
the price list
for details.
Hardware
configuration
restrictions
apply. Support
is not available.
The VM base
is perpetual.
You must
purchase
separately
FortiGuard
and
FortiCare
services on
an annual
basis. See
the price list
for details.
Single annually
contracted SKU that
contains a VM base
and a
FortiCare/FortiGuard
service bundle. Service
bundles and a la carte
services are available.
Annually contracted
program to create
multiple sets of a single
entitlement per VM.
Entitlements contain a
VM base and
FortiCare/FortiGuard
bundle. Service
bundles and a la carte
services are available.
FortiOS 7.6.2 Administration Guide 3987
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,987
|
VM
Feature VM-Series Trial V-series S-series FortiFlex
vCPU
number
upgrade or
downgrade
Not
supported. Not supported.
Not
supported.
Supported via co-term.
You can also upgrade
the service bundle.
Contact a Fortinet
sales representative to
upgrade.
Natively supported via
the scale up/down
feature.
VDOM
support
By default,
each CPU
level
supports up
to a certain
number of
VDOMs. See
the
FortiGateVM data
sheet for
default limits.
VDOMs are
supported, but
restricted by
the CPU
allowance for
the trial license.
By default, all CPU
levels do not support
adding VDOMs, but
you can add additional
VDOMs via a
subscription VDOM
license.
By default, all CPU
levels do not support
adding VDOMs, but
you can add additional
VDOMs via the scale
up/down feature.
Applying a FortiFlex token
You can apply a FortiFlex token in the FortiGate VM License page for the following VM instance types:
l Newly deployed or expired FortiGate-VM instances. After logging into the FortiOS GUI, a FortiFlex token option is
available when the license popup appears.
l Already licensed FortiGate-VM instances. You can go to this page from the Virtual Machine dashboard widget or
from System > FortiGuard. FortiFlex token option is available for migrating into FortiFlex.
Consuming a new vCPU
FortiGate-VM supports automatic vCPU hot-add/hot-remove to the limit of the license entitlement after activating an Sseries license or a FortiFlex license. This enhancement removes the requirement of running the CLI command execute
cpu add or performing a reboot when the FortiGate-VM has a lower number of vCPUs allocated than the licensed
number of vCPUs.
CLI troubleshooting
In some cases, you can view more information from the CLI to diagnose issues with VM licensing. This is also useful
when the GUI is inaccessible due to an invalid contract.
Before you begin, ensure your FortiGate has the proper routes to connect to the internet. Run all following debug
commands for a full picture of the issue.
FortiOS 7.6.2 Administration Guide 3988
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,988
|
VM
To view the license status, expiration date, and VM resources:
# get system status
Version: FortiGate-VM64-KVM v7.6.2,buildXXXX,200730 (GA)
...
Serial-Number: FGVM08**********
....
License Status: Valid
License Expiration Date: 2025-12-10
VM Resources: 1 CPU/8 allowed, 2010 MB RAM
...
To display license details:
# diagnose debug vm-print-license
SerialNumber: FGVM08**********
CreateDate: Tue Dec 10 00:57:32 2019
License expires: Thu Dec 10 00:00:00 2025
Expiry: 366
Key: yes
Cert: yes
Key2: yes
Cert2: yes
Model: 08 (11)
CPU: 8
MEM: 2147483647
To display license information from FortiGuard:
# diagnose hardware sysinfo vm full
UUID: abbe****************************
valid: 1
status: 1
code: 200
warn: 0
copy: 0
received: 4604955037
warning: 4600905081
recv: 202009152207
dup:
Field Value Description
valid
0 Invalid
1 Valid
FortiOS 7.6.2 Administration Guide 3989
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,989
|
VM
Field Value Description
status
0 Startup
1 Success
2 Warning
3 Error
4 Invalid copy
5 Evaluation license expired
6
Grace period. For FortiFlex, there is a two-hour grace
period to begin passing traffic upon retrieving the license
from FortiCloud.
code
2xx, 3xx Success
200 Valid
202 Accepted (treated as correct response code)
4xx Error
400 Expired
401 Duplicate
5xx, 500 Warning
502 Invalid. Cannot connect to FortiGuard distribution servers
6xx Evaluation license expired
Other codes Error
The following are examples of common combinations:
Combination Indicates...
valid: 1
status: 1
code: 200
License is valid and functioning normally.
valid: 1
status: 4
code: 401
License is valid but running on a duplicate instance.
valid: 0
status: 2
code: 502
System cannot connect to FortiGuard.
valid: 0
status: 3
code: 400
License is expired and invalid.
FortiOS 7.6.2 Administration Guide 3990
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,990
|
VM
Combination Indicates...
valid: 0
status: 3
code: 0
VM is unlicensed.
For FortiFlex licenses, the following command allows you to enter the license token and proxy information:
# execute vm-license <token> https://<username>:<password>@<proxy IP address>:<proxy port>
FortiOS can receive the following error codes from the FortiCare server:
1 - Runtime error (server unhandled error on FortiCare sever)
57 - License Token is invalid
58 - License Token is already used and cannot be used again to retrieve license key
The FortiGate can generate the following error code:
60 - Failed to request forticare license. Failed to download VM license.
Contact Fortinet Support for assistance if your licensing issue persists.
Customizing the FortiFlex license token activation retry parameters
FortiOS supports the customization of the retries for FortiFlex license token activation. You can configure the token
activation number of retries and the interval between each attempt using the following commands, respectively:
execute vm-license-options count <integer>
execute vm-license-options interval <interval length in seconds>
If you set vm-license-options count to zero, the token activation retries indefinitely until
success.
To define the FortiFlex token activation parameters:
1. Set the number of retries allowed:
execute vm-license-options count 4
2. Set the retry interval:
execute vm-license-options interval 5
3. Activate the license. FortiOS requests the FortiFlex license token four times, with an interval of five seconds in
between, as set.
l If FortiOS cannot verify the license within the set amount of retries, the download fails:
# execute vm-license F4FC697D65428013FAKE
This operation will reboot the system !
Do you want to continue? (y/n)y
Requesting FortiCare license token: *******, proxy:(null)
Requesting FortiCare license token: *******, proxy:(null)
Requesting FortiCare license token: *******, proxy:(null)
FortiOS 7.6.2 Administration Guide 3991
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,991
|
VM
Requesting FortiCare license token: *******, proxy:(null)
Failed to download VM license.
l If FortiOS can verify the license within the set number of retries, FortiOS successfully installs the VM license:
# execute vm-license 227602862F7E6E9XXXX
This operation will reboot the system !
Do you want to continue? (y/n)y
Requesting FortiCare license token: *******, proxy:(null)
VM license install succeeded. Rebooting firewall.
You can also define FortiFlex token activation parameters in an ISO file using the mime user-data.
To define the parameters in an ISO file:
1. Create a config drive ISO with a MIME file:
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="license.txt
"LICENSE-TOKEN: 334ADF7B49F2FEC1XXXX INTERVAL: 5 COUNT: 4
See Cloud-init using config drive for more information.
2. Attach the ISO config drive at boot time. See Cloud-init for more information.
3. Boot up the VM and verify the token activation parameters:
# diagnose debug cloudinit show
>> Found config drive /dev/sr0
>> Successfully mount config drive
>> MIME parsed preconfig script
>> MIME parsed VM token
>> MIME parsed config script
>> Found metadata source: config drive
>> Run preconfig script
>> FortiGate-VM64 conf sys global
…
>> Trying to install vmlicense ...
>> License-token:334ADF7B49F2FEC1XXXX INTERVAL:5 COUNT:4
>> Run config script
Permanent trial mode for FortiGate-VM
FortiGate-VM has a permanent evaluation VM license. The evaluation VM license applies to all private cloud (VMware
ESXi, KVM, and so on) and all bring your own license (BYOL) public cloud instances.
When spinning up a new FortiGate-VM, you choose to log in to FortiCloud to activate the VM trial or upload a new
license.
Limitations of the evaluation VM license include the following:
l Maximum of one free evaluation copy per FortiCloud account
l Support for low encryption operation only, except for GUI management access and FortiManager communications
FortiOS 7.6.2 Administration Guide 3992
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,992
|
VM
l Maximum of 1 CPU and 2 GB of memory
l Maximum of three interfaces, firewall policies, and routes
l No FortiCare support
l No FortiGuard support
l Support for a maximum of two virtual domains (VDOM). When using multi-VDOM mode, the root VDOM must be an
admin type and the other can be a traffic VDOM. See VDOM types on page 3075.
To obtain the permanent VM trial license from FortiCare using the CLI:
1. A newly deployed FortiGate-VM no longer has a valid evaluation license, even if the instance has only 1 CPU and 2
GB of memory. Run get sys stat. The following output is expected:
Version: FortiGate-VM64 v7.6.2,buildXXXX,220715 (interim)
...
Serial-Number: FGVMEVNXFLTGKOBC
License Status: Invalid
VM Resources: 1 CPU/1 allowed, 2007 MB RAM/2048 MB allowed
2. Obtain the permanent VM trial license from FortiCare:
execute vm-license-options account-id xxxx@fortinet.com
execute vm-license-options account-password xxxxxxx
execute vm-license
This VM is using the evaluation license. This license does not expire.
Limitations of the Evaluation VM license include:
1.Support for low encryption operation only
2.Maximum of 1 CPU and 2GiB of memory
3.Maximum of three interfaces, firewall policies, and routes each
4.No FortiCare Support
This operation will reboot the system !
Do you want to continue? (y/n)y
Connection to 10.6.30.74 closed.
3. You can run the following commands to check that the permanent VM trial license is valid:
l get system status. The following output is expected:
Version: FortiGate-VM64 v7.6.2,buildXXXX,220715 (interim)
...
Serial-Number: FGVMEVNXFLTGKOBC
License Status: Valid
VM Resources: 1 CPU/1 allowed, 2007 MB RAM/2048 MB allowed
l diagnose hardware sysinfo vm full. The following output is expected:
UUID: 4213dbbc94f2520b0d75eeafe1b319c7
valid: 1
status: 1
code: 0
warn: 0
copy: 0
received: 4294939472
warning: 4294939472
recv: 202207162014
dup:
FortiOS 7.6.2 Administration Guide 3993
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,993
|
VM
l diagnose debug vm-print-license. The following output is expected:
SerialNumber: FGVMEVNXFLTGKOBC
CreateDate: Sat Jul 16 20:11:15 2022
UUID: 4213dbbc94f2520b0d75eeafe1b319c7
Key: yes
Cert: yes
Key2: yes
Cert2: yes
Model: EVAL (1)
CPU: 1
MEM: 2048
VDOM license:
permanent: 2
subscription: 0
To obtain the permanent VM trial license from FortiCare using the GUI:
1. When unlicensed, the FortiOS GUI allows you to download the permanent VM trial license from FortiCare with your
FortiCare account credentials. In the FortiGate VM License page, for How will you license this VM?, select
Evaluation License.
2. In the Email field, enter your FortiCare account email address.
3. In the Password field, enter your FortiCare account password.
4. Click OK. When a permanent VM trial license is applied, the FortiOS, the GUI shows a summary of the license
FortiOS 7.6.2 Administration Guide 3994
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,994
|
VM
limitations and allows you to upload a paid VM license.
To allow FortiManager to apply a license to an unlicensed FortiGate-VM instance:
1. Confirm that the FortiGate is unlicensed by running get system status in the FortiOS CLI. The following shows
expected output for this command:
Version: FortiGate-VM64-AZURE v7.6.2,buildXXXX,220728 (interim)
...
Serial-Number: FGVMEVTN8UP4KIA6
License Status: Invalid
VM Resources: 1 CPU/1 allowed, 1945 MB RAM/2048 MB allowed
2. In the FortiOS CLI, configure the FortiManager as central management:
config system central-management
set type fortimanager
set fmg "<FortiManager IP address>"
end
3. In FortiManager, configure the VM license as Installing VM licenses on managed devices describes.
Adding VDOMs with FortiGate v-series
Each FortiGate-VM base license type allows a default number of virtual domains (VDOM). This topic provides sample
procedures to add VDOMs beyond the default number using separately purchased VDOM licenses.
This topic consists of the following steps:
1. Activate the FortiGate-VM with the base license.
2. Add more VDOMs to the FortiGate-VM.
FortiOS 7.6.2 Administration Guide 3995
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,995
|
VM
To activate the FortiGate-VM with the base license:
1. Purchase and register the FortiGate-VM base license in FortiCare:
a. Purchase the FortiGate-VM base license from Fortinet or a Fortinet reseller.
b. You receive a license certification with a registration code. Open the certification.
c. Log in to Fortinet Customer Service & Support.
d. Go to Register Now and enter the provided registration code.
e. Follow the registration process. The serial number generates and displays on the Registration Completion
page.
f. Go to Asset > Manage/View Products. Click the serial number to download the license file.
2. Upload the FortiGate-VM base license file to FortiOS:
a. Log in to the FortiGate-VM GUI.
b. In Dashboard > Status, in the Virtual Machine widget, click FortiGate VM License.
c. Click the Upload button.
d. Select the FortiGate-VM base license file, then click OK. The FortiGate-VM reboots after applying the base
license.
3. Verify the FortiGate-VM base license status and VDOM information:
a. Log in to the FortiGate-VM GUI.
b. In Dashboard > Status, in the Virtual Machine widget, ensure that there is a checkmark in front of the FortiGateVM base license name. The checkmark indicates that the base license is valid.
c. You can check VDOM information using the CLI. The following output shows that the maximum number of
VDOMs is currently one. This is correct since the FortiGate-VM base license only supports the default root
VDOM that the system uses.
To add more VDOMs to the FortiGate-VM:
You can repeat this procedure multiple times to stack multiple VDOM licenses on the same FortiGate-VM.
1. Purchase and register the FortiGate-VM upgrade license in FortiCare. This example adds 15 VDOMs:
a. Purchase the FortiGate-VM upgrade license from Fortinet or a Fortinet reseller.
b. You receive a license certification with a registration code. Open the certification.
c. Log in to Fortinet Customer Service & Support.
d. Go to Asset > Register/Activate and enter the provided registration code.
e. On the Specify License Confirmation Information screen, enter the FortiGate-VM serial number to apply the
VDOM upgrade license to the FortiGate-VM. In this example, the FortiGate-VM serial number is
FGVM4VTM19000476.
f. Follow the registration process.
g. Go to Asset > Manage/View Products > . Select the desired product, then click License & Key. The VDOM
upgrade license displays under Registered License(s), and a key for adding 15 VDOMs (in this example
FortiOS 7.6.2 Administration Guide 3996
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,996
|
VM
M6JSD-8EE32-VHIJB-N) displays under Available Key(s).
2. Apply the FortiGate-VM upgrade license key to FortiOS:
a. Log in to the FortiGate-VM CLI in the local console or using SSH.
b. Apply the VDOM upgrade license key:
FGVM4VTM19000476 # execute upd-vd-license M6JSD-8EE32-VHIJB-N
update vdom license succeeded
3. Verify the FortiGate-VM VDOM information:
a. Log in to the FortiGate-VM CLI in the local console or using SSH.
b. Check VDOM information using the CLI. The following output shows that the maximum number of VDOMs is
currently 15. When you add VDOMs for the first time on a FortiGate-VM v-series instance, FortiOS does not
count the default VDOM, as the default VDOM is the so-called root VDOM that the system uses and FortiOS
does not treat it as a countable VDOM in terms of VDOM addition. Therefore, as in this example, if your
FortiGate-VM had the default VDOM configuration, then you add 15 VDOMs, FortiOS displays the maximum
VDOM number as 15, not 16.
# get system status
Version: FortiGate-VM64-KVM v6.4.4,build1803,201209 (GA)
Virus-DB: 82.00644(2020-12-18 12:20)
Extended DB: 82.00644(2020-12-18 12:20)
Extreme DB: 1.00000(2018-04-09 18:07)
IPS-DB: 16.00982(2020-12-17 01:04)
IPS-ETDB: 0.00000(2001-01-01 00:00)
APP-DB: 16.00982(2020-12-17 01:04)
INDUSTRIAL-DB: 6.00741(2015-12-01 02:30)
Serial-Number: FGVM02TM20000000
IPS Malicious URL Database: 2.00862(2020-12-18 06:12)
License Status: Invalid Copy
License Expiration Date: 2021-10-02
VM Resources: 2 CPU/2 allowed, 2010 MB RAM
Log hard disk: Available
Hostname: FGDocs
Private Encryption: Disable
Operation Mode: NAT
Current virtual domain: root
Max number of virtual domains: 1
Virtual domains status: 1 in NAT mode, 0 in TP mode
Virtual domain configuration: disable
FIPS-CC mode: disable
FortiOS 7.6.2 Administration Guide 3997
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,997
|
VM
Current HA mode: standalone
Branch point: 1803
Release Version Information: GA
FortiOS x86-64: Yes
System time: Fri Dec 25 13:24:20 2020
PF and VF SR-IOV driver and virtual SPU support
Physical function (PF) and virtual function (VF) PCI Passthrough and SR-IOV drivers in FortiGate guest VM are
supported.
PF provides the ability for PCI Passthrough, but requires an entire Network Interface Card (NIC) for a VM. It can usually
achieve greater performance than a Virtual Function (VF) based SR-IOV. PF is also expensive. While VF allows one NIC
to be shared among multiple guests VMs, PF is allocated to one port on a VM.
The supported driver versions are:
Driver Version Hypervisor
PCIPassthrough/SRIOV
vSPU (Inguest
DPDK)
Note
ixgbe 5.3.7
ESXi, KVM Yes
Yes
Ixgbevf 4.3.5
FortiOS 7.6.2 Administration Guide 3998
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,998
|
VM
Driver Version Hypervisor
PCIPassthrough/SRIOV
vSPU (Inguest
DPDK)
Note
i40e 2.12.6
Yes
i40evf 3.6.15
Available in FortiOS
6.4.0 and earlier
versions.
Iavf 4.5.3
Replaces i40evf
in FortiOS 6.4.1 and
later versions. Supports
Intel E810-C 100G
adapters.
Mlx5 24.04-0.6.6
Supports Nvidia
ConnectX-5 and
ConnectX-6 100G
adapters.
Bnxt_en
1.10.1-
216.0.416.1
Available
in FortiOS 6.4.3 and
later versions. Supports
Broadcom P2100G
100G adapters.
Vmxnet3 1.4.16.0-kNAPI ESXi
The combination of
VMware ESXi and
NSX-T does not
support virtual SPU
(vSPU).
ICE 1.9.11 ESXi, KVM Yes No
Added support to Intel
25GbE E-810 card and
its variants (E810-
XXVDA2 and E810-
XXVDA4)
Other hypervisors, such as Xen or Microsoft Hyper-V, may work with vSPU, although they are
unverified.
All tools and software utilities for UEFI 1.X have been removed from 6.2.0 and later releases.
Update to UEFI 2.x to use the UEFI tools or software utilities.
You perform the configuration to use PF or VF on the hypervisor, and do not configure it on the FortiGate.
FortiOS 7.6.2 Administration Guide 3999
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,999
|
VM
To check what driver is being used on the FortiGate:
# diagnose hardware deviceinfo nic port2
Name: port2
Driver: i40e
Version: 2.4.10
Bus: 0000:03:00.0
Hwaddr: 3c:fd:fe:1e:98:02
Permanent Hwaddr:3c:fd:fe:1e:98:02
State: up
Link: up
Mtu: 1500
Supported: auto 1000full 10000full
Advertised: auto 1000full 10000full
Auto: disabled
Rx packets: 0
Rx bytes: 0
Rx compressed: 0
...
Using OCI IMDSv2
OCI IMDSv2 offers increased security for accessing instance metadata compared to IMDSv1. IMDSv2 is used in OCI
SDN connectors and on instance deployments with bootstrap metadata. When upgrading from previous FortiOS builds
with legacy IMDSv1 endpoints, the endpoints will be updated to IMDSv2, and the same calls can be made.
The following use cases illustrate IMDSv2 support on the FortiGate-VM.
To configure the Oracle OCI instance to use IMDSv2:
1. In OCI, deploy an instance using IMDSv2 with bootstrap metadata. There are two methods to enable IMDSv2 :
l Use the OCI command line to deploy an instance using user-data. This example uses a MIME file that
contains the license and configuration, as well as a JSON file that specifies to disable V1 metadata.
oci compute instance launch
--availability-domain wwwl:US-ASHBURN-AD-1
--compartment-id
ocid1.tenancy.oc1..aaaaaaaaaaa3aaaaaaaaaaaaaaaaa7xxxxxxx54aaaaaa4xxxxxxxx55xxxa
--display-name fos-byol-v6.4.6-b2290-emulated
--image-id
ocid1.image.oc1.iad.aaaaaaaa6xxx43xxxxxxxxx7aaaaaaaaaaaaaaaaaaaa3xxxxxxxxxxxxxxx
--subnet-id
ocid1.subnet.oc1.iad.aaaaaaaaxxxxxxxxx2xxxxxxxxxxxxxxxxxxxx5aaa4xxxxxxxxxxxx42aaa
--shape VM.Standard1.4
--assign-public-ip true
--user-data-file /home/oci/userdata/mime.txt
--ssh-authorized-keys-file /home/oci/userdata/myfirstkeypair.pub
--instance-options file://home/oci/scripts/metadatav2.json
root@mail:/home/oci/scripts# cat metadatav2.json
{
"areLegacyImdsEndpointsDisabled": true
}
FortiOS 7.6.2 Administration Guide 4000
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,000
|
VM
l While the instance is running, edit the instance metadata service version in the GUI ,and change the allowed
IMDS version to VERSION 2 ONLY (see Getting Instance Metadata in the OCI documentation).
2. The FortiGate will use the metadata v2 endpoints to get the metadata bootstrap information. In FortiOS, verify this
by running the following after bootup:
# diagnose debug cloudinit show
To configure an SDN connector with meta-IAM enabled and firewall addresses to obtain dynamic
addresses:
1. Configure an IAM policy and dynamic group (see How Policies Work and Managing Dynamic Groups in the OCI
documentation).
FortiOS 7.6.2 Administration Guide 4001
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,001
|
VM
2. In FortiOS, configure the OCI Fabric connector (see OCI SDN connector using certificates on page 3755 for
detailed instructions):
a. Create the SDN connector.
b. Verify that the OCI connector comes up (Security Fabric > External Connectors page indicates the status is
up).
c. Configure a dynamic firewall address with a filter.
d. Verify the dynamic firewall address is resolved by the SDN connector.
To manually update the external IP:
# execute update-eip
instance: fos-byol-v6.4.6-b2290-emulated
vnic0: fos-byol-v6.4.6-b2290-emulated
10.0.0.58 (129.213.138.192)
port1: 10.0.0.58, eip: 129.213.138.192
EIP is updated successfully
To verify the OCI daemon debugs related to metadata:
# diagnose test application ocid 4
instance: fos-byol-v6.4.6-b2290-emulated
vnic0: fos-byol-v6.4.6-b2290-emulated
10.0.0.58
# diagnose test application ocid 5
Compartment
Id:ocid1.tenancy.oc1..aaaaaaaaaaa3aaaaaaaaaaaaaaaaa7xxxxxxx54aaaaaa4xxxxxxxx55xxxa
Instance Id:ocid1.instance.oc1.iad.axxxxxxxxxxxxxxxxxxx4aaaaa5aaaaaaaaa4xxxxxxx2aaaaaaaa
Instance Name:fos-byol-v6.4.6-b2290-emulated
OCI Regarxiehlion:us-ashburn-1
# diagnose test application ocid 6
Instance Principal Token has been refreshed
FIPS cipher mode for AWS, Azure, OCI, and GCP FortiGate-VMs
AWS, Azure, OCI, and GCP FortiGate-VMs support FIPS cipher mode. You must remove all VPN configurations before
you can enable FIPS CC mode.
FIPS cipher mode only allows a restricted set of ciphers for features that require encryption, such as SSH, IPsec and
SSL VPN, and HTTPS. You cannot use insecure protocols such as Telnet, TFTP, and HTTP to access the FortiGateVM.
You must perform a factory reset to disable fips-ciphers mode.
To enable fips-cipher mode:
config system fips-cc
set status fips-ciphers
end
Warning: entering fips-ciphers mode. To exit this mode, factory reset is required.
Do you want to continue? (y/n) y
FortiOS 7.6.2 Administration Guide 4002
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,002
|
VM
FIPS-CC cipher mode is silently enabled when configured via cloud-init.
The following behavior occurs when you enable FIPS cipher mode:
l You can restore a license, image, configuration, and so on from an FTP server.
l The following options are available:
SSH algorithms l aes128-gcm@openssh.com
l aes256-gcm@openssh.com
l hmac-sha2-256
l hmac-sha2-512
IKE/IPsec phase1 proposals l aes128-sha256
l aes128-sha256
l aes128-sha384
l aes128-sha384
l aes128-sha512
l aes128-sha512
l aes128gcm-prfsha256
l aes128gcm-prfsha256
l aes128gcm-prfsha384
l aes128gcm-prfsha384
l aes128gcm-prfsha512
l aes128gcm-prfsha512
l aes256-sha256
l aes256-sha256
l aes256-sha384
l aes256-sha384
l aes256-sha512
l aes256-sha512
l aes256gcm-prfsha256
l aes256gcm-prfsha256
l aes256gcm-prfsha384
l aes256gcm-prfsha384
l aes256gcm-prfsha512
l aes256gcm-prfsha512
IKE/IPsec phase2 proposals l aes128-sha256
l aes128-sha256
l aes128-sha384
l aes128-sha384
l aes128-sha512
l aes128-sha512
l aes128gcm
l aes128gcm
l aes256-sha256
l aes256-sha256
l aes256-sha384
FortiOS 7.6.2 Administration Guide 4003
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,003
|
VM
l aes256-sha384
l aes256-sha512
l aes256-sha512
l aes256gcm
l aes256gcm
IKE/IPsec DH groups l Default = 19, or any three from 14 - 21, 27 - 32
HTTPS for admin and SSL
VPN (with RSA server
certificate) TLS suites
PFS:
l TLS_AES_256_GCM_SHA384
l ECDHE-RSA-AES256-GCM-SHA384
l DHE-RSA-AES256-GCM-SHA384
l TLS_AES_128_GCM_SHA256
l ECDHE-RSA-AES128-GCM-SHA256
l DHE-RSA-AES128-GCM-SHA256
Elliptic curves:
l prime256v1
l secp384r1
l secp521r1
DH group:
l RFC3526/Oakley group 14 (2048 bits)
HTTPS for admin and SSL
VPN (with ECC server
certificate) TLS suites
PFS:
l TLS_AES_256_GCM_SHA384
l ECDHE-ECDSA-AES256-GCM-SHA384
l TLS_AES_128_GCM_SHA256
l ECDHE-ECDSA-AES128-GCM-SHA256
Elliptic curves:
l prime256v1
l secp384r1
l secp521r1
l The FortiCare license is validated.
l FortiGuard databases and engines are updated.
l The DH-RSA-AES128-GCM-SHA256 and DH-RSA-AES256-GCM-SHA384 ciphers are not supported.
Cloud-init
You can use cloud-init to preconfigure a FortiGate-VM instance before bootup using a text file. For example, you can
include a license or configuration information in the cloud-init file, so that the license and configuration is already present
on the FortiGate-VM after initialization. All FortiGate-VM public and private cloud platforms support cloud-init. You can
provide the cloud-init file when initializing the FortiGate-VM through the GUI of your desired cloud platform.
When providing FortiOS configuration in the cloud-init text file, you can include a full backed up FortiOS configuration or
a partial configuration. For a partial configuration, provide the configuration in the form of CLI commands. The example
in this topic includes a partial configuration that consists of the following CLI commands:
FortiOS 7.6.2 Administration Guide 4004
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,004
|
VM
config system global
set hostname mimecheck
set admintimeout 480
end
config system admin
edit admin
set password 12345678
end
The following shows the content of an example cloud-init MIME file that includes the FortiGate-VM license and some
configuration. The example omits most of the license file content for security purposes:
Content-Type: multipart/mixed; boundary="===============0740947994048919689=="
MIME-Version: 1.0
--===============0740947994048919689==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="config"
config system global
set hostname mimecheck
set admintimeout 480
end
config system admin
edit admin
set password 12345678
end
--===============0740947994048919689==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="license"
-----BEGIN FGT VM LICENSE-----
QAAAAM9mmdw0/C5oquSAhgYYurEyOAeTChjuEt8NlvQZszsj6FMpzv9FFLl8DuV8
C7JSP1JqFSjTEeSLa/crtO84Df7gGQAAgZ3RwxjOeKPEgl4i4cQKpcECVcXM4hcb
...
uqoVJ7Nca1B4mZUE3v4BuO07fZZJCdO2
-----END FGT VM LICENSE-----
--===============0740947994048919689==--
To debug the cloud-init configuration, use the diagnose debug cloud-init show command. The following shows
example output for this command:
>> Checking metadata source config drive
>> Found config drive /dev/sr0
>> Successfully mount config drive
>> MIME parsed preconfig script
>> Found metadata source: config drive
>> Trying to install vmlicense ...
>> Run config script
>> FGVMULTM12345678 $
>> FGVMULTM12345678 $ config system global
FortiOS 7.6.2 Administration Guide 4005
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,005
|
VM
>> FGVMULTM12345678 (global) $ set hostname vFGTvm00
>> FGVMULTM12345678 (global) $ end
>> vFGTvm00 $ config system admin
>> vFGTvm00 (admin) $ edit admin
>> vFGTvm00 (admin) $ set password 12345678
>> vFGTvm00 (admin) $ end
>> vFGTvm00 $
>> vFGTvm00 $ config system interface
>> vFGTvm00 (interface) $ edit port1
>> vFGTvm00 (port1) $ set mode static
>> vFGTvm00 (port1) $ set ip 10.6.30.169/24
>> vFGTvm00 (port1) $ set allowaccess ping https ssh snmp http telnet fgfm radius-acct
probe-response ftm
>> vFGTvm00 (port1) $ next
>> vFGTvm00 (interface) $ edit port2
>> vFGTvm00 (port2) $ set mode static
>> vFGTvm00 (port2) $ set ip 10.1.100.169/24
>> vFGTvm00 (port2) $ set allowaccess ping https ssh snmp http telnet fgfm radius-acct
probe-response ftm
>> vFGTvm00 (port2) $ next
>> vFGTvm00 (interface) $ edit port3
>> vFGTvm00 (port3) $ set mode static
>> vFGTvm00 (port3) $ set ip 172.16.200.169/24
>> vFGTvm00 (port3) $ set allowaccess ping https ssh snmp http telnet fgfm radius-acct
probe-response ftm
>> vFGTvm00 (port3) $ next
>> vFGTvm00 (interface) $ end
>> vFGTvm00 $
>> vFGTvm00 $ config firewall policy
>> vFGTvm00 (policy) $ edit 0
>> vFGTvm00 (0) $ set srcintf "port2"
>> vFGTvm00 (0) $ set dstintf "port3"
>> vFGTvm00 (0) $ set srcaddr "all"
>> vFGTvm00 (0) $ set dstaddr "all"
>> vFGTvm00 (0) $ set action accept
>> vFGTvm00 (0) $ set schedule "always"
>> vFGTvm00 (0) $ set service "ALL"
>> vFGTvm00 (0) $ set nat enable
>> vFGTvm00 (0) $ next
>> vFGTvm00 (policy) $ end
>> vFGTvm00 $
>> vFGTvm00 $ config router static
>> vFGTvm00 (static) $ edit 1
>> vFGTvm00 (1) $ set gateway 172.16.200.254
>> vFGTvm00 (1) $ set device "port3"
>> vFGTvm00 (1) $ next
>> The destination is set to 0.0.0.0/0 which means all IP addresses.
>> vFGTvm00 (static) $ end
>> vFGTvm00 $
>> Finish running config script
FortiOS 7.6.2 Administration Guide 4006
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,006
|
VM
TPM support for FortiGate-VM
Using the TPM module, the FortiGate can generate, store, and authenticate cryptographic keys. When TPM is enabled
on a FortiGate,a master-encryption-password is automatically generated to encrypt sensitive data on the FortiGate such
as admin passwords, IPsec VPN preshared keys (PSK), and other passwords and keys as this document lists. In turn, a
TPM-generated primary key, which is stored on the TPM, encrypts this master-encryption-passsword.
When the FortiGate backs up configurations to a configuration file, the master-encryption-password encrypts passwords
and keys. The primary key also encrypts the master-encryption-password. Therefore, when restoring a config file, if the
FortiGate unit does not have TPM enabled, or does not have the same master-encryption-key, you cannot upload the
configuration file.
This enhancement adds TPM support to FGT-VM64 platforms. Hypervisors with software TPM emulator packages
installed can support the TPM feature in FortiOS. This feature supports KVM/QEMU.
For information about TPM, see Trusted platform module support on page 3066.
Passwords and keys that the masterencryptionkey can encrypt include:
l Alert email user password
l BGP and other routing-related configurations
l External resource
l FortiGuard proxy password
l FortiToken/FortiToken Mobile seed
l High availability password
l Link Monitor server-side password
l IPsec VPN PSK
l Local certificate private key
l SDN connector server-side password
l Local, LDAP, RADIUS, FSSO, and other user category-related passwords
l Modem/PPPoE
l NST password
l NTP Password
l SNMP
l Wireless security-related password
You cannot restore a private key-encrypted configuration via the FortiOS GUI if private-data-encryption is
disabled. The following shows the GUI in this scenario:
Also, if a configuration backup was taken while the private-data-encryption is enabled, then private-data-encryption is
disabled and re-enabled again, the configuration backup will no longer be able to be restored.
FortiOS 7.6.2 Administration Guide 4007
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,007
|
VM
To check if your FortiGate has a TPM:
1. Verify that the required packages are installed on the Linux KVM host:
packet@kvm-s01:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
packet@kvm-s01:~$
packet@kvm-s01:~$ apt list swtpm swtpm-tools qemu libvirt0 virtinst
Listing... Done
libvirt0/jammy-updates,jammy-updates,now 8.0.0-1ubuntu7.1 amd64 [installed,automatic]
qemu/jammy-updates,jammy-updates,now 1:6.2+dfsg-2ubuntu6.3 amd64 [installed]
swtpm-tools/jammy,jammy,now 0.6.3-0ubuntu3 amd64 [installed]
swtpm/jammy,jammy,now 0.6.3-0ubuntu3 amd64 [installed]
virtinst/jammy,jammy,jammy,jammy,now 1:4.0.0-1 all [installed]
2. Import a FGT_VM64_KVM VM to the host. You may want to change the following script to fit your setup:
UUID="$(uuid)"
SKU="FGT_VM64_KVM"
VER=7
NUM=0418
CPU=2
RAM=2048
CONTROLLER="type=ide,index=0"
BUS="ide"
MODEL="virtio"
RND_MAC() { printf '90:6C:AC:%02X:%02X\n' $((RANDOM%256)) $((RANDOM%256)) ;}
MACADDR=$(RND_MAC)
DOMAIN=$SKU-v$VER-b$NUM
qemu-img create -f qcow2 $DOMAIN-log.qcow2 1024M
qemu-img create -f qcow2 $DOMAIN-wanopt.qcow2 1024M
virt-install --connect qemu:///system \
--name $DOMAIN \
--uuid $UUID \
--virt-type kvm \
--arch=x86_64 \
--hvm \
--osinfo linux \
--os-variant=generic \
--graphics vnc,listen=0.0.0.0 --noautoconsole \
--cpu host-passthrough \
--vcpus=$CPU \
FortiOS 7.6.2 Administration Guide 4008
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,008
|
VM
--ram $RAM \
--sysinfo host \
--controller $CONTROLLER \
--boot hd,menu=on \
--disk fortios.qcow2,device=disk,bus=$BUS,format=qcow2,cache=none,io=native \
--disk $DOMAIN-log.qcow2,device=disk,bus=$BUS,format=qcow2,cache=none,io=native \
--disk $DOMAIN-wanopt.qcow2,device=disk,bus=$BUS,format=qcow2,cache=none,io=native \
--features kvm_hidden=on,smm=on \
--tpm backend.type=emulator,backend.version=2.0,model=tpm-tis \
--network bridge=br1,model=$MODEL,mac=$MACADDR:01 \
--network bridge=br2,model=$MODEL,mac=$MACADDR:02 \
--network bridge=br3,model=$MODEL,mac=$MACADDR:03 \
--network bridge=br4,model=$MODEL,mac=$MACADDR:04 \
--import
Key pairs are created on the host when the VM with TPM is imported:
packet@kvm-s01:~$ sudo ls -al /var/lib/swtpm-localca/
total 56
drwxr-x--- 2 swtpm root 4096 Sep 21 08:09 .
drwxr-xr-x 49 root root 4096 Sep 19 12:42 ..
-rwxr-xr-x 1 swtpm swtpm 0 Sep 21 08:09 .lock.swtpm-localca
-rw-r--r-- 1 swtpm swtpm 5519 Sep 21 08:09 01.pem
-rw-r--r-- 1 swtpm swtpm 1 Sep 21 08:19 certserial
-rw-r--r-- 1 swtpm swtpm 48 Sep 21 08:09 index.txt
-rw-r--r-- 1 swtpm swtpm 21 Sep 21 08:09 index.txt.attr
-rw-r--r-- 1 swtpm swtpm 0 Sep 21 08:09 index.txt.old
-rw-r--r-- 1 swtpm swtpm 5519 Sep 21 08:09 issuercert.pem
-rw-r--r-- 1 swtpm swtpm 3 Sep 21 08:09 serial
-rw-r--r-- 1 swtpm swtpm 3 Sep 21 08:09 serial.old
-rw-r----- 1 swtpm swtpm 2459 Sep 21 08:09 signkey.pem
-rw-r--r-- 1 swtpm swtpm 1468 Sep 21 08:09 swtpm-localca-rootca-cert.pem
-rw-r----- 1 swtpm swtpm 2459 Sep 21 08:09 swtpm-localca-rootca-privkey.pem
packet@kvm-s01:~$
packet@kvm-s01:~$ sudo cat /var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-
swtpm.log
Starting vTPM manufacturing as swtpm:swtpm @ Wed 21 Sep 2023 08:09:30 AM PDT
Successfully created RSA 2048 EK with handle 0x81010001.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type ek --ek
b0a85bad0cb79ef673f05f4d3fdb4f65da3171d86a392e60435c18a431a3062aafaadb22e2af06b2522cfcf9
59ca334ba38684859beb8064f2ba610735cb1dccee1388b9da840a4732d626358e383f0d089592d04dfc15b7
e82285f1fa1b4a73bd1bfdbf0d75a02f94f069ae1546d2f28f984046f384f4b35ef1451a191628b2a1329f13
8dad4e4407d0d03b2f71defc568642fe74d98f0e383e8ac1a5c94b4c30c1a0aae0cfe96bc9316397582cbbb8
34557a2112aad32d3f1e825e8dfbd569bb9b2492728c425609515568f17d42aee8a5fdaf973a441aaf8bf207
62101a9e2507ee0b4e876280e36474b4c10179df18fe066db708d0c11e741a8e722154c9 --dir
/var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc-08002799a4d5/tpm2 --logfile
/var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-swtpm.log --vmid FGT_VM64_KVM_
v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpm-spec-family 2.0 --tpm-spec-level
0 --tpm-spec-revision 164 --tpm-manufacturer id:00001014 --tpm-model swtpm --tpm-version
id:20191023 --tpm2 --configfile /etc/swtpm-localca.conf --optsfile /etc/swtpmlocalca.options
Creating root CA and a local CA's signing key and issuer cert.
Successfully created EK certificate locally.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type platform --ek
b0a85bad0cb79ef673f05f4d3fdb4f65da3171d86a392e60435c18a431a3062aafaadb22e2af06b2522cfcf9
59ca334ba38684859beb8064f2ba610735cb1dccee1388b9da840a4732d626358e383f0d089592d04dfc15b7
FortiOS 7.6.2 Administration Guide 4009
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,009
|
VM
e82285f1fa1b4a73bd1bfdbf0d75a02f94f069ae1546d2f28f984046f384f4b35ef1451a191628b2a1329f13
8dad4e4407d0d03b2f71defc568642fe74d98f0e383e8ac1a5c94b4c30c1a0aae0cfe96bc9316397582cbbb8
34557a2112aad32d3f1e825e8dfbd569bb9b2492728c425609515568f17d42aee8a5fdaf973a441aaf8bf207
62101a9e2507ee0b4e876280e36474b4c10179df18fe066db708d0c11e741a8e722154c9 --dir
/var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc-08002799a4d5/tpm2 --logfile
/var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-swtpm.log --vmid FGT_VM64_KVM_
v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpm-spec-family 2.0 --tpm-spec-level
0 --tpm-spec-revision 164 --tpm-manufacturer id:00001014 --tpm-model swtpm --tpm-version
id:20191023 --tpm2 --configfile /etc/swtpm-localca.conf --optsfile /etc/swtpmlocalca.options
Successfully created platform certificate locally.
Successfully created NVRAM area 0x1c00002 for RSA 2048 EK certificate.
Successfully created NVRAM area 0x1c08000 for platform certificate.
Successfully created ECC EK with handle 0x81010016.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type ek --ek
x=d28e9411dbe9aa0ada17c179c0854bebcf2d7ef2f94f42ef92f4e2deb28b568c9ecabd847fd36a974efceb
7b0d54893e,y=6b777ed060459c7907eb639665b3e64d9a93e692b7a4c0d20a18acafb6a2ae8e1284e948060
266b96c1c23cc883e7634,id=secp384r1 --dir /var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc08002799a4d5/tpm2 --logfile /var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-
swtpm.log --vmid FGT_VM64_KVM_v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpmspec-family 2.0 --tpm-spec-level 0 --tpm-spec-revision 164 --tpm-manufacturer
id:00001014 --tpm-model swtpm --tpm-version id:20191023 --tpm2 --configfile /etc/swtpmlocalca.conf --optsfile /etc/swtpm-localca.options
Successfully created EK certificate locally.
Successfully created NVRAM area 0x1c00016 for ECC EK certificate.
Successfully activated PCR banks sha1,sha256 among sha1,sha256,sha384,sha512.
Successfully authored TPM state.
Ending vTPM manufacturing @ Wed 21 Sep 2023 08:09:33 AM PDT
Starting vTPM manufacturing as swtpm:swtpm @ Wed 21 Sep 2023 08:19:44 AM PDT
Successfully created RSA 2048 EK with handle 0x81010001.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type ek --ek
b49eb6d250c2add268fe448098b458f57e3a47719c3fbcc49fb85ecddd937f2f662a238eee0b8814ea3c07a4
beeebad5a4ef30fd224e9051fad2ae29256ba7b85b03aef004ec05d2fd1e8139edcb3396b0b2b0a2adfb6b29
fd975a9daf385aa3ffc0739fbc2d6b5850b9f424c787074ac56571fc15564b3dfbd847f2c79d310dfea27f2a
694bb2c49d3bbb2e2d2a61c29d4214140358dfe23b97562ea8c756da7942e8be3b260da9dfccb26383c4734c
76d6e8e47e55055c1a697c1379faf3b41400034b201115fb0913151f0a1d4b963208e5f758ad9c59ee1da145
d2bc740069768545085d18a00108915214014b8b99fb47611f8b9260c70a4e2cef3ce1c7 --dir
/var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc-08002799a4d5/tpm2 --logfile
/var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-swtpm.log --vmid FGT_VM64_KVM_
v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpm-spec-family 2.0 --tpm-spec-level
0 --tpm-spec-revision 164 --tpm-manufacturer id:00001014 --tpm-model swtpm --tpm-version
id:20191023 --tpm2 --configfile /etc/swtpm-localca.conf --optsfile /etc/swtpmlocalca.options
Successfully created EK certificate locally.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type platform --ek
b49eb6d250c2add268fe448098b458f57e3a47719c3fbcc49fb85ecddd937f2f662a238eee0b8814ea3c07a4
beeebad5a4ef30fd224e9051fad2ae29256ba7b85b03aef004ec05d2fd1e8139edcb3396b0b2b0a2adfb6b29
fd975a9daf385aa3ffc0739fbc2d6b5850b9f424c787074ac56571fc15564b3dfbd847f2c79d310dfea27f2a
694bb2c49d3bbb2e2d2a61c29d4214140358dfe23b97562ea8c756da7942e8be3b260da9dfccb26383c4734c
76d6e8e47e55055c1a697c1379faf3b41400034b201115fb0913151f0a1d4b963208e5f758ad9c59ee1da145
d2bc740069768545085d18a00108915214014b8b99fb47611f8b9260c70a4e2cef3ce1c7 --dir
/var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc-08002799a4d5/tpm2 --logfile
/var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-swtpm.log --vmid FGT_VM64_KVM_
v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpm-spec-family 2.0 --tpm-spec-level
0 --tpm-spec-revision 164 --tpm-manufacturer id:00001014 --tpm-model swtpm --tpm-version
id:20191023 --tpm2 --configfile /etc/swtpm-localca.conf --optsfile /etc/swtpmFortiOS 7.6.2 Administration Guide 4010
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,010
|
VM
localca.options
Successfully created platform certificate locally.
Successfully created NVRAM area 0x1c00002 for RSA 2048 EK certificate.
Successfully created NVRAM area 0x1c08000 for platform certificate.
Successfully created ECC EK with handle 0x81010016.
Invoking /usr/lib/x86_64-linux-gnu/swtpm/swtpm-localca --type ek --ek
x=56a69f0827e7f4fc237dffb8202573f910140516ced4d85f62b443b627d6eb3075993a5e757119ed56ab43
daa76e5f23,y=c38364e2663bcb8cab92a658c2f4054826ca36d6cff99ea0a7a2ef9f600bf5902902482a67a
d90101930ed7f17cc613d,id=secp384r1 --dir /var/lib/libvirt/swtpm/eb3c65cc-d354-11ea-a7dc08002799a4d5/tpm2 --logfile /var/log/swtpm/libvirt/qemu/FGT_VM64_KVM_v7.0.8_b0418-
swtpm.log --vmid FGT_VM64_KVM_v7.0.8_b0418:eb3c65cc-d354-11ea-a7dc-08002799a4d5 --tpmspec-family 2.0 --tpm-spec-level 0 --tpm-spec-revision 164 --tpm-manufacturer
id:00001014 --tpm-model swtpm --tpm-version id:20191023 --tpm2 --configfile /etc/swtpmlocalca.conf --optsfile /etc/swtpm-localca.options
Successfully created EK certificate locally.
Successfully created NVRAM area 0x1c00016 for ECC EK certificate.
Successfully activated PCR banks sha1,sha256 among sha1,sha256,sha384,sha512.
Successfully authored TPM state.
Ending vTPM manufacturing @ Wed 21 Sep 2023 08:19:44 AM PDT
3. Log in to FGT_VM64_KVM and check TPM status:
FGT_VM64_KVM # diagnose hardware deviceinfo tpm
TPM capability information of fixed properties:
=========================================================
TPM_PT_FAMILY_INDICATOR: 2.0
TPM_PT_LEVEL: 0
TPM_PT_REVISION: 164
TPM_PT_DAY_OF_YEAR: 75
TPM_PT_YEAR: 2021
TPM_PT_MANUFACTURER: IBM
TPM_PT_VENDOR_STRING: SW TPM
TPM_PT_VENDOR_STRING_1 in HEX: 0x53572020
TPM_PT_VENDOR_STRING_2 in HEX: 0x2054504d
TPM_PT_VENDOR_STRING_3 in HEX: 0x00000000
TPM_PT_VENDOR_STRING_4 in HEX: 0x00000000
TPM_PT_VENDOR_TPM_TYPE: 1
TPM_PT_FIRMWARE_VERSION: 8217.4131.22.13878
TPM_PT_FIRMWARE_VERSION in HEX: 0x2019102300163636
TPM_PT_MEMORY:
=========================================================
Shared RAM: 0 CLEAR
Shared NV: 1 SET
Object Copied To Ram: 1 SET
TPM_PT_PERMANENT:
=========================================================
Owner Auth Set: 0 CLEAR
Sendorsement Auth Set: 0 CLEAR
Lockout Auth Set: 0 CLEAR
Disable Clear: 0 CLEAR
In Lockout: 0 CLEAR
TPM Generated EPS: 1 SET
FortiOS 7.6.2 Administration Guide 4011
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,011
|
VM
FGT_VM64_KVM # diagnose tpm get-property
TPM capability information of fixed properties:
=========================================================
TPM_PT_FAMILY_INDICATOR: 2.0
TPM_PT_LEVEL: 0
TPM_PT_REVISION: 164
TPM_PT_DAY_OF_YEAR: 75
TPM_PT_YEAR: 2021
TPM_PT_MANUFACTURER: IBM
TPM_PT_VENDOR_STRING: SW TPM
TPM_PT_VENDOR_STRING_1 in HEX: 0x53572020
TPM_PT_VENDOR_STRING_2 in HEX: 0x2054504d
TPM_PT_VENDOR_STRING_3 in HEX: 0x00000000
TPM_PT_VENDOR_STRING_4 in HEX: 0x00000000
TPM_PT_VENDOR_TPM_TYPE: 1
TPM_PT_FIRMWARE_VERSION: 8217.4131.22.13878
TPM_PT_FIRMWARE_VERSION in HEX: 0x2019102300163636
TPM_PT_MEMORY:
=========================================================
Shared RAM: 0 CLEAR
Shared NV: 1 SET
Object Copied To Ram: 1 SET
TPM_PT_PERMANENT:
=========================================================
Owner Auth Set: 0 CLEAR
Sendorsement Auth Set: 0 CLEAR
Lockout Auth Set: 0 CLEAR
Disable Clear: 0 CLEAR
In Lockout: 0 CLEAR
TPM Generated EPS: 1 SET
FGT_VM64_KVM # diagnose tpm get-var-property
TPM capability information of variable properties:
TPM_PT_STARTUP_CLEAR:
=========================================================
Ph Enable: 1 SET
Sh Enable: 1 SET
Eh Enable: 1 SET
Orderly: 0 CLEAR
FGT_VM64_KVM # diagnose tpm read-clock
Clock info:
=========================================================
Time since the last TPM_Init:
2375158 ms = 0 y, 0 d, 0 h, 39 min, 35 s, 158 ms
Time during which the TPM has been powered:
2375319 ms = 0 y, 0 d, 0 h, 39 min, 35 s, 319 ms
TPM Reset since the last TPM2_Clear: 5
FortiOS 7.6.2 Administration Guide 4012
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,012
|
VM
Number of times that TPM2_Shutdown: 0
Safe: 1 = Yes
FGT_VM64_KVM # diagnose tpm shutdown-prepare
Shutdown works as expected.
FGT_VM64_KVM # diagnose tpm selftest
Successfully tested. Works as expected.
FGT_VM64_KVM # diagnose tpm generate-random-number
Random value:
0x00000000: 0x73 0xF1 0x9F 0x31
FGT_VM64_KVM # diagnose tpm SHA-1 1234567890abcdef1234567890abcdef
1234567890abcdef1234567890abcdef
TPM2_Hash of '1234567890abcdef1234567890abcdef' with SHA-1:
0x00000000: 62 0A 31 15 69 9A 42 2B
0x00000008: D8 74 DE 31 D3 E6 91 1C
0x00000010: 58 3A 76 75
FGT_VM64_KVM # diagnose tpm SHA-256 1234567890abcdef1234567890abcdef
1234567890abcdef1234567890abcdef
TPM2_Hash of '1234567890abcdef1234567890abcdef' with SHA-256:
0x00000000: C5 12 D9 2E 35 45 B2 F1
0x00000008: 22 2E 4B 4C 6A F6 D3 30
0x00000010: EC 30 02 A0 4B CA A4 1D
0x00000018: F9 CC 2C 49 62 84 96 D6
4. Enable TPM and input the master encryption password. This is an example. Using
0123456789abcdef0123456789abcdef as your private key is not recommended:
FGT_VM64_KVM # exec private-encryption-key sample
Private encryption is not enabled.
Command fail. Return code 7
FGT_VM64_KVM # config system global
FGT_VM64_KVM (global) # set private-data-encryption enable
FGT_VM64_KVM (global) # end
This operation will generate a random private data encryption key!
Previous config files encrypted with the system default key cannot be restored after
this operation!
Do you want to continue? (y/n)y
Private data encryption key generation succeeded!
The following shows an example of a successful activation:
FGT_VM64_KVM # exec private-encryption-key sample
B64TEXT: u7oOx1iBjPFu4XLZVq5/RpoZrDJ9htRo6Jjhfts4BaI=
B64HMAC: FHmUhzSyT0IEfyoRnfdTFbY2l0o=
Note the B64TEXT and B64HMAC sample keys. Run the following to verify the feature:
FortiOS 7.6.2 Administration Guide 4013
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,013
|
VM
FGT_VM64_KVM # exec private-encryption-key verify
u7oOx1iBjPFu4XLZVq5/RpoZrDJ9htRo6Jjhfts4BaI= FHmUhzSyT0IEfyoRnfdTFbY2l0o=
Verification passed.
5. Back up the config:
FGT_VM64_KVM # execute backup config tftp FGVM02TM12345678.conf 172.18.70.161
Please wait...
Connect to tftp server 172.18.70.161 ...
#
Send config file to tftp server OK.
6. Verify that the backup config has private-encryption-key:
packet@1804:/mnt/incoming$ less FGVM02TM12345678.conf
#config-version=FGVMK6-7.0.8-FW-build0418-220920:opmode=0:vdom=0:user=admin
#conf_file_ver=2079893748141389
#buildno=0418
#global_vdom=1
#private-encryption-key=oY5GhQK3w0Ddn0EX+8hp6UYpjB4=
config system global
set admin-server-cert "Fortinet_Factory"
set alias "FortiGate-VM64-KVM"
set hostname "FGT_VM64_KVM"
set private-data-encryption enable
set timezone 04
end
FortiOS 7.6.2 Administration Guide 4014
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,014
|
Hyperscale firewall
Hyperscale hardware and facilities can scale a distributed computing environment up to thousands of servers. It is about
achieving massive scale in computing, typically for big data or cloud computing.
A hyperscale firewall secures hyperscale data centers and 5G networks.
See the Hyperscale Firewall Guide. For information about the difference between hyperscale and standard FortiOS
CGNAT, see Hyperscale and standard FortiOS CGNAT feature comparison.
FortiOS 7.6.2 Administration Guide 4015
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,015
|
Troubleshooting
This section is intended for administrators with super_admin permissions who require assistance with basic and
advanced troubleshooting. Administrators with other types of permissions may not be able to perform all of the tasks in
this section.
This section contains the following troubleshooting topics:
l Troubleshooting methodologies on page 4017
l Connectivity Fault Management on page 4020
l Troubleshooting scenarios on page 4023
l System date and time settings on page 4024
l Checking the hardware connections on page 4025
l Checking FortiOS network settings on page 4026
l Checking CPU and memory resources on page 4028
l FortiGuard server settings on page 4070
l Troubleshooting high CPU usage on page 4031
l Checking the modem status on page 4035
l Running ping and traceroute on page 4035
l Checking the logs on page 4041
l Verifying routing table contents in NAT mode on page 4041
l Verifying the correct route is being used on page 4042
l Verifying the correct firewall policy is being used on page 4042
l Checking the bridging information in transparent mode on page 4043
l Checking wireless information on page 4044
l Performing a sniffer trace or packet capture on page 4045
l Debugging the packet flow on page 4047
l Testing a proxy operation on page 4050
l Displaying detail Hardware NIC information on page 4051
l Performing a traffic trace on page 4054
l Using a session table on page 4054
l Finding object dependencies on page 4058
l Diagnosing NPU-based interfaces on page 4059
l Identifying the XAUI link used for a specific traffic stream on page 4060
l Running the TAC report on page 4061
l Using the process monitor on page 4061
l Computing file hashes on page 4063
l Other commands on page 4066
l FortiGuard troubleshooting on page 4069
l View open and in use ports on page 4072
l IPS and AV engine version on page 4073
l print tablesize on page 4073
FortiOS 7.6.2 Administration Guide 4016
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,016
|
Troubleshooting
l CLI troubleshooting cheat sheet on page 4074
l CLI error codes on page 4074
l Additional resources on page 4075
Troubleshooting methodologies
The sections in this topic provide an overview of how to prepare to troubleshoot problems in FortiGate. They include
verifiying your user permissions, establishing a baseline, defining the problem, and creating a plan.
Verify user permissions
Before you begin troubleshooting, verify the following:
l You have administrator privileges for the FortiGate.
l The FortiGate is integrated into your network.
l The operation mode is configured.
l The system time, DNS settings, administrator password, and network interfaces are configured.
l Firmware, FortiGuard AntiVirus, FortiGuard Application Control, and FortiGuard IPS are up to date.
If you are using a FortiGate that has virtual domains (VDOMs) enabled, you can often
troubleshoot within your own VDOM. However, you should inform the super_admin for the
FortiGate that you will be performing troubleshooting tasks.
You may also need access to other networking equipment, such as switches, routers, and
servers to carry out tests. If you do not have access to this equipment, contact your network
administrator for assistance.
Establish a baseline
FortiGate operates at all layers of the OSI model. For this reason, troubleshooting can be complex. Establishing baseline
parameters for your system before a problem occurs helps to reduce the complexity when you need to troubleshoot.
A best practice is to establish and record the normal operating status. Regular operation data shows trends, and allows
you to see where changes occur when problems arise. You can gather this data by using logs and SNMP tools to
monitor the system performance or by regularly running information gathering commands and saving the output.
You should back up your FortiOS configuration on a regular basis even when you are not
troubleshooting. You can restore the backed up configuration as needed to save time
recreating it from the factory default settings.
Use the following CLI commands to obtain normal operating data for a FortiGate:
get system status Displays firmware versions and FortiGuard engine versions, and
other system information.
FortiOS 7.6.2 Administration Guide 4017
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,017
|
Troubleshooting
get system performance status Displays CPU and memory states, average network usage, average
sessions and session setup rate, viruses caught, IPS attacks blocked,
and uptime.
get hardware memory Displays information about memory.
get system session status Displays total number of sessions.
get router info routing-table all Displays all the routes in the routing table, including their type,
source, and other useful data.
get ips session Displays memory used and maximum amount available to IPS as well
as counts
get webfilter ftgd-statistics Displays a list of FortiGuard related counts of status, errors, and other
data.
diagnose sys session list Displays the list of current detailed sessions.
show sys dns Displays the configured DNS servers.
diagnose sys ntp status Displays information about NTP servers.
You can run any commands that apply to your system for information gathering. For example, if you have active VPN
connections, use the get vpn series of commands to get more information about them.
Use execute tac report to get an extensive snapshot of your system. This command runs many diagnostic
commands for specific configurations. It also records the current state of each feature regardless of the features
deployed on your FortiGate. If you need to troubleshoot later, you can run the same command again and compare the
differences to identify any suspicious output.
Define the problem
The following questions are intended to compare the current behavior of the FortiGate with normal operations to help
you define the problem. Be specific with your answers. After you define the problem, search for a solution in the
troubleshooting scenarios section, and then create a plan to resolve it.
What is the problem? The problem being observed may not be the actual problem. You should
determine where the problem lies before starting to troubleshoot the FortiGate.
Was the device working
before?
If the device never worked, it might be defective. For more information, see
Troubleshooting your installation on page 38.
Can the problem be
reproduced?
If the problem is intermittent, it may be dependent on system load.
Intermittent problems are challenging to troubleshoot because they are difficult to
reproduce.
What has changed? Use the FortiGate event log to identify possible configuration changes.
There may be changes in the operating environment. For example, there might be
a gradual increase in load as more sites are forwarded through the firewall.
If something has changed, roll back the change and assess the impact.
What is the scope of the
problem?
After you isolate the problem, determine what applications, users, devices, and
operating systems the problem affects.
FortiOS 7.6.2 Administration Guide 4018
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,018
|
Troubleshooting
The following questions are intended to narrow the scope of the problem and
identify what to check during troubleshooting. The more factors you can eliminate,
the less you need to check. For this reason, be as specific and accurate as
possible when gathering information.
l What is not working?
l Is more than one thing not working?
l Is it partly working? If so, what parts are working?
l Is it a connectivity issue for the entire device, or is there an application that
isn’t reaching the Internet?
l Where did the problem occur?
l When did the problem occur and to which users or groups of users?
l What components are involved?
l What applications are affected?
l Can you use a packet sniffer to trace the problem?
l Can you use system debugging or look in the session table to trace the
problem?
l Do any of the log files indicate a failure has occurred?
Create a troubleshooting plan
After you define the problem and its scope, develop a troubleshooting plan.
Create checklist Make a list all the possible causes of the problem and how you can test for each
cause.
Create a checklist to keep track of what has been tried and what is left to test.
Checklists are useful when more than one person is performing troubleshooting
tasks.
Obtain the required equipment Testing your solution may require additional networking equipment, computers, or
other devices.
Network administrators usually have additional networking equipment available to
loan you, or a lab where you can bring the FortiGate unit to test.
If you do not have access to equipment, check for shareware applications that can
perform the same tasks. Often, there are software solutions you can use when
hardware is too expensive.
Consult Fortinet
troubleshooting resources
After the checklist is created, refer to the troubleshooting scenarios sections to
assist with implementing your plan. See Troubleshooting scenarios on page
4023.
Gather information for
technical support
If you still require technical assistance after the plan is implemented, be prepared
to provide Fortinet technical support with following information:
l Firmware build version (use the get system status command)
l Network topology diagram
l Recent configuration file
l Recent debug log (optional)
l Summary of troubleshooting steps you have taken and the results.
FortiOS 7.6.2 Administration Guide 4019
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,019
|
Troubleshooting
Do not provide the output from the execute tac report unless
the support team requests it. The output from this command is
very large and is not required in many cases.
Contact technical support Before contacting technical support, ensure you have login access (preferably
with full read/write privileges) to all networking devices that could be relevant to
troubleshooting.
If you are using VMs, be prepared to have someone who can log in to the virtual
hosting platform in case it is necessary to check and possibly modify resource
allocation.
For information about contacting technical support, go to FortiCare Support
Service page.
Connectivity Fault Management
Some FortiGate hardware models support Connectivity Fault Management (CFM) technology. With CFM, administrators
can easily diagnose and resolve issues in Ethernet networks. CFM provides tools for monitoring, testing, and verifying
the connectivity and performance of network segments.
The following platforms support CFM:
FortiGate FG-40F, FG-40F-3G4G, FG-60F, FG-61E, FG-61F, FG-81F, FG-90E-POE, FG-100F, FG101F, FG-200E, FG-1100E
FortiWiFi FWF-40F, FWF-60F, FWF-61F
Use the config ethernet-oam cfm command to configure the CFM protocol.
config ethernet-oam cfm
edit <domain-id>
set domain-name <string>
set domain-level <integer>
config service
edit <service-id>
set service-name <string>
set interface "<string>"
set mepid <integer>
set message-interval <integer>
set cos <integer>
set sender-id Hostname {none | Hostname}
next
end
next
end
<domain-id> Specify the domain ID for the Ethernet layer operation, administration, and
management (OAM) protocol. A unique domain ID is used to communicate with
other peers under the same domain ID and domain level.
FortiOS 7.6.2 Administration Guide 4020
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,020
|
Troubleshooting
domain-level <integer> Specify the OAM maintenance level (0 to 7, with 0 being the smallest and 7 being
the largest). A unique domain level is used to communicate with other devices
under the same domain ID and domain level.
domain-name <string> Specify the OAM domain name or maintenance domain identifier (MDID). Other
peer devices recognize the domain name. All devices in the same domain with the
same service level can communicate with each other.
A domain can provide multiple services. Each service uses a special service ID. The following items describe a service:
<service-id> Specify the ID for the service.
service-name <string> Specify the name of the service.
interface <string> Specify the name of the VLAN interface where the service is enabled. The service
is associated with a particular VLAN network port and can't be accessed by other
network ports.
mepid <integer> Specify the unique ID of the maintenance association endpoints (MEP) (1 - 8191).
The service is associated with a unique MEP ID and can't respond to other
service requests of a different MEP ID.
message interval
<integer>
Specify the continuity-check message frequency interval in milliseconds.
Determines how long to send a continuity-check message to determine whether
the service is alive.
cos <integer> Specify the class of service (COS) bit for continuity-check messages (0 to 7). CoS
is an optional, special bit in the packet of continuity-check messages.
sender-id {none |
hostname}
Specify the type, length, value (TLV) sender ID:
l none: indicates no sender ID.
l hostname: uses the Fortinet production name of the device as the sender
ID, for example, FortiGate-80F.
The sender ID is an optional column that includes a hostname in the packet of
continuity-check messages.
The following diagnose commands can be used with this feature:
diagnose ethernet-oam
cfmpeer
Locate peers configured with config ethernet-oam cfm that are using the
CFM Continuity Check Protocol (CCP) protocol to connect to the CCP daemon
(CCD).
diagnose debug
application cfmd
{enable | disable}
Enable or disable debugging messages of the CFM protocol.
l enable: enable debugging messages for the CFM protocol. Messages
appear on the console.
l disable: disable debugging messages.
The following execute commands can be used with this feature:
execute ethernet ping Check if an interface has a peer with mac address and level available under CFM
support.
FortiOS 7.6.2 Administration Guide 4021
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,021
|
Troubleshooting
execute ethernet
traceroute
Check the Ethernet traceroute with the peer FortiGate. The traceroute is
instructed to achieve a peer through an interface with mac_address and level
available under CFM support.
Example
In this example, an interface (vlan101) connects FortiGate 81F to FortiGate 101F. CFM is configured for the interface
(vlan101) on the FortiGate 81F. All steps are performed on the FortiGate 101F.
Because this feature is based on IEEE 802.1Q, an IP address is not needed to connect the interface.
To configure and use CFM :
1. Configure CFM for the interface named vlan101:
config ethernet-oam cfm
edit 1
set domain-name cfm-test
set domain-level 1
config service
edit 1
set service-name vlan-101
set interface "vlan101"
set mepid 101
set message-interval 10000
set cos 7
set sender-id Hostname
next
end
next
end
2. On the FortiGate 101F, show the peers connecting to the device:
# diagnose ethernet-oam cfmpeer
wait for the responses from CCD daemons ...
======== MEPs (pid 11251) ========
======== domain_name: cfm-test service_name: vlan-101 mepid: 101 ========
1 MAC = e0:23:ff:9b:07:0a, state = UP, mdlevel = 1, domain_name = cfm-test, service_
name = vlan-101, mepid = 81, TLV_port_status = PsUP, TLV_interface_status = isUp
======== END ========
3. On FortiGate 101F, check whether the interface has a peer under CFM support:
# execute ethernet ping vlan101 1 5 e0:23:ff:9b:07:0a
Sending CFM LBM to e0:23:ff:9b:07:0a
64 bytes from e0:23:ff:9b:07:0a, sequence 422603820, 1 ms
64 bytes from e0:23:ff:9b:07:0a, sequence 422603821, 1 ms
64 bytes from e0:23:ff:9b:07:0a, sequence 422603822, 1 ms
64 bytes from e0:23:ff:9b:07:0a, sequence 422603823, 1 ms
64 bytes from e0:23:ff:9b:07:0a, sequence 422603824, 1 ms
4. Execute the Ethernet traceroute:
FortiOS 7.6.2 Administration Guide 4022
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,022
|
Troubleshooting
# execute ethernet traceroute vlan101 1 e0:23:ff:9b:07:0a
Sending CFM LTM probe to e0:23:ff:9b:07:0a
ethtrace_main: flags = 0, usefdbonly = 0
ttl 1: LTM with id 984984516
cfm_matchltr - 384
cfm_matchltr - 404
reply from e0:23:ff:9b:07:0a, id=984984516, ttl=0, RlyHit
Troubleshooting scenarios
The following table is intended to help you diagnose common problems and provides links to the corresponding
troubleshooting topics:
Problem Probable cause Recommended action
Hardware
connections
l Are all of the cables and interfaces
connected properly?
l Is the LED for the interface green?
Checking the hardware connections on page
4025
FortiOS network
settings
l If you are having problems connecting to
the management interface, is your
protocol enabled on the interface for
administrative access?
l Does the interface have an IP address?
Checking FortiOS network settings on page
4026
CPU and memory
resources
l Is the CPU running at almost 100
percent usage?
l Is your FortiGate running low on
memory?
Checking CPU and memory resources on
page 4028
Modem status l Is the modem connected?
l Are there PPP issues?
Checking the modem status on page 4035
Ping and traceroute Is the FortiGate experiencing complete
packet loss?
Running ping and traceroute on page 4035
Logs Do you need to identify a problem? Checking the logs on page 4041
Contents of the
routing table (in
NAT mode)
l Are there routes in the routing table for
default and static routes?
l Do all connected subnets have a route in
the routing table?
l Does a route have a higher priority than
it should?
Verifying routing table contents in NAT mode
on page 4041
Traffic routes Is the traffic routed correctly? Verifying the correct route is being used on
page 4042
Firewall policies Is the correct firewall policy applied to the
expected traffic?
Verifying the correct firewall policy is being
used on page 4042
FortiOS 7.6.2 Administration Guide 4023
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,023
|
Troubleshooting
Problem Probable cause Recommended action
Bridging
information in
transparent mode
Are you having problems in transparent
mode?
Checking the bridging information in
transparent mode on page 4043
Firewall session
list
Are there active firewall sessions? Using a session table on page 4054
Wireless Network Is the wireless network working properly? Checking wireless information on page 4044
FortiGuard
connectivity
Is the FortiGate communicating properly with
FortiGuard?
Verifying connectivity to FortiGuard on page
4069
Sniffer trace l Is traffic entering the FortiGate? Does
the traffic arrive on the expected
interface?
l Is the ARP resolution correct for the
next-hop destination?
l Is the traffic exiting the FortiGate to the
destination as expected?
l Is the FortiGate sending traffic back to
the originator?
Performing a sniffer trace or packet capture
on page 4045
Packet flow Is traffic entering or leaving the FortiGate as
expected?
Debugging the packet flow on page 4047
FortiGate is frozen
or halted
The FortiGate may have experienced a
kernel issue.
On supported models, use the NMI button to
troubleshoot kernel issues.
System date and time settings
The system date and time are important for FortiGuard services, logging events, sending alerts, and certificates that
have a time requirement to check for validity.
The wrong time makes the log entries confusing and difficult to use. If all devices have the same time, it helps to correlate
log entries from different devices.
When possible, use Network Time Protocol (NTP) to set the date and time. This is an automatic method that does not
require manual intervention. However, you must ensure that the port is allowed through the firewalls on your network.
FortiToken synchronization requires NTP in many situations.
For information about setting the system date and time, see Setting the system time on page 3049.
To view and configure the date and time in the GUI:
1. Go to Dashboard > Status. The date and time are displayed in the System Information widget, next to System Time.
2. Go to System > Settings.
3. In the System Time section, select NTP, and then configure the Time Zone, and Set Time settings as required.
FortiOS 7.6.2 Administration Guide 4024
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,024
|
Troubleshooting
To view the date and time in the CLI:
# execute date
current date is: 2024-07-23
# execute time
current time is: 14:17:00
last ntp sync:Tue Jul 23 13:25:21 2024
To configure the date and time in the CLI:
Use the set timezone ? command to display a list of timezones and the integers that represent them.
config system global
set timezone <integer>
end
config system ntp
set type custom
config ntpserver
edit 1
set server “ntp1.fortinet.net”
next
edit 2
set server “ntp2.fortinet.net”
next
end
set ntpsync enable
set syncinterval 60
end
Checking the hardware connections
If traffic is not flowing from the FortiGate, there may be a problem with the hardware connection.
To check hardware connections:
1. Ensure the network cables are plugged into the interfaces.
2. Verify the LED connection lights for the network cables indicate there is a connection. The lights are typically green
when there is a connection.
3. Change the cable when:
l The cable or its connector are damaged.
l You are unsure of the type or quality of the cable, such as straight through or crossover.
l You see exposed wires at the connector.
4. Connect the FortiGate to different hardware.
5. Go to Network > Interfaces to ensure the link status for the interface is set to Up.
The link status is based on the physical connection and cannot be set in FortiOS.
To enable an interface in the GUI:
You should still perform basic software connectivity tests to ensure complete connectivity even if there was a problem
with the hardware connection. The interface might also be disabled, or its Status might be set to Down. See Interfaces on
page 168.
FortiOS 7.6.2 Administration Guide 4025
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,025
|
Troubleshooting
1. Go to Network > Interfaces.
2. Select an interface, such as Port1, and click Edit.
3. In the Miscellaneous area, next to Status, click Enabled.
4. Click OK.
To enable an interface in the CLI:
config system interface
edit port1
set status up
next
end
Checking FortiOS network settings
Check the FortiOS network settings if you have problems connecting to the management interface. FortiOS network
settings include, interface settings, DNS Settings, and DHCP settings.
Interface settings
If you can access the FortiGate with the management cable only, you can view the interface settings in the GUI.
To view the interface settings in the GUI:
1. Go to Network > Interfaces.
2. Select an interface and click Edit.
3. Check the following interfaces to ensure they are not blocking traffic.
Setting Description
Link Status The status is Up when a valid cable is plugged in. The status is Down when an
invalid cable is plugged in.
The Link Status is shown physically by the connection LED for the interface. If the
LED is green, the connection is good. If Link Status is Down, the interface does not
work.
Link status also appears in the Network > Interfaces page by default.
Addressing mode Do not use DHCP if you do not have a DHCP server. You will not be able to log into
an interface in DHCP mode as it will not have an IP address.
IP/Network Mask An interface requires an IP address to connect to other devices. Ensure there is a
valid IP address in this field. The one exception is when DHCP is enabled for this
interface to get its IP address from an external DHCP server.
IPv6 address The same protocol must be used by both ends to complete the connection. Ensure
this interface and the remote connection are both using IPv4 or both are using IPv6
addresses.
FortiOS 7.6.2 Administration Guide 4026
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,026
|
Troubleshooting
Setting Description
Administrative access If no protocols are selected, you will have to use the local management cable to
connect to the unit. If you are using IPv6, configure the IPv6 administrative access
protocols.
Status Ensure the status is set to Up or the interface will not work.
To display the internal interface settings in the CLI:
FGT# show system interface <interface_name>
To view the list of possible interface settings:
config system interface
edit <interface_name>
get
end
DNS settings
To view DNS settings in the GUI:
Go to Network > DNS.
You can trace many networking problems back to DNS issues. Check the following items:
1. Are there values for both the Primary DNS server and Secondary DNS server fields.
2. Is the Local Domain Name correct?
3. Are you using IPv6 addressing? If so, are the IPv6 DNS settings correct?
4. Are you using Dynamic DNS (DDNS)? If so, is it using the correct server, credentials, and interface?
5. Can you contact both DNS servers to verify the servers are operational?
6. If an interface addressing mode is set to DHCP and is set to override the internal DNS, is that interface receiving a
valid DNS entry from the DHCP server? Is it a reasonable address and can it be contacted to verify it is operational?
7. Are there any DENY security policies that need to allow DNS?
8. Can any internal device perform a successful traceroute to a location using the FQDN?
DHCP server settings
DHCP servers are common on internal and wireless networks. The DHCP server will cause problems if it is not
configured correctly.
To view DHCP server settings in the GUI:
1. Go to Network > Interfaces.
2. Select an interface, and click Edit.
FortiOS 7.6.2 Administration Guide 4027
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,027
|
Troubleshooting
Check the following items:
1. Is the DHCP server enabled?
2. Is the DHCP server entry set to Relay? If so, verify there is another DHCP server to which requests can be relayed.
Otherwise, set it to Server.
3. Does the DHCP server use a valid IP address range? Are other devices using the addresses? If one or more
devices are using IP addresses in this range, you can use the IP reservation feature to ensure the DHCP server
does not use these addresses. See DHCP servers and relays on page 424
4. Is there a gateway entry? If not, add a gateway entry to ensure that the server's clients have a default route.
5. Is the system DNS setting being used? A best practice is to avoid confusion by using the system DNS whenever
possible. However, you can specify up to three custom DNS servers, and you should use all three entries for
redundancy.
There are some situations, such as a new wireless interface, or during the initial FortiGate
configuration, where interfaces override the system DNS entries. When this happens, it often
shows up as intermittent Internet connectivity.
To fix the problem, go to Network > DNS, and enable Use FortiGuard Servers.
Checking CPU and memory resources
Check the CPU and memory resources when the FortiGate is not working, the network is slow, or there is a reduced
firewall session setup rate. All processes share the system resources in FortiOS, including CPU and memory.
To view system resources in the GUI:
Go to Dashboard > Status.
The resource information is located in the CPU and Memory widgets. For information, see Dashboards and Monitors on
page 106.
To view system resources in the CLI:
get system performance status
Sample output:
FGT# get system performance status
CPU states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU0 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU1 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU2 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
CPU3 states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
Memory: 4050332k total, 527148k used (13%), 3381312k free (83%), 141872k freeable (3%)
Average network usage: 41 / 28 kbps in 1 minute, 54 / 44 kbps in 10 minutes, 42 / 34 kbps
in 30 minutes
Average sessions: 33 sessions in 1 minute, 48 sessions in 10 minutes, 38 sessions in 30
minutes
Average session setup rate: 0 sessions per second in last 1 minute, 0 sessions per second
in last 10 minutes, 0 sessions per second in last 30 minutes
Virus caught: 0 total in 1 minute
IPS attacks blocked: 0 total in 1 minute
Uptime: 0 days, 22 hours, 59 minutes
FortiOS 7.6.2 Administration Guide 4028
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,028
|
Troubleshooting
The first line of the output shows the CPU usage by category:
CPU states: 0% user 0% system 0% nice 100% idle 0% iowait 0% irq 0% softirq
The second line of the output shows the memory usage:
Memory: 4050332k total, 527148k used (13%), 3381312k free (83%), 141872k freeable (3%)
Memory usage should not exceed 90%. Using too much memory prevents some processes from functioning properly.
For example, if the system is running low on memory, antivirus scanning enters into failopen mode where it drops
connections or bypasses the antivirus system.
Other lines of output, such as average network usage, average session setup rate, viruses caught,
and IPS attacks blocked, help determine why system resource usage is high.
For example:
l A high average network usage may indicate high traffic processing on the FortiGate,
l A very low or zero, average session setup rate may indicate the proxy is overloaded and unable to do its
job.
Troubleshooting CPU and network resources
FortiGate has stopped working
If the FortiGate has stopped working, the first line of the output will look similar to this:
CPU states: 0% user 0% system 0% nice 100% idle
Network is slow
If your network is running slow, the first line of the output will look similar to this:
CPU states: 1% user 98% system 0% nice 1% idle
This example shows that all of the CPU is being used by system processes, and the FortiGate is overloaded. When
overloading occurs, it is possible a process such as scanunitid is using all the resources to scan traffic. In this case
you need to reduce the amount of traffic being scanned by blocking unwanted protocols, configuring more security
policies to limit scanning to certain protocols, or similar actions.
It is also possible a hacker has accessed your network and is overloading it with malicious activity, such as running a
spam server or using zombie PCs to attack other networks on the Internet.
You can use the following command to investigate the problem with the CPU:
get system performance top
This command shows all of the top processes that are running on the FortiGate and their CPU usage. The process
names are on the left. If a process is using most of the CPU cycles, investigate it to determine whether the activity is
normal.
Reduced firewall session setup rate
A reduced firewall session setup rate can be caused by a lack of system resources on the FortiGate, or reaching the
session count limit for a VDOM.
FortiOS 7.6.2 Administration Guide 4029
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,029
|
Troubleshooting
As a best practice, administrators should record the session setup rate during normal
operation to establish a baseline to help define a problem when your are troubleshooting.
The session setup rate appears in the average sessions section of the output.
A reduced firewall session setup rate will look similar to this:
Average sessions: 80 sessions in 1 minute, 30 sessions in 10 minutes, 42 sessions in 30
minutes
Average session setup rate: 3 sessions per second in last 1 minute, 0 sessions per second in
last 10 minutes, 0 sessions per second in last 30 minutes
In the example above, there were 80 sessions in 1 minute, or an average of 3 sessions per second.
The values for 10 minutes and 30 minutes allow you to take a longer average for a more reliable value if your
FortiGate is working at maximum capacity. The smallest FortiGate can have 1,000 sessions established per second
across the unit.
The session setup rate is a global command. If you have multiple VDOMs configured with
many sessions in each VDOM, the session setup rate per VDOM will be slower than if there
are no VDOMs configured.
High memory usage
As with any system, a FortiGate has limited hardware resources, such as memory, and all processes running on the
FortiGate share the memory. Each process uses more or less memory, depending on its workload. For example, a
process usually uses more memory in high traffic situations. If some processes use all of the available memory, other
processes will not be able to run.
When high memory usage occurs, the services may freeze up, connections may be lost, or new connections may be
refused.
If you see high memory usage in the Memory widget, the FotiGate may be handling high traffic volumes. Alternatively,
the FortiGate may have problems with connection pool limits that are affecting a single proxy. If the FortiGate receives
large volumes of traffic on a specific proxy, the unit may exceed the connection pool limit. If the number of free
connections within a proxy connection pool reaches zero, issues may occur.
To view current memory usage information in the CLI:
diagnose hardware sysinfo memory
Sample output:
total: used: free: shared: buffers: cached: shm:
Mem: 2074185728 756936704 1317249024 0 20701184 194555904 161046528
Swap: 0 0 0
MemTotal: 2025572 kB
MemFree: 1286376 kB
MemShared: 0 kB
Buffers: 20216 kB
Cached: 189996 kB
SwapCached: 0 kB
Active: 56644 kB
FortiOS 7.6.2 Administration Guide 4030
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,030
|
Troubleshooting
Inactive: 153648 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 2025572 kB
LowFree: 1286376 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Troubleshooting high CPU usage
Connection-related problems may occur when FortiGate's CPU resources are over extended. This occurs when you
deploy too many FortiOS features at the same time.
Examples of CPU intensive features:
l VPN high-level encryption
l Intensive scanning of all traffic
l Logging all traffic and packets
l Dashboard widgets that frequently perform data updates
For information on customizing the CPU use threshold, see Execute a CLI script based on memory and CPU thresholds
on page 3682.
Determining the current level of CPU usage
You can view CPU usage levels in the GUI or CLI. For precise usage values for both overall usage and specific
processes, use the CLI.
To view CPU usage in the GUI:
Go to Dashboard > Status. Real-time CPU usage information is located in the CPU widget.
To view CPU usage in the CLI:
l Show top processes information:
diagnose sys top
l Show top threads information:
diagnose sys top-all
Sample output:
Run Time: 86 days, 0 hours and 10 minutes
0U, 0N, 0S, 100I, 0WA, 0HI, 0SI, 0ST; 3040T, 2437F
bcm.user 93 S < 3.1 0.4
httpsd 18922 S 1.5 0.5
httpsd 19150 S 0.3 0.5
newcli 20195 R 0.1 0.1
cmdbsvr 115 S 0.0 0.8
pyfcgid 20107 S 0.0 0.6
forticron 146 S 0.0 0.5
httpsd 139 S 0.0 0.5
FortiOS 7.6.2 Administration Guide 4031
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,031
|
Troubleshooting
cw_acd 166 S 0.0 0.5
miglogd 136 S 0.0 0.5
pyfcgid 20110 S 0.0 0.4
pyfcgid 20111 S 0.0 0.4
pyfcgid 20109 S 0.0 0.4
httpsd 20192 S 0.0 0.4
miglogd 174 S 0.0 0.4
miglogd 175 S 0.0 0.4
fgfmd 165 S 0.0 0.3
newcli 20191 S 0.0 0.3
initXXXXXXXXXXX 1 S 0.0 0.3
httpsd 184 s 0.0 0.3
The following table explains the codes in the second line of the output:
Code Description
U Percentage of user space applications that are currently using the CPU
N Percentage of time that the CPU spent on low priority processes since the last shutdown
S Percentage of system processes (or kernel processes) that are using the CPU
I Percentage of idle CPU resources
WA Percentage of time that the CPU spent waiting on IO peripherals since the last shutdown
HI Percentage of time that the CPU spent handling hardware interrupt routines since the last shutdown
SI Percentage of time that the CPU spent handling software interrupt routines since the last shutdown
ST Steal time: Percentage of time a virtual CPU waits for the physical CPU when the hypervisor is
servicing another virtual processor
T Total FortiOS system memory in MB
F Free memory in MB
Each additional line of the command output displays information specific to processes or threads that are running on the
FortiGate unit. For example, the sixth line of the output is: newcli 20195 R 0.1 0.1
The following table describes the data in the sixth line of the output:
Item Description
newcli The process (or thread) name.
Duplicate process or thread names indicate that separate instances of that process or thread are
running.
20195 The process or thread ID, which can be any number.
R Current state of the process or thread. The process or thread state can be:
l R - running
l S - sleep
l Z - zombie
l D- disk sleep
0.1 The percentage of CPU capacity that the process or thread is using.
FortiOS 7.6.2 Administration Guide 4032
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,032
|
Troubleshooting
Item Description
CPU usage can range from 0.0 for a process or thread that is sleeping to higher values for a process
or thread that's taking a lot of CPU time.
0.1 The amount of memory that the process or thread is using.
Memory usage can range from 0.1 to 5.5 and higher.
You can use the following single-key commands when running diagnose sys top or diagnose sys top-all:
l q to quit and return to the normal CLI prompt.
l p to sort the processes by the amount of CPU that the processes are using.
l m to sort the processes by the amount of memory that the processes are using.
The output only displays the top processes or threads that are running. For example, if 20 are listed, they are the top 20
currently running, sorted by either CPU or memory usage. You can configure the number of processes or threads
displayed, using the following CLI commands:
diagnose sys top <integer_seconds> <integer_maximum_lines>
diagnose sys top-all <integer_seconds> <integer_maximum_lines>
Where:
l <integer_seconds> is the delay in seconds (default is 5)
l <integer_maximum_lines> is the maximum number of lines (or processes) to list (default is 20)
Determining which features are using the most CPU resources
You can use the CLI to view the top few processes that are currently running and using the most CPU resources.
To view processes using the most CPU resources:
get system performance top
The entries at the top are using the most CPU resources. The second column from the right shows CPU usage by
percentage. Note which processes are using the most resources and try to reduce their CPU load.
Processes you will see include:
l ipsengine: the IPS engine that scans traffic for intrusions
l scanunitd: antivirus scanner
l httpsd: secure HTTP
l iked: internet key exchange (IKE) in use with IPsec VPN tunnels
l newcli: active whenever you're accessing the CLI
l sshd: there are active secure socket connections
l cmdbsrv: the command database server application
Go to the features that are at the top of the list and look for evidence of CPU overuse. Generally, the monitor for a feature
is a good place to start.
FortiOS 7.6.2 Administration Guide 4033
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,033
|
Troubleshooting
Checking for unnecessary CPU “wasters”
These are some best practices that will reduce your CPU usage, even if the FortiGate is not experiencing high CPU
usage. Note that if the following information instructs you to turn off a feature that you require, disregard that part of the
instructions.
l Use hardware acceleration wherever possible to offload tasks from the CPU. Offloading tasks, such as encryption,
frees up the CPU for other tasks.
l Schedule antivirus, IPS, and firmware updates during off-peak hours. These updates do not usually consume CPU
resources but they can disrupt normal operation.
l Check the log levels and which events are being logged. This is the severity of the messages that are recorded.
Consider going up one level to reduce the amount of logging. Also, if there are events you do not need to monitor,
remove them from the list.
l Log to FortiCloud instead of logging to memory or disk. Logging to memory quickly uses up resources and logging
to local disk impacts overall performance and reduces the lifetime of the unit.
Fortinet recommends logging to FortiCloud to avoid using too much CPU.
l If the disk is almost full, transfer the logs or data off the disk to free up space. When a disk is almost full it consumes
a lot of resources to find free space and organize the files.
l If packet logging is enabled on the FortiGate, consider disabling it. When packet logging is enabled, it records every
packet that comes through that policy.
l Halt all sniffers and traces.
l Ensure the FortiGate isn't scanning traffic twice. Traffic does not need to be rescanned if it enters the FortiGate on
one interface, goes out another, and then comes back in again. Doing so is a waste of resources. However, ensure
that traffic truly is being scanned once.
l Reduce the session timers to close unused sessions faster. Enter the following CLI commands, which reduce the
default values. Note that, by default, the system adds 10 seconds to tcp-timewait.
config system global
set tcp-halfclose-timer 30
set tcp-halfopen-timer 30
set tcp-timewait-timer 0
set udp-idle-timer 60
end
l Go to System > Feature Visibility, and enable only features that you need.
SNMP monitoring
When CPU usage is under control, use SNMP to monitor CPU usage. Alternatively, use logging to record CPU and
memory usage every 5 minutes.
Once the system is back to normal, you should set up a warning system that sends alerts when CPU resources are used
excessively. A common method to do this is using SNMP. SNMP monitors many values in FortiOS and allows you to set
high water marks that generate events. You can run an application on your computer to watch for and record these
events.
To enable SNMP:
1. Go to System > SNMP.
2. Configure an SNMP community.
See SNMP on page 3289.
FortiOS 7.6.2 Administration Guide 4034
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,034
|
Troubleshooting
You can use the System Resources widget to record CPU usage if SNMP is too complicated.
However, the widget only records problems as they happen and will not send you alerts for
problems.
Checking the modem status
You can use the CLI to troubleshoot a modem that is not working properly, or troubleshoot a FortiGate that does not
detect the modem.
To diagnose modem issues in the CLI:
diagnose sys modem {cmd | com | detect | history | external-modem | query| reset}
You should always run the following command after you connect a USB modem to FortiGate:
diagnose sys modem detect
Use the following command to view the modem's configuration, vendor and custom product identification number:
get system modem
Use the following commands to resolve connectivity issues:
l diagnose debug enable: Activates the debug on the console
l diagnose debug application modemd: Dumps communication between the modem and the unit.
l diagnose debug application ppp: Dumps the PPP negotiating messages.
l execute modem dial: Displays modem debug output.
The modem diagnose output should not contain errors when initializing. You should also verify the number used to dial
into your ISP.
Running ping and traceroute
Ping and traceroute are useful tools in network troubleshooting. Alone, either tool can determine network connectivity
between two points. However, ping can be used to generate simple network traffic that you can view using diagnose
commands in FortiGate. This combination can be very powerful when you are trying to locate network problems.
Ping and traceroute can also tell you if your computer or network device has access to a domain name server (DNS).
Both tools can use IP addresses or device domain names to determine why particular services, such as email or web
browsing, may not work properly.
If ping does not work, it may be disabled on at least one of the interface settings and security
policies for that interface.
Both ping and traceroute require particular ports to be open on firewalls to function. Since you typically use these tools to
troubleshoot, you can allow them in the security policies and on interfaces only when you need them. Otherwise, keep
the ports disabled for added security.
FortiOS 7.6.2 Administration Guide 4035
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,035
|
Troubleshooting
Ping
The ping command sends a very small packet to a destination, and waits for a response. The response has a timer that
expires when the destination is unreachable.
Ping is part of layer 3 on the OSI Networking Model. Ping sends Internet Control Message Protocol (ICMP) “echo
request” packets to the destination, and listens for “echo response” packets in reply. However, many public networks
block ICMP packets because ping can be used in a denial of service (DoS) attack (such as Ping of Death or a smurf
attack), or by an attacker to find active locations on the network. By default, FortiGate units have ping enabled while
broadcast-forward is disabled on the external interface.
What ping can tell you
Beyond the basic connectivity information, ping can tell you the amount of packet loss (if any), how long it takes the
packet to make the round trip, and the variation in that time from packet to packet.
If packet loss is detected, you should investigate the following:
l Possible ECMP, split horizon, or network loops.
l Cabling, to ensure there are no loose connections.
l Verify which security policy was used. To do this:
Go to Policy & Objects > Firewall Policy and view the packet count column.
If there is total packet loss, you should investigate the following:
1. Ensure cabling is correct, and all equipment between the two locations is accounted for.
2. Ensure all IP addresses and routing information along the route is configured as expected.
3. Ensure all firewalls, including FortiGate security policies allow PING to pass through.
FortiGate ping options
Use the following CLI to view all the FortiGate ping options:
execute ping-options ?
adaptive-ping Adaptive ping <enable|disable>.
data-size Integer value to specify datagram size in bytes.
df-bit Set DF bit in IP header <yes | no>.
interface Auto | <outgoing interface>.
interval Integer value to specify seconds between two pings.
pattern Hex format of pattern, e.g. 00ffaabb.
repeat-count Integer value to specify how many times to repeat PING.
reset Reset settings.
source Auto | <source interface IP>.
timeout Integer value to specify timeout in seconds.
tos IP type-of-service option.
ttl Integer value to specify time-to-live.
use-sdwan Use SD-WAN rules to get output interface <yes | no>.
validate-reply Validate reply data <yes | no>.
view-settings View the current settings for PING option.
adaptive-ping {enable |
disable}
Enable or disable adaptive ping. FortiGate sends the next packet after the last
response is received.
FortiOS 7.6.2 Administration Guide 4036
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,036
|
Troubleshooting
data-size <integer> Specify the size of data in bytes. The size excludes ICMP header information. The
data size allows you to control the ICMP datagram size to test the effects of
different packet sizes on the connection.
Enter an integer value from <0> to <65507>.
df-bit {yes | no} Don't fragment bit. Prevent or allow the ICMP packet to fragment:
l yes: Prevent the ICMP packet from being fragmented.
l no: Allow the ICMP packet to be fragmented.
interface {auto |
<outgoing
interface>}
Specify the outgoing interface:
l auto: Automatically select the interface based on the destination and routing
table.
l <outgoing interface>: Manually specify the interface to be used for
ping. When source is specified, the IP address will be used as the ping
source IP.
interval <integer> Specify the time between pings in seconds.
Enter an integer value from <1> to <2147483647>.
pattern <string> Specify a pattern in hex format, for example, 00ffaabb, to be used in the data
section of the ICMP packet.
repeat-count <integer> Specify how many times to repeat the ping attempt.
Enter an integer value from <1> to <2147483647>.
reset Reset ping options to default values.
source {auto | <source
interface IP>}
Specify the source IP address to use for sending out ping:
l auto: Selects the primary IP address of the source interface.
l <source interface ip>: Specify a source IP address for the interface
used.
timeout <integer> Specify in seconds how long to wait until the ping times out.
Enter an integer value from <0> to <2147483647>.
tos Set the type of service (ToS) field in the packet header to indicate the desired
quality of service:
l default: Defaults to 0.
l lowcost: Minimize the cost.
l lowdelay: Minimize the delay.
l reliability: Maximize reliability.
l throughput: Maximize throughput.
ttl <integer> Specify the time to live. Time to live is the number of hops the ping packet should
be allowed to make before being discarded or returned.
Enter an integer value from <1> to <1255>.
use-sdwan {yes | no} Specify whether to use SD-WAN rules and policy routes.
l yes: The ping follows SD-WAN rules and policy routes. Usually used with
other options, such as source, to match a specific SD-WAN rule that is based
on a specific source address.
FortiOS 7.6.2 Administration Guide 4037
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,037
|
Troubleshooting
l no: Do not follow SD-WAN rules and policy routes.
validate-reply {yes | no} Specify whether to validate reply data:
l yes: Validate reply data.
l no: Do not validate reply data.
view-settings Display the current ping option settings.
How to use ping
Ping syntax is the same for nearly every type of system on a network.
To ping from a FortiGate unit:
1. Go to Dashboad, and connect to the CLI through either telnet or the CLI widget.
2. Enter execute ping 10.11.101.101 to send 5 ping packets to the destination IP address.
To modify ping options, first apply your changes using the command execute ping-options <option>
<setting>.
# execute ping 10.11.101.101
PING 10.11.101.101 (10.11.101.101): 56 data bytes
64 bytes from 10.11.101.101: icmp_seq=0 ttl=255 time=0.3 ms
64 bytes from 10.11.101.101: icmp_seq=1 ttl=255 time=0.2 ms
64 bytes from 10.11.101.101: icmp_seq=2 ttl=255 time=0.2 ms
64 bytes from 10.11.101.101: icmp_seq=3 ttl=255 time=0.2 ms
64 bytes from 10.11.101.101: icmp_seq=4 ttl=255 time=0.2 ms
--- 10.11.101.101 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.2/0.2/0.3 ms
3. Enter the domain name to test name resolution.
# execute ping google.com
PING google.com (142.250.179.78): 56 data bytes
To ping from a Microsoft Windows PC:
1. Open a command window.
2. Enter ping 10.11.101.100 to ping the default internal interface of the FortiGate with four packets.
Other options include:
l -t to send packets until you press Ctrl+C
l -a to resolve addresses to domain names where possible
l -n X to send X ping packets and stop
C:\>ping 10.11.101.101
Pinging 10.11.101.101 with 32 bytes of data:
Reply from 10.11.101.101: bytes=32 time=10ms TTL=255
Reply from 10.11.101.101: bytes=32 time<1ms TTL=255
Reply from 10.11.101.101: bytes=32 time=1ms TTL=255
Reply from 10.11.101.101: bytes=32 time=1ms TTL=255
Ping statistics for 10.11.101.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
FortiOS 7.6.2 Administration Guide 4038
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,038
|
Troubleshooting
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 3ms
To ping from a Linux PC:
1. Go to a shell prompt.
2. Enter “ping 10.11.101.101”.
Traceroute
Where ping will only tell you if it reached its destination and returned successfully, traceroute shows each step of the
journey to its destination and how long each step takes. If ping finds an outage between two points, you can use
traceroute to locate exactly where the problem is.
Traceroute works by sending ICMP packets to test each hop along the route. It sends three packets, and then increases
the time to live (TTL) setting by one each time. This effectively allows the packets to go one hop farther along the route.
This is why most traceroute commands display their maximum hop count before they start tracing the route, which is the
maximum number of steps it takes before it declares the destination unreachable. Also, the TTL setting may result in
steps along the route timing out due to slow responses. There are many possible reasons for this to occur.
By default, traceroute uses UDP datagrams with destination ports numbered from 33434 to 33534. The traceroute utility
may also offer the option to select use of ICMP echo request (type 8) instead, which the Windows tracert utility uses. If
you must, allow both protocols inbound through the FortiGate security policies (UDP with ports from 33434 to 33534 and
ICMP type 8).
To track traceroute packets in the GUI:
Go to Policy & Objects > Firewall Policy and view the packet count column.
This allows you to verify the connection and confirm which security policy the traceroute packets are using.
What traceroute can tell you
Both ping and traceroute verify connectivity between two points. However, only traceroute shows you each step in the
connection path. Also, ping and traceroute use different protocols and ports, so one may succeed where the other fails.
You can verify your DNS connection using traceroute. If you enter an FQDN instead of an IP address for the traceroute,
DNS tries to resolve that domain name. If the name isn't resolved, you have DNS issues.
Using traceroute
The traceroute command varies slightly between operating systems. In Microsoft Windows, the command name is
shortened to “tracert”. Also, your output lists different domain names and IP addresses along your route.
To use traceroute on a Microsoft Windows PC:
1. Open a command window.
2. Enter tracert fortinet.com to trace the route from the PC to the Fortinet web site.
C:\>tracert fortinet.com
Tracing route to fortinet.com [208.70.202.225]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 172.20.120.2
2 66 ms 24 ms 31 ms 209-87-254-xxx.storm.ca [209.87.254.221]
FortiOS 7.6.2 Administration Guide 4039
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,039
|
Troubleshooting
3 52 ms 22 ms 18 ms core-2-g0-0-1104.storm.ca [209.87.239.129]
4 43 ms 36 ms 27 ms core-3-g0-0-1185.storm.ca [209.87.239.222]
5 46 ms 21 ms 16 ms te3-x.1156.mpd01.cogentco.com [38.104.158.69]
6 25 ms 45 ms 53 ms te8-7.mpd01.cogentco.com [154.54.27.249]
7 89 ms 70 ms 36 ms te3-x.mpd01.cogentco.com [154.54.6.206]
8 55 ms 77 ms 58 ms sl-st30-chi-.sprintlink.net [144.232.9.69]
9 53 ms 58 ms 46 ms sl-0-3-3-x.sprintlink.net [144.232.19.181]
10 82 ms 90 ms 75 ms sl-x-12-0-1.sprintlink.net [144.232.20.61]
11 122 ms 123 ms 132 ms sl-0-x-0-3.sprintlink.net [144.232.18.150]
12 129 ms 119 ms 139 ms 144.232.20.7
13 172 ms 164 ms 243 ms sl-321313-0.sprintlink.net [144.223.243.58]
14 99 ms 94 ms 93 ms 203.78.181.18
15 108 ms 102 ms 89 ms 203.78.176.2
16 98 ms 95 ms 97 ms 208.70.202.225
The first column on the left is the hop count, which cannot exceed 30 hops. When that number is reached, the
traceroute ends.
The second, third, and fourth columns display how much time each of the three packets takes to reach this stage of
the route. These values are in milliseconds and normally vary quite a bit. Typically a value of <1ms indicates a local
connection.
The fifth column (farthest to the right) shows the domain name of the device and its IP address, or possibly only the
IP address.
To perform a traceroute on a Linux PC:
1. Go to a command line prompt.
2. Enter “traceroute fortinet.com”.
The Linux traceroute output is very similar to the Windows tracert output.
To trace a route from a FortiGate to a destination IP address in the CLI:
# execute traceroute www.fortinet.com
traceroute to www.fortinet.com (66.171.121.34), 32 hops max, 84 byte packets
1 172.20.120.2 0.637 ms 0.653 ms 0.279 ms
2 209.87.254.221 <static-209-87-254-221.storm.ca> 2.448 ms 2.519 ms 2.458 ms
3 209.87.239.129 <core-2-g0-2.storm.ca> 2.917 ms 2.828 ms 9.324 ms
4 209.87.239.199 <core-3-bdi1739.storm.ca> 13.248 ms 12.401 ms 13.009 ms
5 216.66.41.113 <v502.core1.tor1.he.net> 17.181 ms 12.422 ms 12.268 ms
6 184.105.80.9 <100ge1-2.core1.nyc4.he.net> 21.355 ms 21.518 ms 21.597 ms
7 198.32.118.41 <ny-paix-gni.twgate.net> 83.297 ms 84.416 ms 83.782 ms
8 203.160.228.217 <217-228-160-203.TWGATE-IP.twgate.net> 82.579 ms 82.187 ms 82.066 ms
9 203.160.228.229 <229-228-160-203.TWGATE-IP.twgate.net> 82.055 ms 82.455 ms 81.808 ms
10 203.78.181.2 82.262 ms 81.572 ms 82.015 ms
11 203.78.186.70 83.283 ms 83.243 ms 83.293 ms
12 66.171.127.177 84.030 ms 84.229 ms 83.550 ms
13 66.171.121.34 <www.fortinet.com> 84.023 ms 83.903 ms 84.032 ms
14 66.171.121.34 <www.fortinet.com> 83.874 ms 84.084 ms 83.810 ms
FortiOS 7.6.2 Administration Guide 4040
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,040
|
Troubleshooting
Checking the logs
A log message records the traffic passing through FortiGate to your network and the action FortiGate takes when it
scans the traffic. You should log as much information as possible when you first configure FortiOS. If FortiGate logs are
too large, you can turn off or scale back the logging for features that are not in use.
It is difficult to troubleshoot logs without a baseline. Before you can determine if the logs indicate a problem, you need to
know what logs result from normal operation.
When troubleshooting with log files
l Compare current logs to a recorded baseline of normal operation.
l If you need to, increase the level of logging (such as from Warning to Information) to obtain more information.
When increasing logging levels, ensure that you configure email alerts and select both disk usage and log quota.
This ensures that you will be notified if the increase in logging causes problems.
To configure the log settings in the GUI:
Go to Log & Report > Log Settings.
Determine the activities that generate the most log entries:
l Check all logs to ensure important information is not overlooked.
l Filter or order log entries based on different fields, such as level, service, or IP address, to look for patterns that may
indicate a specific problem, such as frequent blocked connections on a specific port for all IP addresses.
Logs can help identify and locate any problems, but they do not solve them. The purpose of logs is to speed up your
problem solving and save you time and effort.
For more information about logging and log reports, see Log and Report on page 3855.
Verifying routing table contents in NAT mode
Verify the contents of the routing table when a FortiGate has limited or no connectivity.
The routing table stores the routes currently in use for both static and dynamic protocols. Storing a route in the routing
table saves time and resources performing a lookup. To ensure the most recently used routes remain in the table, old
routes are bumped to make room for new ones. You cannot perform this task when FortiGate is in transparent mode.
If FortiGate is running in NAT mode, verify that all desired routes are in the routing table, including local subnets, default
routes, specific static routes, and dynamic routing protocols.
To view the routing table in the CLI:
get router info routing-table all
Sample output:
FGT# get router info routing-table all
Codes:
K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
FortiOS 7.6.2 Administration Guide 4041
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,041
|
Troubleshooting
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default
S* 0.0.0.0/0 [10/0] via 172.20.120.2, wan1
C 10.31.101.0/24 is directly connected, internal
C 172.20.120.0/24 is directly connected, wan1
Verifying the correct route is being used
Run a trace route from a machine in the local area network (LAN) to ensure traffic is flowing as expected through the
correct route when there is more than one default route.
In the following example output:
l The first hop contains the IP address 10.10.1.99, which is the internal interface of the FortiGate.
l The second hop contains the IP address 172.20.120.2, to which the wan1 interface of the FortiGate is
connected.
This means the route through the wan1 interface is being used for this traffic.
C:\>tracert www.fortinet.com
Tracing route to www.fortinet.com [66.171.121.34]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.1.99
2 1 ms <1 ms <1 ms 172.20.120.2
3 3 ms 3 ms 3 ms static-209-87-254-221.storm.ca [209.87.254.221]
4 3 ms 3 ms 3 ms core-2-g0-2.storm.ca [209.87.239.129]
5 13 ms 13 ms 13 ms core-3-bdi1739.storm.ca [209.87.239.199]
6 12 ms 19 ms 11 ms v502.core1.tor1.he.net [216.66.41.113]
7 22 ms 22 ms 21 ms 100ge1-2.core1.nyc4.he.net [184.105.80.9]
8 84 ms 84 ms 84 ms ny-paix-gni.twgate.net [198.32.118.41]
9 82 ms 84 ms 82 ms 217-228-160-203.TWGATE-IP.twgate.net [203.160.22
8.217]
10 82 ms 81 ms 82 ms 229-228-160-203.TWGATE-IP.twgate.net [203.160.22
8.229]
11 82 ms 82 ms 82 ms 203.78.181.2
12 84 ms 83 ms 83 ms 203.78.186.70
13 84 ms * 85 ms 66.171.127.177
14 84 ms 84 ms 84 ms fortinet.com [66.171.121.34]
15 84 ms 84 ms 83 ms fortinet.com [66.171.121.34]
You can also see the route taken for each session by debugging the packet flow in the CLI. For more information, see
Debugging the packet flow on page 4047.
Verifying the correct firewall policy is being used
If you have more than one firewall policy, you can check which policy is being used in the Policy & Objects module in the
GUI.
To verify the firewall policy in the GUI:
1. Go to Policy & Objects > Firewall Policy.
2. Look in the Count column to see which policy is being used. The count must show traffic increasing.
FortiOS 7.6.2 Administration Guide 4042
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,042
|
Troubleshooting
Debugging the packet flow in the CLI shows the policy ID that's allowing the traffic. For information, see Debugging the
packet flow on page 4047.
Checking the bridging information in transparent mode
Checking the bridging information is useful when you are experiencing connectivity problems. When FortiGate is set to
transparent mode, it acts like a bridge and sends all incoming traffic out on the other interfaces. Each bridge is a link
between interfaces.
When traffic is flowing between the interfaces, you can see the bridges listed in the CLI. If no bridges are listed, this is the
likely cause of the connectivity issue. When investigating bridging information, check for the MAC address of the
interface or device in question.
How to check the bridging information
To view the list of bridge instances in the CLI:
diagnose netlink brctl list
Sample output:
#diagnose netlink brctl list
list bridge information
1. root.b fdb: size=256 used=6 num=7 depth=2 simple=no
Total 1 bridges
How to display forwarding domain information
You can use forwarding domains, or collision domains, in routing to limit where packets are forwarded on the network.
Layer 2 broadcasts are limited to the same group. By default, all interfaces are in group 0. For example, if the FortiGate
has 12 interfaces, only two may be in the same forwarding domain, which limits packets that are broadcast to those two
interfaces. This reduces traffic on the rest of the network.
Collision domains prevent the forwarding of ARP packets to all VLANs on an interface. Without collision domains,
duplicate MAC addresses on VLANs may cause ARP packets to be duplicated. Duplicate ARP packets can cause some
switches to reset. It's important to know what interfaces are part of which forwarding domains because this determines
which interfaces can communicate with each other.
To manually configure forwarding domains in transparent mode in the CLI:
config system interface
edit <interface_name>
set forward-domain <integer>
end
To display the forward domains information in the CLI:
diagnose netlink brctl domain <name> <id>
Where <name> is the name of the forwarding domain to display and <id> is the domain ID.
FortiOS 7.6.2 Administration Guide 4043
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,043
|
Troubleshooting
Sample output:
diagnose netlink brctl domain ione 101
show bridge root.b ione forward domain.
id=101 dev=trunk_1 6
To list the existing bridge MAC table in the CLI:
diagnose netlink brctl name host <name>
Sample output:
show bridge control interface root.b host.
fdb: size=256, used=6, num=7, depth=2, simple=no
Bridge root.b host table
port no device devname mac addr ttl attributes
2 7 wan2 02:09:0f:78:69:00 0 Local Static
5 6 vlan_1 02:09:0f:78:69:01 0 Local Static
3 8 dmz 02:09:0f:78:69:01 0 Local Static
4 9 internal 02:09:0f:78:69:02 0 Local Static
3 8 dmz 00:80:c8:39:87:5a 194
4 9 internal 02:09:0f:78:67:68 8
1 3 wan1 00:09:0f:78:69:fe 0 Local Static
To list the existing bridge port list in the CLI:
diagnose netlink brctl name port <name>
Sample output:
show bridge root.b data port.
trunk_1 peer_dev=0
internal peer_dev=0
dmz peer_dev=0
wan2 peer_dev=0
wan1 peer_dev=0
Checking wireless information
Check wireless connections, stations, and interfaces when the problem is not caused by a physical interface.
Troubleshooting station connection issues
To check if a station entry is created on access control in the CLI:
FG600B3909600253 # diagnose wireless-controller wlac -d sta
* vf=0 wtp=70 rId=2 wlan=open ip=0.0.0.0 mac=00:09:0f:db:c4:03 rssi=0 idle=148 bw=0 use=2
vf=0 wtp=70 rId=2 wlan=open ip=172.30.32.122 mac=00:25:9c:e0:47:88 rssi=-40 idle=0 bw=9
use=2
FortiOS 7.6.2 Administration Guide 4044
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,044
|
Troubleshooting
Enabling diagnostics for a specific station
This example uses the station MAC address to find where it is failing:
FG600B3909600253 # diagnose wireless-controller wlac sta_filter 00:25:9c:e0:47:88 1
Set filter sta 00:25:9c:e0:47:88 level 1
FG600B3909600253 # 71419.245 <ih> IEEE 802.11 mgmt::disassoc <== 00:25:9c:e0:47:88 vap open
rId 1 wId 0 00:09:0f:db:c4:03
71419.246 <dc> STA del 00:25:9c:e0:47:88 vap open rId 1 wId 0
71419.246 <cc> STA_CFG_REQ(34) sta 00:25:9c:e0:47:88 del ==> ws (0-192.168.35.1:5246) rId 1
wId 0
71419.246 <cc> STA del 00:25:9c:e0:47:88 vap open ws (0-192.168.35.1:5246) rId 1 wId 0
00:09:0f:db:c4:03 sec open reason I2C_STA_DEL
71419.247 <cc> STA_CFG_RESP(34) 00:25:9c:e0:47:88 <== ws (0-192.168.35.1:5246) rc 0
(Success).
Performing a sniffer trace or packet capture
When you troubleshoot networks and routing in particular, it helps to look inside the headers of packets to determine if
they are traveling the route that you expect them to take. Packet sniffing is also known as network tap, packet capture, or
logic analyzing.
System event logs are generated when a packet capture is started or stopped in the GUI, and when a sniffer operation is
started or stopped in the CLI.
For more information on controlling GUI packet captures in the CLI, see Using the packet capture tool on page 828.
For FortiGates with NP2, NP4, or NP6 interfaces that are offloading traffic, disable offloading
on these interfaces before you perform a trace or it will change the sniffer trace.
Sniffing packets
To perform a sniffer trace in the CLI:
Before you start sniffing packets, you should prepare to capture the output to a file. A large amount of data may scroll by
and you will not be able to see it without saving it first. One method is to use a terminal program like PuTTY to connect to
the FortiGate CLI. Once the packet sniffing count is reached, you can end the session and analyze the output in the file.
The general form of the internal FortiOS packet sniffer command is:
# diagnose sniffer packet <interface_name> <'filter'> <verbose> <count> <tsformat>
To stop the sniffer, type CTRL+C.
<interface_name> The name of the interface to sniff, such as port1 or internal. This can also be
any to sniff all interfaces.
<'filter'> What to look for in the information the sniffer reads. none indicates no filtering,
and all packets are displayed as the other arguments indicate.
The filter must be inside single quotes (‘).
FortiOS 7.6.2 Administration Guide 4045
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,045
|
Troubleshooting
<verbose> The level of verbosity as one of:
l 1 - print header of packets
l 2 - print header and data from IP of packets
l 3 - print header and data from Ethernet of packets
l 4 - print header of packets with interface name
l 5 - print header and data from IP of packets with interface name
l 6 - print header and data from Ethernet of packets with interface name
<count> The number of packets the sniffer reads before stopping. If you don't put a
number here, the sniffer will run until you stop it with <CTRL+C>.
<tsformat> The timestamp format.
l a: absolute UTC time, yyyy-mm-dd hh:mm:ss.ms
l l: absolute LOCAL time, yyyy-mm-dd hh:mm:ss.ms
l otherwise: relative to the start of sniffing, ss.ms
Simple sniffing example:
# diagnose sniffer packet port1 none 1 3.
This displays the next three packets on the port1 interface using no filtering, and verbose level 1. At this verbosity level,
you can see the source IP and port, the destination IP and port, action (such as ack), and sequence numbers.
In the output below, port 443 indicates these are HTTPS packets and that 172.20.120.17 is both sending and receiving
traffic.
Head_Office_620b # diagnose sniffer packet port1 none 1 3
interfaces=[port1]
filters=[none]
0.545306 172.20.120.17.52989 -> 172.20.120.141.443: psh 3177924955 ack 1854307757
0.545963 172.20.120.141.443 -> 172.20.120.17.52989: psh 1854307757 ack 3177925808
0.562409 172.20.120.17.52988 -> 172.20.120.141.443: psh 4225311614 ack 3314279933
Using packet capture in a firewall policy
FortiGate can capture packets matching a firewall policy. You can enable capture-packet in the firewall policy.
To use packet capture, the FortiGate must have a disk and logging must be enabled in the firewall policy.
For information about using the packet capture tool in the GUI, see Using the packet capture tool on page 828.
To enable packet capture in a policy in the GUI:
1. Go to Policy & Objects > Firewall Policy and click Create New.
2. Enter a name for the policy and configure the required settings.
3. Enable Log Allowed Traffic and select Security Events or All Sessions.
4. Enable Capture Packets.
5. Click OK.
FortiOS 7.6.2 Administration Guide 4046
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,046
|
Troubleshooting
To enable packet capture in a policy in the CLI:
config firewall policy
edit <id>
set action accept
set logtraffic {all | utm}
set capture-packet enable
next
end
To view the packet capture:
1. Go to Log & Report > Forward Traffic and select the log that matches the firewall policy.
2. Select Details > Archived Data and click on the download button.
3. Open the downloaded PCAP file in a packet analyzer tool, such as Wireshark.
Debugging the packet flow
Debug the packet flow when network traffic is not entering and leaving the FortiGate as expected. When debugging the
packet flow in the CLI, each command configures a part of the debug action. The final command starts the debug.
For information about using the debug flow tool in the GUI, see Using the debug flow tool on page 832.
To trace the packet flow in the CLI:
# diagnose debug flow trace start
To follow packet flow by setting a flow filter:
# diagnose debug flow {filter | filter6} <option>
l Enter filter if your network uses IPv4.
l Enter filter6 if your network uses IPv6.
Replace <option> with one of the following variables:
Variable Description
addr IPv4 or IPv6 address
clear clear filter
daddr destination IPv4 or IPv6 address
FortiOS 7.6.2 Administration Guide 4047
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,047
|
Troubleshooting
Variable Description
dport destination port
negate inverse IPv4 or IPv6 filter
port port
proto protocol number
saddr source address
sport source port
vd index of virtual domain; -1 matches all
If FortiGate is connected to FortiAnalyzer or FortiCloud, the diagnose debug flow output will be
recorded as event log messages and then sent to the devices. Do not run this command
longer than necessary, as it generates a significant amount of data.
Flow monitoring does not work for traffic offloaded to NP6 or NP7 processors. To use the
diagnose debug flow commands with sessions offloaded to NP6 or NP7 processors you can
test the traffic flow using ICMP (ICMP traffic is not offloaded) or you can disable NP6 or NP7
offloading.
You can use the following command to temporarily disable NP6 offloading of all traffic:
diagnose npu {np6 | np6xlite | np6lite} fastpath disable
You must disable NP7 offloading in the firewall policy that accepts the traffic that you are
tracing, see Tracing packet flow on FortiGates with NP7 processors.
You can also use the NP7 packet sniffer to sniff NP7 offloaded traffic without disabling NP7
offloading, see NP7 packet sniffer.
To start flow monitoring with a specific number of packets:
# diagnose debug flow trace start <N>
To stop flow tracing at any time:
# diagnose debug flow trace stop
The following example shows the flow trace for a device with an IP address of 203.160.224.97:
# diagnose debug enable
# diagnose debug flow filter addr 203.160.224.97
# diagnose debug flow show function-name enable
# diagnose debug flow trace start 100
Sample output: HTTP
To observe the debug flow trace, connect to the website at the following address:
https://www.fortinet.com
Comment: SYN packet received:
FortiOS 7.6.2 Administration Guide 4048
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,048
|
Troubleshooting
id=20085 trace_id=209 func=resolve_ip_tuple_fast
line=2700 msg="vd-root received a packet(proto=6,
192.168.3.221:1487->203.160.224.97:80) from port5."
SYN sent and a new session is allocated:
id=20085 trace_id=209 func=resolve_ip_tuple line=2799
msg="allocate a new session-00000e90"
Lookup for next-hop gateway address:
id=20085 trace_id=209 func=vf_ip4_route_input line=1543
msg="find a route: gw-192.168.11.254 via port6"
Source NAT, lookup next available port:
id=20085 trace_id=209 func=get_new_addr line=1219
msg="find SNAT: IP-192.168.11.59, port-31925"
direction“
Matched security policy. Check to see which policy this session matches:
id=20085 trace_id=209 func=fw_forward_handler line=317
msg="Allowed by Policy-3: SNAT"
Apply source NAT:
id=20085 trace_id=209 func=__ip_session_run_tuple
line=1502 msg="SNAT 192.168.3.221->192.168.11.59:31925"
SYN ACK received:
id=20085 trace_id=210 func=resolve_ip_tuple_fast line=2700
msg="vd-root received a packet(proto=6, 203.160.224.97:80-
>192.168.11.59:31925) from port6."
Found existing session ID. Identified as the reply direction:
id=20085 trace_id=210 func=resolve_ip_tuple_fast line=2727
msg="Find an existing session, id-00000e90, reply direction"
Apply destination NAT to inverse source NAT action:
id=20085 trace_id=210 func=__ip_session_run_tuple
line=1516 msg="DNAT 192.168.11.59:31925-
>192.168.3.221:1487"
Lookup for next-hop gateway address for reply traffic:
id=20085 trace_id=210 func=vf_ip4_route_input line=1543
msg="find a route: gw-192.168.3.221 via port5"
ACK received:
id=20085 trace_id=211 func=resolve_ip_tuple_fast line=2700
msg="vd-root received a packet(proto=6,
192.168.3.221:1487->203.160.224.97:80) from port5."
Match existing session in the original direction:
id=20085 trace_id=211 func=resolve_ip_tuple_fast line=2727
msg="Find an existing session, id-00000e90, original
direction"
Apply source NAT:
id=20085 trace_id=211 func=__ip_session_run_tuple
line=1502 msg="SNAT 192.168.3.221->192.168.11.59:31925"
FortiOS 7.6.2 Administration Guide 4049
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,049
|
Troubleshooting
Receive data from client:
id=20085 trace_id=212 func=resolve_ip_tuple_fast
line=2700 msg="vd-root received a packet(proto=6,
192.168.3.221:1487->203.160.224.97:80) from port5."
Match existing session in the original direction:
id=20085 trace_id=212 func=resolve_ip_tuple_fast
line=2727 msg="Find an existing session, id-00000e90,
original direction"
Apply source NAT:
id=20085 trace_id=212 func=__ip_session_run_tuple
line=1502 msg="SNAT 192.168.3.221->192.168.11.59:31925"
Receive data from server:
id=20085 trace_id=213 func=resolve_ip_tuple_fast
line=2700 msg="vd-root received a packet(proto=6,
203.160.224.97:80->192.168.11.59:31925) from port6."
Match existing session in reply direction:
id=20085 trace_id=213 func=resolve_ip_tuple_fast
line=2727 msg="Find an existing session, id-00000e90,
reply direction"
Apply destination NAT to inverse source NAT action:
id=20085 trace_id=213 func=__ip_session_run_tuple
line=1516 msg="DNAT 192.168.11.59:31925-
>192.168.3.221:1487"
Sample output: IPsec (policy-based)
id=20085 trace_id=1 msg="vd-root received a packet(proto=1, 10.72.55.240:1->10.71.55.10:8)
from internal."
id=20085 trace_id=1 msg="allocate a new session-00001cd3"
id=20085 trace_id=1 msg="find a route: gw-66.236.56.230 via wan1"
id=20085 trace_id=1 msg="Allowed by Policy-2: encrypt"
id=20085 trace_id=1 msg="enter IPsec tunnel-RemotePhase1"
id=20085 trace_id=1 msg="encrypted, and send to 15.215.225.22 with source 66.236.56.226"
id=20085 trace_id=1 msg="send to 66.236.56.230 via intf-wan1“
id=20085 trace_id=2 msg="vd-root received a packet (proto=1, 10.72.55.240:1-1071.55.10:8)
from internal."
id=20085 trace_id=2 msg="Find an existing session, id-00001cd3, original direction"
id=20085 trace_id=2 msg="enter IPsec ="encrypted, and send to 15.215.225.22 with source
66.236.56.226“ tunnel-RemotePhase1"
id=20085 trace_id=2 msgid=20085 trace_id=2 msg="send to 66.236.56.230 via intf-wan1"
Testing a proxy operation
To monitor proxy operations in the CLI:
diagnose test application <application> <option>
FortiOS 7.6.2 Administration Guide 4050
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,050
|
Troubleshooting
To display a list of available application values:
diagnose test application ?
To display a list of available option values:
diagnose test application <application> ?
The <option> value will depend on the application value used in the command.
For example, if the application is http, the CLI command that displays the <option> values is:
diagnose test application http ?
Displaying detail Hardware NIC information
Monitoring the hardware NIC is important because interface errors indicate data link or physical layer issues which may
impact the performance of the FortiGate.
To monitor hardware network operations in the CLI:
diagnose hardware deviceinfo nic <interface>
or
diagnose netlink interface list <interface>
Sample output:
The following is sample output when the <interface> is set to port1:
# diagnose netlink interface list port1
if=port1 family=00 type=1 index=3 mtu=1500 link=0 master=0
flags=up broadcast run multicast
Qdisc=mq hw_addr=00:0c:29:fc:18:54 broadcast_addr=ff:ff:ff:ff:ff:ff
stat: rxp=61149 txp=81109 rxb=5839308 txb=52396373 rxe=0 txe=0 rxd=0 txd=0 mc=95 collision=0
@ time=1678486883
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0
misc rxc=0 txc=0
Field descriptions
The diagnose hardware deviceinfo nic and diagnose netlink interface list commands display lists
of error names and values that are related to hardware.
The following table describes possible hardware errors:
Field Description
Rx packets (rxp) Number of received packets.
Tx packets (txp) Number of transmitted packets.
FortiOS 7.6.2 Administration Guide 4051
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,051
|
Troubleshooting
Field Description
Rx bytes (rxb) Number of received bytes.
Tx bytes (txb) Number of transmitted bytes.
Rx_Errors (rxe) = rx
error count
Bad frame was marked as error by PHY.
Tx_Errors (txe) = Tx_
Aborted_Errors
ECOL (Excessive Collisions Count); only valid in half-duplex mode.
Rx_CRC_Errors +
Rx_Length_Errors -
Rx_Align_Errors
This error is only valid in 10/100M mode.
Rx_Dropped (rxd) or
Rx_No_Buffer_
Count
Running out of buffer space.
Tx_Dropped (txd) Number of dropped packet.
Multicast (mc) Number of multicast packets received.
Collisions Total number of collisions experienced by the transmitter; valid in half-duplex mode.
Rx_Length_Errors
(rxl)
Number of packets dropped due to invalid length.
Rx_Over_Errors
(rxo)
Receive FIFO overflow event counter.
Rx_CRC_Errors
(rxc)
Number of received packets with Frame CRC error.
Rx_Frame_Errors
(rxf)
Same as Rx_Align_Errors. This error is only valid in 10/100M mode.
Rx_FIFO_Errors
(rxfi)
Same as Rx_Missed_Errors - a missed packet count
Rx_Missed_Errors
(rxm)
Equals Rx_FIFO_Errors + CEXTERR (Carrier Extension Error Count). Only valid in 1000M
mode, which is marked by PHY.
Tx_Aborted_Errors
(txa)
See Tx_Errors.
Tx_Carrier_Errors
(txc)
The PHY should assert the internal carrier sense signal during every transmission. Failure to
do so may indicate that the link has failed or the PHY has an incorrect link configuration. This
register only increments if transmits are enabled. This register isn't valid in internal SerDes 1
mode (TBI mode for the 82544GC/EI) and is valid only when the Ethernet controller is
operating at full duplex.
Tx_FIFO_Errors (txfi) Number of Frame transmission error due to underflow.
FortiOS 7.6.2 Administration Guide 4052
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,052
|
Troubleshooting
Field Description
Tx_Heartbeat_Errors
(txh)
Number of heartbeat error.
Tx_Window_Errors
(txw)
Late Collisions (LATECOL) Count
Late collisions are collisions that occur after 64-byte time into the transmission of the packet
while working in 10 to 100 Mb/s data rate and 512-byte time into the transmission of the
packet while working in the 1,000 Mb/s data rate. This register only increments if transmits are
enabled and the device is in half-duplex mode.
Rx compressed
(misc rxc)
Number of received compressed packets.
Tx compressed (misc
txc)
Number of transmitted compressed packets.
Tx_Single_Collision_
Frames
Counts the number of times that a successfully transmitted packet encountered a single
collision.
The value increments only if transmits are enabled and the Ethernet controller is in half-duplex
mode.
Tx_Multiple_
Collision_Frames
A Multiple Collision Count which indicates the number of times that a transmit encountered
more than one collision, but less than 16. The value increments only if transmits are enabled
and the Ethernet controller is in half-duplex mode.
Tx_Deferred Counts defer events.
A deferred event occurs when the transmitter cannot immediately send a packet due to:
l The medium being busy because another device is transmitting.
l The IPG timer has not expired.
l Half-duplex deferral events are occurring.
l XOFF frames are being received .
l The link is not up.
This register only increments if transmits are enabled. This counter does not increment for
streaming transmits that are deferred due to TX IPG.
Rx_Frame_Too_
Longs
The Rx frame is oversized.
Rx_Frame_Too_
Shorts
The Rx frame is too short.
Rx_Align_Errors This error is only valid in 10/100M mode.
Symbol Error Count Counts the number of symbol errors (SYMERRS) between reads.
The count increases for every bad symbol that's received, whether or not a packet is currently
being received and whether or not the link is up. This register increments only in internal
SerDes mode.
FortiOS 7.6.2 Administration Guide 4053
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,053
|
Troubleshooting
Performing a traffic trace
Traffic tracing allows you to follow a specific packet stream. This is useful when you want to confirm that packets are
using the route you expect them to take on your network.
To view traffic sessions:
Use this command to view the characteristics of a traffic session though specific security policies.
diagnose sys session
To trace per-packet operations for flow tracing:
diagnose debug flow
To trace per-Ethernet frame:
diagnose sniffer packet
To trace a route from a FortiGate to a destination IP address:
# execute traceroute www.fortinet.com
traceroute to www.fortinet.com (66.171.121.34), 32 hops max, 84 byte packets
1 172.20.120.2 0.637 ms 0.653 ms 0.279 ms
2 209.87.254.221 <static-209-87-254-221.storm.ca> 2.448 ms 2.519 ms 2.458 ms
3 209.87.239.129 <core-2-g0-2.storm.ca> 2.917 ms 2.828 ms 9.324 ms
4 209.87.239.199 <core-3-bdi1739.storm.ca> 13.248 ms 12.401 ms 13.009 ms
5 216.66.41.113 <v502.core1.tor1.he.net> 17.181 ms 12.422 ms 12.268 ms
6 184.105.80.9 <100ge1-2.core1.nyc4.he.net> 21.355 ms 21.518 ms 21.597 ms
7 198.32.118.41 <ny-paix-gni.twgate.net> 83.297 ms 84.416 ms 83.782 ms
8 203.160.228.217 <217-228-160-203.TWGATE-IP.twgate.net> 82.579 ms 82.187 ms 82.066 ms
9 203.160.228.229 <229-228-160-203.TWGATE-IP.twgate.net> 82.055 ms 82.455 ms 81.808 ms
10 203.78.181.2 82.262 ms 81.572 ms 82.015 ms
11 203.78.186.70 83.283 ms 83.243 ms 83.293 ms
12 66.171.127.177 84.030 ms 84.229 ms 83.550 ms
13 66.171.121.34 <www.fortinet.com> 84.023 ms 83.903 ms 84.032 ms
14 66.171.121.34 <www.fortinet.com> 83.874 ms 84.084 ms 83.810 ms
Using a session table
A session is a communication channel between two devices or applications across the network. Sessions allow FortiOS
to inspect and act on a sequential group of packets in a session all at once instead of inspecting each packet individually.
Each session has an entry in the session table that includes important information about the session.
You can view FortiGate session tables from the FortiGate GUI or CLI. The most useful troubleshooting data comes from
the CLI. The session table in the GUI also provides useful summary information, particularly the current policy number
that the session is using.
When to use a session table
Session tables are useful when verifying open connections. For example, if you have a web browser open to browse the
Fortinet website, you would expect a session entry from your computer on port 80 to the IP address for the Fortinet
FortiOS 7.6.2 Administration Guide 4054
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
4,054
|
Troubleshooting
website.
You can also use a session table to investigate why there are too many sessions for FortiOS to process.
GUI
To view session information in the GUI:
1. Go to Security Fabric > Physical Topology.
2. From the Metrics dropdown, select Sessions.
Finding the security policy for a specific connection
Every program and device on your network must have an open communication channel or session to pass information.
FortiGate manages these sessions with features such as traffic shaping, antivirus scanning, and blocking known bad
websites. Each session will have an entry in the session table.
If a secure web browser session is not working properly, you can check the session table to ensure the session is still
active and going to the proper address. The session table can also tell you the security policy number it matches, so you
can check what is happening in that policy.
1. Get the connection information.
You need to be able to identify the session you want. To do this, you will need:
l The source IP address (usually your computer)
l The destination IP address (if you have it)
l The port number which is determined by the program you are using. Common ports are:
l Port 80 (HTTP for web browsing)
l Port 443 (HTTPS for SSL encrypted web browsing)
l Port 22 (SSH for Secure Shell)
l Port 25 (SMTP for Mail Transfer)
2. Find the session and policy ID
Go to Security Fabric > Physical Topology. From the Metrics dropdown, select Sessions.
To find your session, search for your source IP address, destination IP address (if you have it), and port number. The
policy ID is listed after the destination information.
3. Use filters to find a session
If there are multiple pages of sessions, you can use a filter to hide the sessions you do not need. To filter the sessions in
the table, click Add Filter, and select an option from the list. You can filter the table by Destination IP, Source IP, or
Source Port.
CLI
The session table output in the CLI is very large. The CLI command supports filters to show only the data you need.
FortiOS 7.6.2 Administration Guide 4055
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.