Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

FortiGuard server settings

Your local FortiGate connects to remote FortiGuard servers to get updates to FortiGuard information, such as new viruses that may have been found or other new threats.

This section provides methods to display FortiGuard server information on your FortiGate, and how to use that information and update it to fix potential problems.

Displaying the server list

To get a list of FDS servers FortiGate uses to send web filtering requests:

get webfilter status

or

diagnose debug rating

Rating requests are only sent to the server at the top of the list in normal operation. Each server is probed for Round Trip Time (RTT) every two minutes. Rating may not be enabled on your FortiGate.

Optionally, you can add a refresh rate to the end of the command to determine how often the server list is refreshed.

Sample output:
Locale       : english
License      : Contract
Expiration   : Thu Oct  9 02:00:00 2011
-=- Server List (Mon Feb 18 12:55:48 2008) -=-
IP            Weight    RTT    Flags    TZ     Packets CurrLost TotalLost
a.b.c.d	0	1	DI	2	1926879	0	11176
10.1.101.1	10	329	 	1	10263	0	633
10.2.102.2	20	169	 	0	16105	0	80
10.3.103.3	20	182	 	0	6741	0	776
10.4.104.4	20	184	 	0	5249	0	987
10.5.105.5	25	181	 	0	12072	0	178
Output details

The server list includes the IP addresses of alternate servers if the first entry cannot be reached. In this example, the IP addresses are not public addresses.

The following flags in get webfilter status indicate the server status:

Flag

Description

D

The server was found through the DNS lookup of the hostname.

If the hostname returns more than one IP address, all of them are flagged with D and are used first for INIT requests before falling back to the other servers.

I

The server to which the last INIT request was sent

F

The server hasn't responded to requests and is considered to have failed

T

The server is currently being timed

S

Rating requests can be sent to the server.

The flag is set for a server only in two cases:

  • The server exists in the servers list received from the (Undefined variable: FortinetVariables.ProductName1) or any other INIT server.
  • The server list received from the (Undefined variable: FortinetVariables.ProductName1) is empty so the (Undefined variable: FortinetVariables.ProductName1) is the only server that the (Undefined variable: FortinetVariables.ProductName6) knows and it should be used as the rating server.

Sorting the server list

The server list is sorted first by weight. The server with the smallest RTT appears at the top of the list, regardless of weight. When a packet is lost (there has been no response in 2 seconds), it is re-sent to the next server in the list. Therefore, the top position in the list is selected based on RTT, while the other positions are based on weight.

Calculating weight

The weight for each server increases with failed packets and decreases with successful packets. To lower the possibility of using a remote server, the weight isn't allowed to dip below a base weight. The base weight is calculated as the difference in hours between the FortiGate and the server multiplied by 10. The farther away the server is, the higher its base weight is and the lower it appears in the list.

FortiGuard server settings

Your local FortiGate connects to remote FortiGuard servers to get updates to FortiGuard information, such as new viruses that may have been found or other new threats.

This section provides methods to display FortiGuard server information on your FortiGate, and how to use that information and update it to fix potential problems.

Displaying the server list

To get a list of FDS servers FortiGate uses to send web filtering requests:

get webfilter status

or

diagnose debug rating

Rating requests are only sent to the server at the top of the list in normal operation. Each server is probed for Round Trip Time (RTT) every two minutes. Rating may not be enabled on your FortiGate.

Optionally, you can add a refresh rate to the end of the command to determine how often the server list is refreshed.

Sample output:
Locale       : english
License      : Contract
Expiration   : Thu Oct  9 02:00:00 2011
-=- Server List (Mon Feb 18 12:55:48 2008) -=-
IP            Weight    RTT    Flags    TZ     Packets CurrLost TotalLost
a.b.c.d	0	1	DI	2	1926879	0	11176
10.1.101.1	10	329	 	1	10263	0	633
10.2.102.2	20	169	 	0	16105	0	80
10.3.103.3	20	182	 	0	6741	0	776
10.4.104.4	20	184	 	0	5249	0	987
10.5.105.5	25	181	 	0	12072	0	178
Output details

The server list includes the IP addresses of alternate servers if the first entry cannot be reached. In this example, the IP addresses are not public addresses.

The following flags in get webfilter status indicate the server status:

Flag

Description

D

The server was found through the DNS lookup of the hostname.

If the hostname returns more than one IP address, all of them are flagged with D and are used first for INIT requests before falling back to the other servers.

I

The server to which the last INIT request was sent

F

The server hasn't responded to requests and is considered to have failed

T

The server is currently being timed

S

Rating requests can be sent to the server.

The flag is set for a server only in two cases:

  • The server exists in the servers list received from the (Undefined variable: FortinetVariables.ProductName1) or any other INIT server.
  • The server list received from the (Undefined variable: FortinetVariables.ProductName1) is empty so the (Undefined variable: FortinetVariables.ProductName1) is the only server that the (Undefined variable: FortinetVariables.ProductName6) knows and it should be used as the rating server.

Sorting the server list

The server list is sorted first by weight. The server with the smallest RTT appears at the top of the list, regardless of weight. When a packet is lost (there has been no response in 2 seconds), it is re-sent to the next server in the list. Therefore, the top position in the list is selected based on RTT, while the other positions are based on weight.

Calculating weight

The weight for each server increases with failed packets and decreases with successful packets. To lower the possibility of using a remote server, the weight isn't allowed to dip below a base weight. The base weight is calculated as the difference in hours between the FortiGate and the server multiplied by 10. The farther away the server is, the higher its base weight is and the lower it appears in the list.