index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
4,055
|
Troubleshooting
To view session data in the CLI:
diagnose sys session list
An entry is placed in the session table for each traffic session passing through a security policy
To filter session data:
diagnose sys session filter <option>
The values for <option> include the following:
Value Definition
clear Clear session filter
dintf Destination interface
dport Destination port
dst Destination IP address
duration Duration of the session
expire Expire
negate Inverse filter
nport NAT'd source port
nsrc NAT'd source ip address
policy Policy ID
proto Protocol number
proto-state Protocol state
session-state1 Session state1
session-state2 Session state2
sintf Source interface
sport Source port
src Source IP address
vd Index of virtual domain, -1 matches all
Even though UDP is a sessionless protocol, FortiGate keeps track of the following states:
l When UDP reply does not have a value of 0
l When UDP reply has a value of 1
The following table displays firewall session states from the session table:
State Description
log Session is being logged
FortiOS 7.6.2 Administration Guide 4056
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,056
|
Troubleshooting
State Description
local Session is originated from or destined for local stack
ext Session is created by a firewall session helper
may_dirty Session is created by a policy
For example, the session for ftp control channel will have this state but ftp data
channel won't. This is also seen when NAT is enabled.
ndr Session will be checked by IPS signature
nds Session will be checked by IPS anomaly
br Session is being bridged (TP) mode
Examining the firewall session list
The firewall session list displays all open sessions in FortiGate. Examine the list for strange patterns, such as no
sessions apart from the internal network, or all sessions are only to one IP address.
When you examine the firewall session list in the CLI, you can use filters to reduce the output.
To examine the firewall session list in the CLI:
You can use a filter to limit the sessions displayed by source, destination address, port, or NAT'd address. To use more
than one filter, enter a separate line for each value.
The following example filters the session list based on a source address of 10.11.101.112:
FGT# diagnose sys session filter src 10.11.101.112
FGT# diagnose sys session list
The following example filters the session list based on a destination address of 172.20.120.222.
FGT# diagnose sys session filter dst 172.20.120.222
FGT# diagnose sys session list
To clear all sessions corresponding to a filter:
FGT# diagnose sys session filter dst 172.20.120.222
FGT# diagnose sys session clear
Checking source NAT information
Checking source NAT is important when you are troubleshooting from the remote end of the connection outside the
firewall.
To check the source NAT information in the CLI:
When you display the session list in the CLI, you can match the NAT'd source address (nsrc) and port (nport). This is
useful when multiple internal IP addresses are NAT'd to a common external-facing source IP address.
FGT# diagnose sys session filter nsrc 172.20.120.122
FGT# diagnose sys session filter nport 8888
FGT# diagnose sys session list
FortiOS 7.6.2 Administration Guide 4057
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,057
|
Troubleshooting
Finding object dependencies
You may be prevented from deleting a configuration object when other configuration objects depend on it. You can use
the GUI or CLI to identify objects which depend on, or make reference to the configuration you are trying to delete.
Additionally, if you have a virtual interface with dependent objects, you will need to find and remove those dependencies
before deleting the interface.
To remove interface object dependencies in the GUI:
1. Go to Network > Interfaces. The Ref. column displays the number of objects that reference this interface.
2. Select the number in the Ref . column for the interface. A window listing the dependencies appears.
3. Use these detailed entries to locate and remove object references to this interface. The trash can icon is enabled
after all the object dependencies are removed.
4. Remove the interface by selecting the check box for the interface, and select Delete.
To find object dependencies in the CLI:
When running multiple VDOMs, use the following command in the global configuration only.
diagnose sys cmdb refcnt show <path.object.mkey>
The command searches for the named object in both the most recently used global and VDOM configurations.
Examples
To verify which objects a security policy with an ID of 1 refers to:
diagnose sys cmdb refcnt show firewall.policy.policyid 1
To check what is referred to by interface port1:
diagnose sys cmdb refcnt show system.interface.name port1
To show all dependencies for an interface:
diagnose sys cmdb refcnt show system.interface.name <interface name>
Sample output:
In this example , the interface has dependent objects, including four address objects, one VIP, and three security
policies.
entry used by table firewall.address:name '10.98.23.23_host’
entry used by table firewall.address:name 'NAS'
entry used by table firewall.address:name 'all'
entry used by table firewall.address:name 'fortinet.com'
entry used by table firewall.vip:name 'TORRENT_10.0.0.70:6883'
entry used by table firewall.policy:policyid '21'
entry used by table firewall.policy:policyid '14'
entry used by table firewall.policy:policyid '19'
FortiOS 7.6.2 Administration Guide 4058
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,058
|
Troubleshooting
Diagnosing NPU-based interfaces
You can use the commands in this section to diagnose sessions offloaded to network processors (also called NPUs or
NPs) in your FortiGate. Most FortiGates contain one or more of the following NPUs:
l NP7 or NP7Lite
l NP6, NP6XLite or NP6Lite
You can find your FortiGate unit in the Hardware Acceleration Guide to determine its NPU configuration.
Normally you can use the diagnose debug flow command to view sessions. However, this command only displays
sessions processed by the CPU (also called software sessions). To view sessions offloaded to NPUs (also called
hardware sessions), you must use the commands and techniques described in this section.
Alternatively, you can disable NPU offloading and then use the diagnose debug flow
command. You should only disable the NPU functionality for troubleshooting purposes.
Diagnosing NP7 or NP7Lite sessions
Use the following command to list the NP7 processors in your FortiGate unit and the interfaces that they connect to:
diagnose npu np7 port-list
Use the following command to list the NP7Lite processors in your FortiGate unit and the interfaces that they connect to:
diagnose npu np7lite port-list
To use the NP7 packet sniffer
On FortiGates with NP7 and NP7Lite processors, you can use the following command to view sessions:
diagnose npu sniffer {start | stop | filter}
Here is a basic example to sniff offloaded TCP packets received by the port23 interface. In the following example:
l The first line clears the filter.
l The second line sets the sniffer to look for packets on port23.
l The third line looks for packets exiting the interface.
l The fourth line looks for TCP packets.
l The fifth line starts the sniffer.
l The sixth line starts displaying the packets on the CLI.
diagnose npu sniffer filter
diagnose npu sniffer filter intf port23
diagnose npu sniffer filter dir 1
diagnose npu sniffer filter protocol 6
diagnose npu sniffer start
diagnose sniffer packet npudbg
For more information, see NP7 packet sniffer or Tracing packet flow on FortiGates with NP7 processors.
See this Fortinet Community article for an NP7 packet sniffer example: Troubleshooting Tip: Collecting NP7 packet
capture without disabling offload.
FortiOS 7.6.2 Administration Guide 4059
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,059
|
Troubleshooting
Diagnosing NP6, NP6XLite or NP6Lite sessions
Use either of the following commands to list the NP6 processors in your FortiGate unit and the interfaces that they
connect to:
get hardware npu np6 port-list
diagnose npu np6 port-list
Use the following command to list the NP6XLite processors in your FortiGate unit:
get hardware npu np6xlite port-list
Use either of the following commands to list the NP6Lite processors in your FortiGate unit:
get hardware npu np6lite port-list
diagnose npu np6lite port-list
The output of all of these commands includes the device ID or dev_id of each NP processor. Only FortiGates with NP6
processors have multiple dev_ids. On FortiGates with one NP6, NP6Xlite, or NP6Lite processor, dev_id is always 0.
To diagnose NP6, NP6XLite, or NP6 sessions, disable NPU offloading.
diagnose npu <processor> fastpath disable <dev_id>
Then use the diagnose debug flow command to view sessions.
Identifying the XAUI link used for a specific traffic stream
The diagnose npu np6 xaui-hash command takes a 6-tuple input of the traffic stream to identify the NP6 XAUI link
that the traffic passes through.
This command is only available on the 38xxD, 39xxD, 34xxE, 36xxE, and 5001E series devices.
Syntax
diagnose npu np6 xaui-hash <interface> <proto> <src_ip> <dst_ip> <src_port> <dst_port>
Variable Description
<interface> The network interface that the packets are coming from.
<proto> The proto number, 6 for TCP or 17 for UDP.
<src_ip> The source IP address.
<dst_ip> The destination IP address.
<src_port> The source port.
<dst_port> The destination port.
Examples
# diagnose npu np6 xaui-hash port1 6 1.1.1.1 2.2.2.1 4567 80
NP6_ID: 0, XAUI_LINK: 2
# diagnose npu np6 xaui-hash port1 6 1.1.1.1 2.2.2.1 4567 200
NP6_ID: 6, XAUI_LINK: 2
FortiOS 7.6.2 Administration Guide 4060
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,060
|
Troubleshooting
# diagnose npu np6 xaui-hash port1 6 1.1.1.1 2.2.2.1 4567 20
NP6_ID: 1, XAUI_LINK: 2
# diagnose npu np6 xaui-hash port1 6 1.1.1.1 2.2.2.1 4567 23
NP6_ID: 1, XAUI_LINK: 1
The NP6_ID is the NP index of the model that is being used. It can be found with the diagnose npu np6 port-list
command.
Running the TAC report
The Technical Assistance Center (TAC) report runs an exhaustive series of diagnostic commands. Some of the
commands are only needed if you are using features, such as HA, VPN tunnels, or a modem. Fortinet support my ask
you to use the report output to provide information about the current state of your FortiGate.
Due the amount of output generated, the report may take a few minutes to run. If you are logging CLI output to a file, you
can run this command to familiarize yourself with the diagnostic commands.
To run the TAC report in the CLI:
execute tac report
Using the process monitor
The Process Monitor displays running processes with their CPU and memory usage levels. Administrators can sort,
filter, and terminate processes within the Process Monitor pane.
To access the process monitor:
1. Go to Dashboard > Status:
l Left-click in the CPU or Memory widget and select Process Monitor.
l Click the user name in the upper right-hand corner of the screen, then go to System > Process Monitor.
The Process Monitor appears, which includes a line graph, donut chart, and process list.
FortiOS 7.6.2 Administration Guide 4061
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,061
|
Troubleshooting
2. Click the + beside the search bar to view which columns can be filtered.
To kill a process within the process monitor:
1. Select a process.
2. Click the Kill Process dropdown.
3. Select one of the following options:
l Kill: the standard kill option that produces one line in the crash log (diagnose debug crashlog read).
l Force Kill: the equivalent to diagnose sys kill 9 <pid>. This can be viewed in the crash log.
FortiOS 7.6.2 Administration Guide 4062
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,062
|
Troubleshooting
l Kill & Trace: the equivalent to diagnose sys kill 11 <pid>. This generates a longer crash log and
backtrace. A crash log is displayed afterwards.
Computing file hashes
The following command computes the SHA256 file hashes for all of the files in a directory or directories:
# diagnose sys filesystem hash <paths> -d [depth]
<paths> Add up to 25 paths to show only the hash for the files at those paths.
-d [depth] Specify the maximum depth of the traversal.
This command can be used for troubleshooting and debugging the system. The file hashes of system files can be
compared against known good system files to help identify any compromises made on the system files.
To hash all filesystems:
# diagnose sys filesystem hash
Hash contents: /bin
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/syslogd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/acd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/httpsnifferd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/merged_daemons
-> /bin/init
...
/bin/init
6e2e07782dc17b8693268989f8ba1a8858a73d5291fb521e315011731cefe412 /bin/setpci
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/wad_csvc_cs ->
FortiOS 7.6.2 Administration Guide 4063
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,063
|
Troubleshooting
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/fds_notify ->
/bin/init
...
Hash contents: /lib
3dae8f9c15da465ffda24cebc1328725e98ee7c94a20e54af6ead7eaada45d9d /lib/libusb-1.0.so.0
e50c6b5cad36b200d4903e4d7d5e5eac1f5c618d27fd6961011e28a892ed8866
/lib/libk5crypto.so.3
b021ad6fb16ce1e881ca586036687c1b2ae9555805817ef394284528d9e71612 /lib/libgomp.so.1
...
To hash specific filesystem, add the name of the filesystem:
# diagnose sys filesystem hash /sbin
Hash contents: /sbin
c1f81e67a53bcf70720748fe31c2380e95b4c3dfdb96957fd116fcf702bd797b /sbin/init
Filesystem hash complete. Hashed 1 files.
To hash multiple filesystems, add the names of the filesystems:
Up to 25 file systems can be added.
# diagnose sys filesystem hash /sbin /bin
Hash contents: /sbin
c1f81e67a53bcf70720748fe31c2380e95b4c3dfdb96957fd116fcf702bd797b /sbin/init
Hash contents: /bin
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/syslogd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/acd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/httpsnifferd ->
/bin/init
5132b40a66fd4cf062adb42e2af43cb9aea0672cf885f12978e8de2f3137834b /bin/merged_daemons
-> /bin/init
To specify the maximum depth of the traversal:
# diagnose sys filesystem hash /data2 -d 1
Hash contents: /data2
a0166e804dc3d9a68fcc8015cb2d214ec40f0609e8e2aecc0eb2e5bdffc45524 /data2/new_alert_msg
7270b43899e0f72c7b9c94e66d64fd0e19881d91f74bd5ae6556eba045222e84 /data2/vir
8092e73c6a68f3cb02c86155bf3e55b2c1ab793eafcdd538beb5aa998d4b6b82 /data2/vir.x
2e29084d86f3925a0fb6bf96c4d83a6d3025fdd9cf8059ebcfc307153b9fd63b /data2/virext
48ac27b0b5b10b3b0f3ab2f847406d524709c32117f6b721bb10448742bd5eb6 /data2/virext.x
2e29084d86f3925a0fb6bf96c4d83a6d3025fdd9cf8059ebcfc307153b9fd63b /data2/virexdb
601316a029b28757c44515e37f48de2985d9fe8ef5c318e5f67e51369cba09f0 /data2/virexdb.x
7270b43899e0f72c7b9c94e66d64fd0e19881d91f74bd5ae6556eba045222e84 /data2/virfldb
896b71b3d9b209d339213f9d4af4088d3addd891cd292e93b5168eddb36b599a /data2/virfldb.x
0af98283f9bcb7dff4974197f1c7f1b1013ec741c8cc6c1425119fb88f9a351b /data2/ffdb_map_
default_res
627d2aed79770f698dbfc2bc0889f8285d1ea596c2dace8e6d3e7f00e040d990 /data2/madb.dat
96a296d224f285c67bee93c30f8a309157f0daa35dc5b87e410b78630a09cfc7 /data2/signature_
result
ceab5e70a5368aa834842973241e1ae6ca49ff5c88afb6199e5d87e1749caeb1 /data2/revision_
info_db
7eb70257593da06f682a3ddda54a9d260d4fc514f645237f5ca74b08f8da61a6 /data2/alci.dat
FortiOS 7.6.2 Administration Guide 4064
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,064
|
Troubleshooting
5840dfcf66d296be775e4e4d08bcdd014d1c91bd45e070587907d9eedab53e3e /data2/uwdb
dc64fb8a291c7fc6d655474d00e2c42e7bb2b466de4489d33301f3ba82f64794 /data2/ffdb_
pkg.tgz.x
c66a6ccc586ce29d38854a6afee49c0464fdc0064b59c4a104544325fd1ff03f /data2/afdb
Filesystem hash complete. Hashed 17 files.
# diagnose sys filesystem hash /data2 -d 2
Hash contents: /data2
a0166e804dc3d9a68fcc8015cb2d214ec40f0609e8e2aecc0eb2e5bdffc45524 /data2/new_alert_msg
7270b43899e0f72c7b9c94e66d64fd0e19881d91f74bd5ae6556eba045222e84 /data2/vir
8092e73c6a68f3cb02c86155bf3e55b2c1ab793eafcdd538beb5aa998d4b6b82 /data2/vir.x
2e29084d86f3925a0fb6bf96c4d83a6d3025fdd9cf8059ebcfc307153b9fd63b /data2/virext
48ac27b0b5b10b3b0f3ab2f847406d524709c32117f6b721bb10448742bd5eb6 /data2/virext.x
2e29084d86f3925a0fb6bf96c4d83a6d3025fdd9cf8059ebcfc307153b9fd63b /data2/virexdb
601316a029b28757c44515e37f48de2985d9fe8ef5c318e5f67e51369cba09f0 /data2/virexdb.x
7270b43899e0f72c7b9c94e66d64fd0e19881d91f74bd5ae6556eba045222e84 /data2/virfldb
896b71b3d9b209d339213f9d4af4088d3addd891cd292e93b5168eddb36b599a /data2/virfldb.x
0af98283f9bcb7dff4974197f1c7f1b1013ec741c8cc6c1425119fb88f9a351b /data2/ffdb_map_
default_res
627d2aed79770f698dbfc2bc0889f8285d1ea596c2dace8e6d3e7f00e040d990 /data2/madb.dat
96a296d224f285c67bee93c30f8a309157f0daa35dc5b87e410b78630a09cfc7 /data2/signature_
result
5ce22b4398f63fea2b47b7c1f00813a29851714993aee1269d3e95cbf43f4252 /data2/geodb/geoip.1
81ad258e278019dbd34fd07ba33966a6ff04e3fa352dddfe9ff362ac26d3cc88
/data2/config/cfg0000000001
e0067eb3d67b21cf39f27cb3558c5fbdafbc2c17c2afc29ab776b08e9c777a13
/data2/config/cfg0000000002
e77ad7c6b5d620d49f0f11933baf633335621de848a4229c3724152fff9aa4fa
/data2/config/cfg0000000003
228a7ed52779ba23f41a2423bfa7dbe858f24433f1702161f27678df4894f358
/data2/config/cfg0000000004
fe9e7afe7a6ccb739cb45c8d8f3b985377242ab61cc8199fa33dd475db49420f
/data2/config/cfg0000000005
b632b77348a54a2479453ab0f2c9f8e3c1e910badc8fbfb3fb841acf8eb4e35e
/data2/config/cfg0000000006
baeccb81d75f1f31503d42d3526f8831044144051f562486a89f1c5e4dd46d9c
/data2/config/cfg0000000007
ceab5e70a5368aa834842973241e1ae6ca49ff5c88afb6199e5d87e1749caeb1 /data2/revision_
info_db
7eb70257593da06f682a3ddda54a9d260d4fc514f645237f5ca74b08f8da61a6 /data2/alci.dat
5840dfcf66d296be775e4e4d08bcdd014d1c91bd45e070587907d9eedab53e3e /data2/uwdb
dc64fb8a291c7fc6d655474d00e2c42e7bb2b466de4489d33301f3ba82f64794 /data2/ffdb_
pkg.tgz.x
c66a6ccc586ce29d38854a6afee49c0464fdc0064b59c4a104544325fd1ff03f /data2/afdb
Filesystem hash complete. Hashed 25 files.
An error message is shown if an incorrect value is entered:
# diagnose sys filesystem hash /test-path
ERROR: Could not fetch info for path /test-path (No such file or directory)
Filesystem hash complete. Hashed 0 files.
# diagnose sys filesystem hash /bin -d 0
ERROR: depth must be greater than zero. (0)
Command fail. Return code -651
FortiOS 7.6.2 Administration Guide 4065
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,065
|
Troubleshooting
Other commands
You may be asked to provide the following information when you contact Fortinet support.
l ARP table on page 4066
l IP address on page 4068
ARP table
The ARP table is used to determine the destination MAC addresses of the network nodes, as well as the VLANs and
ports from where the nodes are reached.
To view the ARP table:
# get system arp
Address Age(min) Hardware Addr Interface
10.10.1.3 1 50:b7:c3:75:ea:dd internal7
192.168.0.190 0 28:f1:0e:03:2a:97 wan1
192.168.0.97 0 f4:f2:6d:37:b0:99 wan1
To view the ARP cache in the system:
# diagnose ip arp list
index=14 ifname=internal7 10.10.1.3 50:b7:c3:75:ea:dd state=00000004 use=2494 confirm=1995
update=374 ref=3
index=5 ifname=wan1 192.168.0.190 28:f1:0e:03:2a:97 state=00000002 use=88 confirm=86
update=977639 ref=2
index=22 ifname=internal 192.168.1.111 00:0c:29:c6:79:3d state=00000004 use=3724
confirm=9724 update=3724 ref=0
index=5 ifname=wan1 224.0.1.140 01:00:5e:00:01:8c state=00000040 use=924202 confirm=930202
update=924202 ref=1
index=5 ifname=wan1 192.168.0.97 f4:f2:6d:37:b0:99 state=00000002 use=78 confirm=486
update=614 ref=26
index=14 ifname=internal7 10.10.1.11 state=00000020 use=172 confirm=1037790 update=78 ref=2
ARP request and cache
The FortiGate must make an ARP request when it tries to reach a new destination. The base ARP reachable value
determines how often an ARP request it sent; the default is 30 seconds. The actual ARP reachable time is a random
number between half and three halves of the base reachable time, or 15 to 45 seconds. The random number is updated
every five minutes.
ARP entries in the ARP cache are updated based on the state of the ARP entry and the objects that are using it, as
highlighted in the following output sample:
index=5 ifname=wan1 224.0.1.140 01:00:5e:00:01:8c state=00000040 use=924202
confirm=930202 update=924202 ref=1
There are multiple possible states for an ARP entry, and the state-transition mechanism can be complex. Common
states include the following:
FortiOS 7.6.2 Administration Guide 4066
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,066
|
Troubleshooting
State Meaning Description
000000002 or 0x02 REACHABLE An ARP response was received
000000004 or 0x04 STALE No ARP response within the expected time
000000008 or 0x08 DELAY A transition state between STALE and REACHABLE
before Probes are sent out
000000020 or 0x20 FAILED Did not manage to resolve within the maximum
configured number of probes
000000040 or 0x40 NOARP Device does not support ARP, e.g. IPsec interface
000000080 or 0x80 PERMANENT A statically defined ARP entry
An entry that is in the STALE (0x04) or FAILED (0x20) states with no references to it (ref=0) can be deleted. Many factors
affect the state-transmit mechanism and if an entry is used by other subsystems. For example, ARP creation, ARP
request/reply, neighbor lookup, routing, and others can cause an ARP entry to be in use or referenced.
The garbage collection mechanism runs every 30 seconds, and checks and removes stale and unreferenced entries if
they have been stale for longer than 60 seconds. Garbage collection will also be triggered when the number of ARP
entries exceeds the configured threshold. If the threshold is exceeded, no entries can be added to the ARP table.
To set the maximum number of ARP entries threshold:
config system global
set arp-max-entry <integer>
end
arp-max-entry <integer> The maximum number of dynamically learned MAC addresses that can be added
to the ARP table (131072 to 2147483647, default = 131072).
To set the ARP reachable time on an interface:
config system interface
edit port1
set reachable-time <integer>
next
end
reachable-time <integer> The reachable time (30000 to 3600000, default = 30000).
To clear all of the entries in the ARP table:
execute clear system arp table
To delete a single ARP entry from the ARP table:
diagnose ip arp delete <interface name> <IP address>
FortiOS 7.6.2 Administration Guide 4067
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,067
|
Troubleshooting
To add static ARP entries:
config system arp-table
edit 1
set interface "internal"
set ip 192.168.50.8
set mac bc:14:01:e9:77:02
next
end
To view a summary of the ARP table:
# diagnose sys device list root
list virtual firewall root info:
ip4 route_cache: table_size=65536 max_depth=2 used=31 total=34
arp: table_size=16 max_depth=2 used=5 total=6
proxy_arp: table_size=256 max_depth=0 used=0 total=0
arp6: table_size=32 max_depth=1 used=3 total=3
proxy_arp6: table_size=256 max_depth=0 used=0 total=0
local table version=00000000 main table version=0000002b
vf=root dev=root vrf=0
vf=root dev=ssl.root vrf=0
...
vf=root dev=internal5 vrf=0
ses=0/0 ses6=0/0 rt=0/0 rt6=0/0
IP address
You may want to verify the IP addresses assigned to the FortiGate interfaces are what you expect them to be.
To verify IP addresses:
diagnose ip address list
The output lists the:
l IP address and mask (if available)
l index of the interface (a type of ID number)
l devname (the interface name)
While physical interface names are set, virtual interface names can vary. A good way to use this command is to list all of
the virtual interface names. For vsys_ha and vsys_fgfm, the IP addresses are the local host, which are virtual
interfaces that are used internally.
Sample output:
# diagnose ip address list
IP=10.31.101.100->10.31.101.100/255.255.255.0 index=3 devname=internal
IP=172.20.120.122->172.20.120.122/255.255.255.0 index=5 devname=wan1
IP=127.0.0.1->127.0.0.1/255.0.0.0 index=8 devname=root
IP=127.0.0.1->127.0.0.1/255.0.0.0 index=11 devname=vsys_ha
IP=127.0.0.1->127.0.0.1/255.0.0.0 index=13 devname=vsys_fgfm
FortiOS 7.6.2 Administration Guide 4068
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,068
|
Troubleshooting
FortiGuard troubleshooting
The FortiGuard service provides updates to AntiVirus (AV), Antispam (AS), Intrusion Protection Services (IPS),
Webfiltering (WF), and more. The FortiGuard Distribution System (FDS) consists of a number of servers across the
world that provide updates to your FortiGate unit. Problems can occur with the connection to FDS and its configuration
on your local FortiGate unit.
Some of the more common troubleshooting methods are listed here, including:
l Verifying connectivity to FortiGuard on page 4069
l Troubleshooting process for FortiGuard updates on page 4070
l FortiGuard server settings on page 4070
Verifying connectivity to FortiGuard
You can verify FortiGuard connectivity in the GUI and CLI.
To verify FortiGuard connectivity in the GUI:
1. Got to Dashboard > Status.
2. Check the Licenses widget. When FortiGate is connected to FortiGuard, licensed services are in green icons.
To verify FortiGuard connectivity in the CLI:
execute ping service.fortiguard.net
execute ping update.fortiguard.net
Sample output:
FG100D# execute ping service.fortiguard.net
PING guard.fortinet.net (208.91.112.196): 56 data bytes
64 bytes from 208.91.112.196: icmp_seq=0 ttl=51 time=61.0 ms
64 bytes from 208.91.112.196: icmp_seq=1 ttl=51 time=60.0 ms
64 bytes from 208.91.112.196: icmp_seq=2 ttl=51 time=59.6 ms
64 bytes from 208.91.112.196: icmp_seq=3 ttl=51 time=58.9 ms
64 bytes from 208.91.112.196: icmp_seq=4 ttl=51 time=59.2 ms
--- guard.fortinet.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 58.9/59.7/61.0 ms
FG100D# execute ping update.fortiguard.net
PING fds1.fortinet.com (208.91.112.68): 56 data bytes
64 bytes from 208.91.112.68: icmp_seq=0 ttl=53 time=62.0 ms
64 bytes from 208.91.112.68: icmp_seq=1 ttl=53 time=61.8 ms
64 bytes from 208.91.112.68: icmp_seq=2 ttl=53 time=61.3 ms
64 bytes from 208.91.112.68: icmp_seq=3 ttl=53 time=61.9 ms
64 bytes from 208.91.112.68: icmp_seq=4 ttl=53 time=61.8 ms
FortiOS 7.6.2 Administration Guide 4069
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,069
|
Troubleshooting
Troubleshooting process for FortiGuard updates
The following process shows the logical steps you should take when troubleshooting problems with FortiGuard updates:
1. Does the device have a valid license that includes these services?
Each device requires a valid FortiGuard license to access updates for some or all of these services. You can verify
the status of the support contract for your devices at the Fortinet Support website.
2. If the device is part of a high availability (HA) cluster, do all members of the cluster have the same level of
support?
You can verify the status of the support contract for all of the devices in your HA cluster at the Fortinet Support
website.
3. Are services enabled on the device?
To see the FortiGuard information and status for a device in the GUI, go to System > FortiGuard.
Use this page to verify the status of each component, and enable each service.
4. Can the device communicate with FortiGuard servers?
Go to System > FortiGuard in the GUI, and try to update AntiVirus and IPS, or test the availability of Web Filtering
and AS default and alternate ports.
5. Is there proper routing to reach the FortiGuard servers?
Ensure there is a static or dynamic route that allows your FortiGate to reach the FortiGuard servers. Usually a
generic default route to the internet is enough, but you may need to verify this if your network is complex.
6. Are there issues with DNS?
An easy way to test this is to attempt a traceroute from behind the FortiGate to an external network using the Fully
Qualified Domain Name (FQDN) for a location. If the traceroute FQDN name doesn't resolve, you have general
DNS problems.
7. Is there anything upstream that might be blocking FortiGuard traffic, either on the network or ISP side?
Many firewalls block all ports, by default, and ISPs often block ports that are low. There may be a firewall between
the FortiGate and the FortiGuard servers that's blocking the traffic. By default, FortiGuard uses port 53. If that port is
blocked you need to either open a hole for it or change the port it is using.
8. Is there an issue with source ports?
It is possible that ports that FortiGate uses to contact FortiGuard are being changed before they reach FortiGuard or
on the return trip before they reach FortiGate. A possible solution for this is to use a fixed-port at NAT'd firewalls to
ensure the port remains the same. You can use packet sniffing to find more information about what's happening with
ports.
9. Are there security policies that include antivirus?
If none of the security policies include antivirus, the antivirus database will not be updated. If antivirus is included,
only the database type that's used will be updated.
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.
The default setting to reach FortiGuard is anycast. However, FortiGate can be configured to use unicast server. See
FortiGuard on page 3314 for more information.
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.
FortiOS 7.6.2 Administration Guide 4070
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,070
|
Troubleshooting
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
Service : Web-filter
Status : Enable
License : Contract
Service : Antispam
Status : Disable
Service : Virus Outbreak Prevention
Status : Disable
Num. of servers : 2
Protocol : https
Port : 443
Anycast : Disable
Default servers : Included
-=- Server List (Wed Nov 16 14:42:08 2022) -=-
IP Weight RTT Flags TZ FortiGuard-requests
Curr Lost Total Lost Updated Time
140.174.22.68 30 866 -5
13 0 0 Wed Nov 16 14:41:35 2022
12.34.97.18 30 878 DI -5
12 0 0 Wed Nov 16 14:41:35 2022
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.
FortiOS 7.6.2 Administration Guide 4071
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,071
|
Troubleshooting
Flag Description
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:
l The server exists in the servers list received from the FortiManager or any other INIT server.
l The server list received from the FortiManager is empty so the FortiManager is the only server
that the FortiGate knows and it should be used as the rating server.
Please note that the example output displays Anycast as Disable because the CLI commands above work with the
FortiGuard unicast server case and not with the FortiGuard anycast servers case.
Also, in the example output above, the server 12.34.97.18 was found through a DNS lookup (D flag) and was sent the
last INIT request (I flag).
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.
View open and in use ports
Traffic destined for the FortiGate itself, and not being passed through or dropped, is called local-in traffic. It can be from a
variety of services, such as HTTPS for administrative access, or BGP for inter-router communication.
Local-in traffic is controlled by local-in policies. To enable viewing local-in policies in the GUI, go to System > Feature
Visibility and enable Local In Policy.
The Policy & Objects > Local In Policy page shows a read-only list of the local policies, populated with default values,
and values that are automatically enabled when the related service is enabled, for example, enabling BGP opens TCP
port 179. For more information, see Local-in policy on page 1480.
To view ports that are being listened on, and active connections and the services or processes using
them:
# diagnose sys tcpsock | grep 0.0.0.0
0.0.0.0:10400->0.0.0.0:0->state=listen err=0 socktype=4 rma=0 wma=0 fma=0 tma=0 inode=10621
process=142/authd
...
FortiOS 7.6.2 Administration Guide 4072
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,072
|
Troubleshooting
0.0.0.0:53->0.0.0.0:0->state=listen err=0 socktype=1 rma=0 wma=0 fma=0 tma=0 inode=8067
process=177/dnsproxy
0.0.0.0:22->0.0.0.0:0->state=listen err=0 socktype=1 rma=0 wma=0 fma=0 tma=0 inode=13390
process=225/sshd
0.0.0.0:541->0.0.0.0:0->state=listen err=0 socktype=1 rma=0 wma=0 fma=0 tma=0 inode=13155
process=215/fgfmd
...
0.0.0.0:9980->0.0.0.0:0->state=listen err=0 socktype=1 rma=0 wma=0 fma=0 tma=0 inode=5063
process=129/httpsd
0.0.0.0:179->0.0.0.0:0->state=listen err=0 socktype=1 rma=0 wma=0 fma=0 tma=0 inode=10583
process=148/bgpd
...
For more information on incoming and outgoing ports, see the FortiOS Ports guide.
IPS and AV engine version
The IPS engine is an important module that processes traffic in policies configured with flow-based inspection, next
generation firewall policies, as well as any policies that have IPS and application control defined. Just like its counterpart,
the WAD daemon in proxy-based inspection, the IPS engine can invoke other daemons to perform additional processing
such as certificate inspection, authentication, and other functions.
For each FortiOS release, an IPS engine is built into the firmware. You can find information about the IPS engine in its
corresponding Release Notes.
When a FortiGate is configured for automatic FortiGuard updates and has policies configured to use the IPS engine, it
downloads new releases of the IPS engine that are available through the FortiGuard Distribution Network. The IPS
Engine package released to FortiGuard is unavailable for manual download.
The FortiGate supports manual upgrade/downgrade of the IPS engine in special cases, such as for troubleshooting or
resolving a temporary issue that Technical Support deems necessary. In these cases, Technical Support distributes the
IPS engine package.
Likewise, the AV engine is also built into the FortiOS firmware and available as an automatic update through FortiGuard.
You can find information about the AV engine in its corresponding Release Notes.
Finally, for compatibility information between IPS and AV engines with FortiOS, see IPS Engine and AV Engine Support
for FortiOS and FortiAPS
print tablesize
You can use the print tablesize command to view a list of the maximum values for your device. The four columns
of values provide the following information, respectively:
1. Maximum number of variables allowed for this object type
2. Maximum number of objects of this type allowed per virtual domain (VDOM)
3. System global limit for maximum number of objects of this type
4. Current total number of objects of this type existing in FortiOS
A value of 0 indicates that there is no maximum value limit.
FortiOS 7.6.2 Administration Guide 4073
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,073
|
Troubleshooting
To check the maximum number of variables that you can append to all log messages:
# print tablesize
...
log.setting:custom-log-fields: 5 0 0 0
...
This means that you can add up to five variables:
config log setting
set custom-log-fields <field_1> <field_2> <field_3> <field_4> <field_5>
end
To check the external resource table size limit for your device:
In this example, the device has a global limit of 512, a per-VDOM limit of 256, and there are currently no external
resources existing in FortiOS. the available memory on the device limits the total number of feeds.
# print tablesize
...
system.external-resource: 0 256 512 0
...
To check the current total number of objects of this type existing in FortiOS:
# print tablesize
system.vdom: 0 0 10 3
system.datasource: 0 0 0 3
system.timezone: 0 0 0 597
system.accprofile: 0 0 10 5
system.np6xlite: 0 256 512 1
system.vdom-link: 0 0 0 3
...
CLI troubleshooting cheat sheet
See CLI troubleshooting cheat sheet.
CLI error codes
CLI error codes are shown in the command line if the command execution fails. The message includes a summary,
followed by Command fail. Return code -X, where -X is the error code. For example:
# set test
Command parse error before ‘test’
Command fail. Return code -61
The following table lists common error codes and their descriptions.
FortiOS 7.6.2 Administration Guide 4074
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,074
|
Troubleshooting
Return Code Description
1 Generic CLI syntax error
-1 Invalid length of value.
-4 Maximum number of entries has been reached.
-5 A duplicate entry already exists.
-8 Invalid IP Address.
-37 Permission denied.
-56 Empty values are not allowed.
-61 Input not as expected.
-160 CFG_ER_GENERIC (common generic configuration error)
-553 Name conflicts with an interface, VDOM, switch-interface, zone, or interface
name used for hardware switch interfaces.
-651 Input value is invalid.
Additional resources
To learn more about FortiGate and FortiOS, and for information about technical issues, refer to the following resources.
Fortinet Document Library
Installation Guides, Administration Guides, Quick Start Guides, and other technical documents are available online at
the Fortinet Document Library.
Release notes
Issues that arise after the technical documentation has been published are often listed in the release notes. The release
notes are available in the Fortinet Document Library.
Fortinet Video Library
The Fortinet Video Library hosts a collection of videos that provide valuable information about Fortinet products.
Fortinet Community
The Fortinet Community provides a place to collaborate, share insights and experiences, and get answers to questions.
It incorporates the Fortinet Knowledge Base and technical discussion forums. You can access the Fortinet Community at
https://community.fortinet.com.
FortiOS 7.6.2 Administration Guide 4075
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,075
|
Troubleshooting
Knowledge Base
The Fortinet Knowledge Base provides access to a variety of articles, white papers, and other documentation that
provides technical insight into a range of Fortinet products. You can access the Knowledge Base at
https://community.fortinet.com/t5/Knowledge-Base/ct-p/knowledgebase.
Fortinet technical discussion forums
The online technical forum allows administrators to contribute to discussions about issues related to their Fortinet
products. Searching the forum can help an administrator identify if an issue has been experienced by another user. You
can access the support forum at https://community.fortinet.com/t5/Fortinet-Forum/bd-p/fortinet-discussion.
Fortinet Training Institute
The Fortinet Training Institute hosts a collection of tutorials and training materials that you can use to increase your
knowledge of Fortinet products. You can access these training resources at https://www.fortinet.com/training.html.
Fortinet Support
You defined your problem, researched a solution, put together a plan to find the solution, and executed that plan. At this
point, if the problem has not been solved, contact Fortinet Support for assistance.
FortiOS 7.6.2 Administration Guide 4076
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,076
|
www.fortinet.com
Copyright© 2025 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s Chief Legal Officer, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
0
|
FortiGate-5001E System Guide
FortiGate-5000 Series
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
1
|
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET VIDEO GUIDE
https://video.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com
FORTINET TRAINING & CERTIFICATION PROGRAM
https://www.fortinet.com/support-and-training/training.html
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://fortiguard.com/
END USER LICENSE AGREEMENT
https://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: techdoc@fortinet.com
April 26, 2021
FortiGate-5001E System Guide
01-700-389680-20210426
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
2
|
TABLE OF CONTENTS
Change log 5
FortiGate-5001E and FortiGate-5001E1 security system 6
Physical Description 7
Front panel components 8
LEDs 8
System LEDs 8
BASE and FABRIC network activity LEDs 9
QSFP+ network activity LEDs (port1 and port2) (40G or 4 x 10G) 9
SFP+ network activity LEDs (port3 and port4) (10G) 9
RJ45 management interface LEDs (MGMT1 and MGMT2) 10
Front panel connectors 10
NMI switch 11
Base backplane communication 11
Fabric backplane communication 11
Accelerated packet forwarding and policy enforcement (NP6 network processors) 11
Accelerated IPS, SSL VPN, and IPsec VPN (CP9 content processors) 12
Splitting the FortiGate-5001E front panel port1 and port2 interfaces 13
Hardware installation 14
Installing QSFP+ and SFP+ transceivers 14
To install QSFP+, SFP+ or SFP transceivers 14
Changing the FortiGate-5001E SW6 switch settings 15
Changing or verifying the SW6 switch setting 16
FortiGate-5001E mounting components 17
Inserting a FortiGate-5001E board into a chassis 18
Shutting down and Removing a FortiGate-5001E 21
Resetting a FortiGate-5001E 23
Troubleshooting 24
FortiGate-5001E does not startup 24
FortiGate-5001E status LED is flashing during system operation 24
Fabric backplane communication speed compatibility 25
FortiGate-5001E quick configuration guide 26
Registering your FortiGate-5001E 26
Planning the configuration 26
Choosing the configuration tool 27
Factory default settings 27
Basic GUI configuration 28
Basic CLI configuration 28
Upgrading FortiGate-5001E firmware 29
FortiGate-5001E fabric and base backplane communication 29
Cautions and Warnings 31
Environmental Specifications 31
Safety 32
FortiGate-5001E System Guide 3
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
3
|
Fortinet Technologies Inc.
Regulatory Notices 34
Federal Communication Commission (FCC) – USA 34
Industry Canada Equipment Standard for Digital Equipment (ICES) – Canada 34
European Conformity (CE) - EU 34
Voluntary Control Council for Interference (VCCI) – Japan 35
Product Safety Electrical Appliance & Material (PSE) – Japan 35
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan 35
China 35
FortiGate-5001E System Guide 4
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
4
|
Change log Fortinet Technologies Inc.
Change log
Date Change description
April 26, 2021 Added a note about FortiGate-5001E compatibility with in a with the FortiGate-5060
chassis to FortiGate-5001E and FortiGate-5001E1 security system on page 6.
FortiGate-5001E System Guide 5
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
5
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
FortiGate-5001E and FortiGate-5001E1 security system
The FortiGate-5001E security system is a high-performance Advanced Telecommunications Computing Architecture
(ATCA) compliant FortiGate security system that can be installed in any ATCA chassis that can provide sufficient power
and cooling. The FortiGate-5001E1 security system adds an internal 480 GByte SSD log disk. In all other ways the
FortiGate-5001E and the FortiGate-5001E1 are identical.
The FortiGate-5001E is compatible with Fortinet’s FortiGate-5144C chassis. See the FortiGate-5000 Compatibility
Guide for up-to-date information about FortiGate-5001E compatibility.
Up to six FortiGate-5001Es can also be installed in Fortinet's FortiGate-5060 chassis as
standalone FortiGates. Fabric backplane switching is not supported. See the FortiGate-5060
Chassis Guide for details.
The FortiGate-5001E security system contains two front panel 40GigE QSFP+ fabric channel interfaces, two front panel
10GigE SFP+ fabric channel interfaces, two base backplane 1Gbps base channel interfaces, and two fabric backplane
40Gbps interfaces. The front panel SFP+ interfaces can also operate as Gigabit Ethernet interfaces using SFP
transceivers. Use the front panel interfaces for connections to your networks and the backplane interfaces for
communication across the ATCA chassis backplane. The FortiGate-5001E also includes two front panel
10/100/1000BASE-T out of band management Ethernet interfaces, one RJ45 front panel serial console port, and one
front panel USB port.
FortiGate-5001E front panel
MGMT 1 and MGMT 2
10/100/1000BASE-T Copper
Management Interfaces
3 and 4
10 GigE
SFP+ Fabric Channel
Network Interfaces
Base and Fabric
network activity
LEDs
RJ-45
Console
Extraction
Lever
Retention
Screw
USB
Extraction
Lever
Retention
Screw
IPM
LED
(board
position)
OOS
LED
STA
LED
PWR
LED
ACC
LED
Factory Use
NMI Switch
1 and 2
40 GigE Fabric
Channel QSFP+
Network Interfaces
The FortiGate-5001E front panel 40GigE, 10GigE interfaces and fabric backplane interfaces also provide NP6-
accelerated network processing for eligible traffic passing through these interfaces. All data traffic can also be
accelerated by CP9 processors.
FortiGate-5001E System Guide 6
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
6
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
You can also configure two or more FortiGate-5001Es to create a high availability (HA) cluster using the base or fabric
backplane interfaces for HA heartbeat communication through the chassis backplane, leaving front panel interfaces
available for network connections.
In most cases the base backplane interfaces are used for HA heartbeat communication and
the fabric backplane interfaces are used for data communication.
The FortiGate-5001E also supports high-end FortiGate features including 802.1Q VLANs, multiple virtual domains,
802.3ad aggregate interfaces, and FortiOS Carrier.
The FortiGate-5001E includes the following features:
l Two front panel 40GigE QSFP+ fabric channel (port1 and port2) accelerated by NP6 network processors. Using
40GBASE-SR10 multimode QSFP+ transceivers, port1 and port2 can also be split into four 10GBASE-SR
interfaces using the config system global set split-port command.
l Two front panel 10GigE SFP+ fabric channel interfaces (port3 and port4) also accelerated by NP6 network
processors. These interfaces can also be configured to operate as Gigabit Ethernet interfaces using SFP
transceivers.
l Two front panel 10/100/10000BASE-T out of band management Ethernet interfaces (mgmt1 and mgmt2).
l Two base backplane 1Gbps interfaces (base1 and base2) for HA heartbeat communications across the FortiGate5000 chassis base backplane.
l Two fabric backplane 40Gbps interfaces (fabric1 and fabric2) for data communications across the FortiGate-5000
chassis fabric backplane.
l Two NP6 network processors that accelerate traffic on the interfaces port1 - port4, fabirc1, and fabric2.
l Four CP9 content processors that accelerate IPS, DLP, SSL VPN, key exchange, and IPsec VPN.
l The FortiGate-5001E1 includes a 480 GB SSD for storing log messages, DLP archives, historic reports, IPS packet
archiving, file quarantine, WAN Optimization byte caching and web caching.
l One RJ-45 RS-232 serial console connection.
l 1 USB connector.
l NMI switch for troubleshooting as recommended by Fortinet Support.
l Mounting hardware.
l LED status indicators.
Physical Description
Dimensions 1.2 x 11.34 x 14 in. (3.1 x 28.8 x 35.1 cm) (Height x Width x Depth)
Weight 8.2 lb. (3.7 kg)
Operating Temperature 23 to 131°F (-5 to 55°C)
Storage Temperature -40 to 158°F (-40 to 70°C)
Relative Humidity 5 to 90% (Non-condensing)
Power consumption
Maximum
278 W
FortiGate-5001E System Guide 7
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
7
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
Average Power
Consumption
250 W
Max Current 5.9 A
Heat Dissipation 948.6 BTU/h
Front panel components
From the FortiGate-5001E front panel you can view the status of the front panel LEDs to verify that the board is
functioning normally. You also connect the FortiGate-5001E to your 40-gigabit network using the front panel QSFP+
connectors and to your 10-gigabit network using the front panel SFP+ or SFP connectors. The front panel also includes
two Ethernet management interfaces, an RJ-45 console port for connecting to the FortiOS CLI and a USB port. The USB
port can be used with any USB key for backing up and restoring configuration files.
LEDs
Ports 1 and 2 can operate in 40-gigabit mode or 4 x 10-gigabit mode. The LEDs function differently in each mode.
System LEDs
LED State Description
OOS (Out of
Service)
Off Normal operation.
Red A fault condition exists and the FortiGate-5001E is out of service
(OOS). This LED may also flash very briefly during normal startup.
PWR
(Power)
Off The main power is off. The standby power for IPMC circuits maybe
powered on in this state.
Green The FortiGate-5001E is powered on.
STA
(Status)
Off The FortiGate-5001E is operating normally.
Flashing Green The FortiGate-5001E is starting up. If this LED is flashing at any time
other than system startup, a fault condition may exist.
ACC (Disk
activity)
Off or Flashing
green
The ACC LED flashes green when the FortiGate-5001E accesses
the flash disk. The flash disk stores the current firmware build and
configuration files. The system accesses the flash disk when starting
up, during a firmware upgrade, or when an administrator is using the
CLI or GUI to change the FortiGate-5001E configuration. Under
normal operating conditions this LED flashes occasionally, but is
mostly off. Also flashes green when the FortiGate-5001E1 reads or
writes the 480 GB SSD.
FortiGate-5001E System Guide 8
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
8
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
LED State Description
IPM (Hot
Swap)
Off Normal Operation. The FortiGate-5001E is in contact with the
chassis backplane.
Flashing Blue The FortiGate-5001E is changing from hot swap to running mode or
from running mode to hot swap. This happens when the FortiGate5001E is starting up or shutting down.
Blue The FortiGate-5001E is ready to be hot-swapped (removed from the
chassis). If the IPM light is blue and no other LEDs are lit the
FortiGate-5001E has lost power.
BASE and FABRIC network activity LEDs
LED State Description
BASE (left
base1, right
base2)
Green Base backplane interfaces are connected at 1 Gbps.
Flashing Green Network activity.
Off No link.
FABRIC
(left fabric1,
right
fabric2)
Green Fabric backplane interface is connected at 40 Gbps.
Flashing Green Network activity.
Off No link.
QSFP+ network activity LEDs (port1 and port2) (40G or 4 x 10G)
Left LED Right LED Description
Green Off Connected at 40Gbps.
Flashing
Green
Amber Connected at 10Gbps.
Flashing
Green
Flashing Amber Connected at 10 Gbps (less than 4 channels).
Off Off No link established.
SFP+ network activity LEDs (port3 and port4) (10G)
LED State Description
Link/ACT Green SFP+ interface connected at 10Gbps.
Flashing Green Network activity.
Off No link.
FortiGate-5001E System Guide 9
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
9
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
RJ45 management interface LEDs (MGMT1 and MGMT2)
LED State Description
Link/ACT
(left)
Green Link up.
Flashing Green Network activity.
Off No link.
Speed
(right)
Green Management interface connected at 1 Gbps.
Amber Management interface connected at 100 Mbps.
Off No link, or management interface connected at 10 Mbps.
Front panel connectors
Connector Type Speed Protocol Description
CONSOLE RJ-45 9600 bps 8/N/1 RS-232 serial Serial connection to the
command line
interface.
1 and 2 QSFP+
(40
gigabit)
SFP+ (10
gigabit)
40-gigabit full
4x10-gigabit full
Ethernet 40-gigabit QSFP+
connection to 40GigE
networks or 4x10GigE
SFP+ connection to
10GigE networks.
Quad small form-factor
pluggable transceiver.
3 and 4 SFP+ (10
gigabit)
SFP (1
gigabit)
10-gigabit full
1-gigabit auto
1-gigabit full
Ethernet 10GigE SFP+
connection to 10GigE
networks or 1GigE SFP
connection to 1GigE
networks. Small formfactor pluggable
transceiver.
MGMT1 and
MGMT2
RJ-45 10/100/1000
Base-T
Ethernet Copper 1GigE
connection to
10/100/1000Base-T
copper networks for
management or system
administration.
USB USB USB key for firmware
updates and
configuration backup.
FortiGate-5001E System Guide 10
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
10
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
NMI switch
When working with Fortinet Support to troubleshoot problems with the FortiGate-5001E you can use the front panel nonmaskable interrupt (NMI) switch to assist with troubleshooting. Pressing this switch causes the software to dump
registers/backtraces to the console. After the data is dumped the FortiGate-5001E reboots. While rebooting, traffic is
temporarily blocked. The FortiGate-5001E should restart normally and traffic can resume once its up and running.
Base backplane communication
The FortiGate-5001E base backplane 1-gigabit interfaces (base1 and base2) are typically used for HA heartbeat or
other management base backplane communication. You can also configure FortiGate-5001Es to use the base
backplane interfaces for data communication. To support base backplane communications your FortiGate-series
chassis must include one or more FortiSwitch or FortiController or other 1-gigabit base backplane switches installed in
the chassis in hub/switch slots 1 and 2.
See the FortiGate-5000 Compatibility Guide for up-to-date information about FortiGate-5000 components that are
compatible with the FortiGate-5001E.
Fabric backplane communication
The FortiGate-5001E fabric backplane interfaces (fabric1 and fabric2) are typically used for fabric backplane data
communication. These interfaces can operate as 40-gigabit or 10-gigabit interfaces
To support 40-gigabit fabric backplane communications your FortiGate-5000 series chassis must include one or more
FortiControllers or other 40-gigabit fabric backplane switches installed in the chassis in fabric slots 1 and 2.
To support 10-gigabit fabric backplane communications your FortiGate-5000 series chassis must include one or more
FortiSwitches or FortiControllers or other 10-gigabit fabric backplane switches installed in the chassis in hub/switch slots
1 and 2.
See the FortiGate-5000 Compatibility Guide for up-to-date information about FortiGate-5000 components that are
compatible with the FortiGate-5001E.
Accelerated packet forwarding and policy enforcement (NP6
network processors)
The FortiGate-5001E includes two NP6 processors and an integrated switch fabric (ISF) that provides fastpath
acceleration by offloading communication sessions from the FortiGate CPU. All traffic from the front panel and
backplane interfaces can be accelerated. The result is enhanced network performance provided by the NP6 processor
plus the network processing load is removed from the CPU. The NP6 processor can also handle some CPU intensive
FortiGate-5001E System Guide 11
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
11
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
tasks, like IPsec VPN encryption/decryption. Because of the integrated switch fabric, all sessions are fast-pathed and
accelerated.
NP6 NP6
Integrated Switch Fabric
CPU
CP9
CP9 CP9
CP9
System Bus
fabric1
5x XAUI
4x XAUI 4x XAUI
fabric2
5x XAUI
port1
XLAUI
port2
XLAUI
port4
XLAUI
port3
XFI
base1
SGMII
base2
SGMII
Accelerated IPS, SSL VPN, and IPsec VPN (CP9 content processors)
The FortiGate-5001E includes four CP9 processors that provide the following performance enhancements:
l Flow-based inspection (IPS, application control etc.) pattern matching acceleration with over 10Gbps throughput
l IPS pre-scan
l IPS signature correlation
l Full match processors
l High performance VPN bulk data engine
l IPsec and SSL/TLS protocol processor
l DES/3DES/AES128/192/256 in accordance with FIPS46-3/FIPS81/FIPS197
l MD5/SHA-1/SHA256/384/512-96/128/192/256 with RFC1321 and FIPS180
l HMAC in accordance with RFC2104/2403/2404 and FIPS198
l ESN mode
l GCM support for NSA "Suite B" (RFC6379/RFC6460) including GCM-128/256; GMAC-128/256
l Key Exchange Processor that supports high performance IKE and RSA computation
FortiGate-5001E System Guide 12
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
12
|
FortiGate-5001E and FortiGate-5001E1 security system Fortinet Technologies Inc.
l Public key exponentiation engine with hardware CRT support
l Primary checking for RSA key generation
l Handshake accelerator with automatic key material generation
l True Random Number generator
l Elliptic Curve support for NSA "Suite B"
l Sub public key engine (PKCE) to support up to 4096 bit operation directly (4k for DH and 8k for RSA with CRT)
l DLP fingerprint support
l TTTD (Two-Thresholds-Two-Divisors) content chunking
l Two thresholds and two divisors are configurable
Splitting the FortiGate-5001E front panel port1 and port2 interfaces
You can use the following command to split the 40-gigabit front panel port1 interface into a 4 x 10-gigabit interface:
config system global
set split-port port1
end
The FortiGate-5001E reboots and when it does you can see four new interfaces named port1/1, port1/2, port1/3, and
port1/4.
FortiGate-5001E System Guide 13
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
13
|
Hardware installation Fortinet Technologies Inc.
Hardware installation
This chapter describes installing a FortiGate-5001E (sometimes just referred to as a "board") into a chassis. Before use,
the FortiGate-5001E must be correctly inserted into an Advanced Telecommunications Computing Architecture (ATCA)
chassis that can provide sufficient power and cooling.
Installing QSFP+ and SFP+ transceivers
You must install QSFP+ transceivers to connect the FortiGate-5001E front panel 1 and 2 interfaces to a 40Gbps
network. The QSFP+ transceivers are inserted into cage sockets numbered 1 and 2 on the FortiGate-5001E front panel.
You can install the QSFP+ transceivers before or after inserting the FortiGate-5001E into a chassis.
You can split front panel interfaces 1 and 2 into four 10GBASE-SR interfaces by installing 40GBASE-SR10 multimode
QSFP+ transceiver.
You must install SR SFP+ transceivers for normal operation of the FortiGate-5001E front panel 3 and 4 interfaces. The
FortiGate-5001E ships with two SR SFP+ transceivers. You can also configure the 3 and 4 interfaces to operate at
1Gbps and install SFP transceivers. You can install the transceivers before or after inserting the FortiGate-5001E into a
chassis.
You can install the following types of transceivers for connectors 3 and 4:
l SFP+ SR (10Gbps)
l SFP+ LR (10Gbps )
l SFP (1Gbps)
To install QSFP+, SFP+ or SFP transceivers
To complete this procedure, you need:
l A FortiGate-5001E
l QSFP+, SFP+ or SFP transceivers
l An electrostatic discharge (ESD) preventive wrist or ankle strap with connection cord
FortiGate-5001Es must be protected from static discharge and physical shock. Only handle or
work with FortiGate-5001Es at a static-free workstation. Always wear a grounded electrostatic
discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
Handling the QSFP+, SFP+ and SFP transceivers by holding the release latch can damage
the connector. Do not force transceivers into their cage slots. If the transceiver does not easily
slide in and click into place, it may not be aligned correctly. If this happens, remove the
transceiver, realign it and slide it in again.
1. Attach the ESD wrist strap to your wrist and to an available ESD socket or wrist strap terminal.
2. Remove the caps from the cage sockets on the FortiGate-5001E front panel.
FortiGate-5001E System Guide 14
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
14
|
Hardware installation Fortinet Technologies Inc.
3. Hold the sides of the transceiver and slide it into the cage socket until it clicks into place.
Changing the FortiGate-5001E SW6 switch settings
FortiGate-5001Es must be protected from static discharge and physical shock. Only handle or
work with FortiGate-5001Es at a static-free workstation. Always wear a grounded electrostatic
discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
You can set the SW6 switch on the FortiGate-5001E to operate the FortiGate-5001E in standalone mode (without a shelf
manager) or in normal mode in a chassis with a shelf manager. Fortinet factory sets the switch for normal mode; allowing
you to install the FortiGate-5001E in a chassis with an operating shelf manager (such as a FortiGate-5144C chassis).
The top of the FortiGate-5001E is covered with a metal panel. The printed circuit board is under the metal panel. SW6 is
located on the area of the printed circuit board that extends from the back side of the FortiGate-5001E as shown in the
following diagram.
Location of SW6 on the FortiGate-5001E circuit board
Front Faceplate
Normal Mode
(Factory Default)
ON
SW
3 421
ON
SW6
21 3 4
ON
SW6
21 3 4
Standalone Mode
(No Shelf Manager)
Location of SW6
FortiGate-5001E System Guide 15
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
15
|
Hardware installation Fortinet Technologies Inc.
SW6 factory default normal mode (shelf-manager mode) setting
Normal Mode
(Factory Default)
ON
SW6
21 3 4
A FortiGate-5001E set to normal mode (the default setting) can be installed into an ATCA chassis (such as a FortiGate5144C chassis) with a shelf manager. By default a FortiGate-5001E will not start up if installed in a chassis that does not
contain a shelf manager or that contains a shelf manager that is not operating.To operate a FortiGate-5001E in a chassis
that does not contain an operating shelf manager, you must change the SW6 switch setting to standalone mode:
SW6 standalone mode setting
ON
SW6
21 3 4
Standalone Mode
(No Shelf Manager)
In all cases you should confirm that you have the correct SW6 setting before installing the FortiGate-5001E in a chassis.
FortiGate-5001E SW6 settings
Chassis Correct SW6 setting Results of incorrect SW6 setting
FortiGate-5144C or ATCA chassis with a
compatible operating shelf manager.
ON
SW6
21 3 4
Shelf manager cannot find the
FortiGate-5001E. No shelf
manager information about the
FortiGate-5001E available.
Any ATCA chassis without an operating shelf
manager.
ON
SW6
21 3 4
FortiGate-5001E will not start
up.
If the shelf manager in a FortiGate-5000 series chassis is missing or not functioning,
FortiGate-5001Es with factory default SW6 settings will not start up.
Changing or verifying the SW6 switch setting
To complete this procedure, you need:
l A FortiGate-5001E.
l A tool for changing the SW6 switch setting (optional).
l An electrostatic discharge (ESD) wrist strap with connection cord.
FortiGate-5001Es must be protected from static discharge and physical shock. Make sure to
handle or work with FortiGate-5001Es at a static-free workstation or always wear a grounded
electrostatic discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
FortiGate-5001E System Guide 16
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
16
|
Hardware installation Fortinet Technologies Inc.
1. Attach the ESD wrist strap to your wrist and to an available ESD socket or wrist strap terminal.
2. If you have installed the FortiGate-5001E in a chassis, remove it.
For removal instructions, see Shutting down and Removing a FortiGate-5001E on page 21.
3. Locate the SW6 switch on the FortiGate-5001E.
4. If required, change the SW6 switch to the correct setting.
5. Insert the FortiGate-5001E into a chassis and verify that it starts up and operates correctly.
For inserting instructions, see Inserting a FortiGate-5001E board into a chassis on page 18.
FortiGate-5001E mounting components
To install a FortiGate-5001E you slide the board into a hub/switch slot in the front of an ATCA chassis (usually slot 3
plus) and then use the mounting components to lock the board into place in the slot. When locked into place and
positioned correctly the board front panel is flush with the chassis front panel. The board is also connected to the chassis
backplane.
FortiGate-5001Es are vertical when inserted into a FortiGate-5144C chassis, but you also
often see the board on a horizontal surface or horizontally in an illustration. Because of this,
the descriptions in this document refer to left (top) and right (bottom) mounting components.
To position the board correctly you must use the mounting components shown below for the right (bottom) of the
FortiGate-5001E front panel. The mounting components on the left (top) of the front panel are the same but reversed.
The FortiGate-5001E mounting components align the board in the chassis slot and are used to insert and eject the board
from the slot.
FortiGate-5001E System Guide 17
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
17
|
Hardware installation Fortinet Technologies Inc.
Closed
Open
Alignment
Pin
Retention
Screw
Lock Handle
Alignment Pin
Retention
Screw
Lock
Handle
Handle
Hook
Alignment Pin
Retention
Screw
Lock
Hook
Alignment
Pin
Retention
Screw
Lock
Handle
The FortiGate-5001E handles align the board in the chassis slot and are used to insert and eject the board from the slot.
The right (bottom) handle activates a microswitch that turns on or turns off power to the board. When the right (bottom)
handle is open the microswitch is off and the board cannot receive power. When the right (bottom) handle is fully closed
the microswitch is on and if the board is fully inserted into a chassis slot the board can receive power.
Inserting a FortiGate-5001E board into a chassis
The FortiGate-5001E must be fully installed in a chassis slot (usually slot 3 plus), with the handles closed and locked and
retention screws fully tightened for the FortiGate-5001E to receive power and operate normally. If the FortiGate-5001E is
not receiving power, the HS LED glows solid blue and all other LEDs remain off.
It is important to carefully seat the FortiGate-5001E all the way into the chassis, to not use too much force on the
handles, and to make sure that the handles are properly locked. Only then will the FortiGate-5001E power-on and start
up correctly.
FortiGate-5001Es are hot swappable. The procedure for inserting a FortiGate-5001E into a chassis slot is the same
whether or not the chassis is powered on.
FortiGate-5001E System Guide 18
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
18
|
Hardware installation Fortinet Technologies Inc.
To insert a FortiGate-5001E into a chassis slot
Do not carry the FortiGate-5001E by holding the handles or retention screws. When inserting
or removing the FortiGate-5001E from a chassis slot, handle the board by the front panel. The
handles are not designed for carrying the board. If the handles become bent or damaged the
FortiGate-5001E may not align correctly in the chassis slot.
To complete this procedure, you need:
l A FortiGate-5001E
l An ATCA chassis with an empty hub/switch slot
l An electrostatic discharge (ESD) preventive wrist strap with connection cord
FortiGate-5001Es must be protected from static discharge and physical shock. Make sure to
handle or work with FortiGate-5001Es at a static-free workstation or always wear a grounded
electrostatic discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. If required, remove the protective metal frame that the FortiGate-5001E has been shipped in.
3. Insert the FortiGate-5001E into the empty slot in the chassis.
4. Unlock the handles by squeezing the handle locks.
Unlock Handle
5. Open the handles to their fully open positions.
To avoid damaging the lock, make sure you squeeze the handles fully to unlock them before
opening. The handles should pop easily out of the board front panel
FortiGate-5001E System Guide 19
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
19
|
Hardware installation Fortinet Technologies Inc.
Handle
Alignment Pin
Open
Alignment Pin
Lock
Handle
6. Carefully guide the FortiGate-5001E into the chassis using the rails in the slot.
Insert the FortiGate-5001E by applying moderate force to the front faceplate (not the handles) to slide the board into
the slot. The board should glide smoothly into the chassis slot. If you encounter any resistance while sliding the
board in, the board could be aligned incorrectly. Pull the board back out and try inserting it again.
7. Slide the board in until the alignment pins are inserted half way into their sockets in the chassis.
8. Turn both handles to their fully-closed positions.
The handles should hook into the sides of the chassis slot. Closing the handles draws the board into position in the
chassis slot and into full contact with the chassis backplane. The board front panel should be in contact with the
chassis front panel. When the handles are fully-closed they lock into place.
As the right (bottom) handle closes the microswitch is turned on, supplying power to the board. If the chassis is
powered on the HS LED starts flashing blue. If the board is aligned correctly, inserted all the way into the slot, and
the right (bottom) handle is properly closed the HS LED flashes blue for a few seconds. At the same time the ACC
LEDs turn green. After a few seconds the HS LED goes out and the FortiGate-5001E firmware starts up. If the board
is operating correctly, the front panel LEDs are lit as described below.
If the board has not been inserted properly the HS LED changes to solid blue and all other LEDS turn off. If this
occurs, open the handles, slide the board part way out, and repeat the insertion process.
9. Once the board is inserted correctly, fully tighten the retention screws to lock the FortiGate-5001E into position in
the chassis slot.
Tighten
Retention
Screw
FortiGate-5001E System Guide 20
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
20
|
Hardware installation Fortinet Technologies Inc.
FortiGate-5001E normal operating LEDs
LED State
OOS Off
PWR Green
STA Off
ACC Off (Or flashing green when the system accesses the FortiController-5903C flash
disk.)
IPM Off
Shutting down and Removing a FortiGate-5001E
To avoid potential hardware problems, always shut down the FortiGate-5001E operating system properly before
removing the FortiGate-5001E from a chassis slot or before powering down the chassis.
The following procedure describes how to correctly use the FortiGate-5001E mounting components to remove a
FortiGate-5001E from an ATCA chassis slot.
FortiGate-5001E are hot swappable. The procedure for removing a FortiGate-5001E from a chassis slot is the same
whether or not the chassis is powered on.
To remove a FortiGate-5001E from a chassis slot
Do not carry the FortiGate-5001E by holding the handles or retention screws. When inserting
or removing the FortiGate-5001E from a chassis slot, handle the board by the front panel. The
handles are not designed for carrying the board. If the handles become bent or damaged the
FortiGate-5001E may not align correctly in the chassis slot.
To complete this procedure, you need:
l An ATCA chassis with a FortiGate-5001E installed
l An electrostatic discharge (ESD) preventive wrist strap with connection cord
FortiGate-5001Es must be protected from static discharge and physical shock. Make sure to
handle or work with FortiGate-5001Es at a static-free workstation or always wear a grounded
electrostatic discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Disconnect all cables from the FortiGate-5001E, including all network cables and the console cable.
3. Fully loosen the FortiGate-5001E retention screws.
FortiGate-5001E System Guide 21
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
21
|
Hardware installation Fortinet Technologies Inc.
Loosen
Retention
Screw
4. Unlock the handles by squeezing the handle locks.
5. Slowly open both handles a small amount (about 8 degrees) until the IPM LED flashes blue.
6. Keep the handles in this position until the IPM LED stops flashing and becomes solid blue.
Waiting for the IPM LED to change to solid blue makes sure that the board software
shutdowns completely before disconnecting it from backplane power.
7. Open the handles to their fully open positions.
Opening the handles turns off the microswitch, turns off all LEDs, and ejects the board from the chassis slot. You
need to use moderate pressure on the handles to eject the board.
To avoid damaging the lock, make sure you squeeze the handles fully to unlock them before
opening. The handles should pop easily out of the board front panel.
.
Handle
Alignment Pin
Open
Alignment Pin
Lock
Handle
8. Pull the board about half way out.
9. Turn both handles to their fully-closed positions.
When the handles are fully-closed they lock into place.
FortiGate-5001E System Guide 22
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
22
|
Hardware installation Fortinet Technologies Inc.
Fully Closed
and Locked
Alignment Pin
Handle
Close
Alignment Pin
Handle
10. Carefully slide the board completely out of the slot.
11. Re-attach the protective metal frame if you are going ship the FortiGate-5001E or store it outside of a chassis.
Resetting a FortiGate-5001E
You can use the following procedure to reset a FortiGate-5001E without removing it from the chassis. You do not have to
loosen the retention screws or adjust the position of the FortiGate-5001E to use this procedure.
To complete this procedure, you need:
l An ATCA chassis with a FortiGate-5001E installed
l An electrostatic discharge (ESD) preventive wrist strap with connection cord
FortiGate-5001Es must be protected from static discharge and physical shock. Make sure to
handle or work with FortiGate-5001Es at a static-free workstation or always wear a grounded
electrostatic discharge (ESD) preventive wrist strap when handling FortiGate-5001Es.
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Unlock the right handle by squeezing the handle lock.
Unlock Handle
3. Pivot the right handle open.
The handle can only pivot a short distance. Pivoting the right handle turns off the microswitch which powers down
the board, turning off all LEDs except the IPM LED which turns on.
FortiGate-5001E System Guide 23
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
23
|
Hardware installation Fortinet Technologies Inc.
4. After 10 seconds snap the right handle back into place.
5. The board powers up, the LEDs light and in a few minutes the FortiGate-5001E operates normally.
Troubleshooting
This section describes some common troubleshooting topics:
FortiGate-5001E does not startup
Positioning of FortiGate-5001E handles and a few other causes may prevent a FortiGate-5001E from starting up
correctly.
Chassis with a shelf manager: no communication with shelf manager
If the FortiGate-5001E is receiving power and the handles are fully closed and the FortiGate-5001E still does not start
up, the problem could be that the FortiGate-5001E cannot communicate with the chassis shelf manager. This problem
can only occur in an ATCA chassis that contains a shelf manager.
To correct this problem power down and then restart the chassis. If you are operating a FortiGate-5000 series chassis
you can power down and then restart the chassis without removing FortiGate-5000 series components.
All chassis: handles not fully closed
If the handles are damaged or positioned incorrectly the FortiGate-5001E will not start up. Make sure the handles are
correctly aligned, fully inserted and locked.
All chassis: Firmware problem
If the FortiGate-5001E is receiving power and the handles are fully closed, and you have restarted the chassis and the
FortiGate-5001E still does not start up, the problem could be with FortiOS. Connect to the FortiGate-5001E console and
try cycling the power to the board. If the BIOS starts up, interrupt the BIOS startup and install a new firmware image.
If this does not solve the problem, contact Fortinet Technical Support.
FortiGate-5001E status LED is flashing during system operation
Normally, the FortiGate-5001E Status LED is off when the FortiGate-5001E is operating normally. If this LED starts
flashing while the board is operating, a fault condition may exist. At the same time the FortiGate-5001E may stop
processing traffic.
To resolve the problem you can try removing and reinserting the FortiGate-5001E in the chassis slot. Reloading the
firmware may also help.
If this does not solve the problem there may have been a hardware failure or other problem. Contact Fortinet Technical
Support for assistance.
FortiGate-5001E System Guide 24
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
24
|
Hardware installation Fortinet Technologies Inc.
Fabric backplane communication speed compatibility
To make sure the FortiGate-5001E can successfully communicate with the fabric backplane you should make sure the
fabric backplane interfaces are set to the correct speed for the chassis and the backplane switching device.
Do not set the FortiGate-5001E fabric backplane interfaces to auto negotiate. In most cases this setting will cause
interruptions or compatibility issues.
This applies to fabric backplane interfaces fabric1 and fabric2 as well as any VLANs added to these interfaces. For
example, SLBC configurations include interfaces such as elbc-ctrl/1 and elbc-ctrl/2 that must be able to connect to the
fabric backplane.
For example, if the FortiGate-5001E is installed in a FortiGate-5144C chassis with a 40-Gbyte backplane the FortiGate5001E fabric backplane interfaces should be set to 40000full:
config system interface
edit fabric1
set speed 40000full
next
edit fabric2
set speed 40000full
next
edit elbc-ctrl/1
set speed 40000full
next
edit elbc-ctrl/2
set speed 40000full
end
If the FortiGate-5001E is installed in a chassis with a 10-gbyte backplane (such as the FortiGate-5060 or 5140B) the
FortiGate-5001E fabric backplane interfaces should be set to 10000full:
config system interface
edit fabric1
set speed 10000full
next
edit fabric2
set speed 10000full
next
edit elbc-ctrl/1
set speed 10000full
next
edit elbc-ctrl/2
set speed 10000full
end
FortiGate-5001E System Guide 25
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
25
|
FortiGate-5001E quick configuration guide Fortinet Technologies Inc.
FortiGate-5001E quick configuration guide
This section is a quick start guide to connecting and configuring a FortiGate-5001E security system for your network.
Before using this chapter, your FortiGate-5000 series or compatible ATCA chassis should be mounted and connected to
your power system. In addition, your FortiGate-5001E should be inserted into the chassis and QSFP+ or SFP+
transceivers should be installed. The FortiGate-5001E should also be powered up and the front panel LEDs should
indicate that the board is functioning normally.
Registering your FortiGate-5001E
Register your FortiGate-5001E to receive Fortinet customer services such as product updates and customer support.
You must also register your product for FortiGuard services. Register your product by visiting
https://support.fortinet.com. To register, enter your contact information and the serial numbers of the Fortinet products
that you or your organization have purchased.
Planning the configuration
Before beginning to configure your FortiGate-5001E security system, you need to plan how to integrate the cluster into
your network. In NAT/Route mode, the FortiGate-5001E security system is visible to the networks that it is connected to.
Each interface connected to a network must be configured with an IP address that is valid for that network. In many
configurations, in NAT/Route mode all of the FortiGate interfaces are on different networks, and each network is on a
separate subnet.
You would typically use NAT/Route mode when the FortiGate-5001E security system is deployed as a gateway between
private and public networks. In the default NAT/Route mode configuration, the FortiGate-5001E security system
functions as a firewall. Firewall policies control communications through the FortiGate-5001E security system. No traffic
can pass through the FortiGate-5001E security system until you add firewall policies.
In NAT/Route mode, firewall policies can operate in NAT mode or in Route mode. In NAT mode, the firewall performs
network address translation before IP packets are sent to the destination network. In Route mode, no translation takes
place.
FortiGate-5001E System Guide 26
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
26
|
FortiGate-5001E quick configuration guide Fortinet Technologies Inc.
FortiGate-5001E
in NAT/Route mode
port1
192.168.1.2
port2
204.23.1.2
Internal
network
NAT mode policies
controlling traffic
between internal
and external networks
Choosing the configuration tool
You can use either the GUI or the Command Line Interface (CLI) to configure the FortiGate-5001E. Some basic
configuration settings can only be done from the CLI. You can connect to the GUI by connecting to mgmt1 using HTTP or
HTTPS. You can connect to the CLI by connecting to mgmt1 using SSH or Telent or by a direct console connection to
the FortiGate-5001E Console port. Use a terminal emulator with the following settings to connect to the console port: bits
per second: 9600, data bits: 8, parity: none, stop bits: 1, flow control: none.
Factory default settings
The FortiGate-5001E ships with the following factory default configuration.
Option Default Configuration
Administrator Account User
Name
admin
Password (none)
mgmt1 IP/Netmask 192.168.1.99/24
mgmt2 IP/Netmask 192.168.100.99/24
FortiGate-5001E System Guide 27
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
27
|
FortiGate-5001E quick configuration guide Fortinet Technologies Inc.
Option Default Configuration
Default route Gateway 192.168.100.1
Device mgmt2
At any time during the configuration process, if you run into problems, you can reset the FortiGate-5001E to the factory
defaults and start over. From the CLI enter execute factoryreset.
Basic GUI configuration
Use the following steps to set up a basic configuration.
1. Connect to the FortiGate-5001E mgmt1 interface by browsing to https://192.168.1.99.
2. Type admin in the Name field and select Login.
3. Change the admin administrator password by going to System > Administrators.
4. Edit the admin administrator and select Change Password to add a pasword.
5. To configure interfaces go to Network > Interfaces and edit each interface to configure.
6. To configure DNS setting go to Network > DNS.
7. To configure the Default Gateway go to Network > Static Routes and Edit the static route with destination
0.0.0.0/0.
Basic CLI configuration
Use the following steps to set up a basic configuration.
Use the serial cable supplied with your FortiGate-5001E to connect the FortiGate-5001E Console port or use SSH to
connect to the mgmt1 interface CLI.
At the Login: prompt, type admin and press Enter twice (no password required).
Change the administrator password.
config system admin
edit admin
set password <password>
end
Configure the mgmt1, port1, and port1 interfaces.
config system interface
edit mgmt1
set ip <intf_ip>/<netmask_ip>
next
edit port1
set ip <intf_ip>/<netmask_ip>
next
edit port2
set ip <intf_ip>/<netmask_ip>
end
FortiGate-5001E System Guide 28
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
28
|
FortiGate-5001E quick configuration guide Fortinet Technologies Inc.
Configure the primary and secondary DNS server IP addresses..
config system dns
set primary <dns-server_ip>
set secondary <dns-server_ip>
end
Configure the default gateway.
config router static
edit 1
set device <interface_name>
set gateway <gateway_ip>
end
Upgrading FortiGate-5001E firmware
Fortinet periodically updates the FortiGate-5001E FortiOS firmware to include enhancements and address issues. After
you have registered your FortiGate-5001E security system you can download FortiGate-5001E firmware from the
support web site https://support.fortinet.com.
Only FortiGate-5001E administrators (whose access profiles contain system read and write privileges) and the
FortiGate-5001E admin user can change the FortiGate-5001E firmware.
1. Copy the firmware image file to your management computer.
2. Log into the GUI as the admin administrator.
3. From the System Information widget, select Update beside Firmware Version.
4. Select Upload Firmware, select the firmware image file that you downloaded. The FortiGate-5001E uploads the
firmware image file, upgrades to the new firmware version, restarts, and displays the FortiGate-5001E login. This
process takes a few minutes.
5. Log into the GUI.
6. Check the Firmware Version on the System Information widget to confirm the firmware upgrade is successfully
installed.
7. Update the FortiGate-5001E antivirus and attack definitions.
FortiGate-5001E fabric and base backplane communication
By default the fabric and base backplane interfaces are not enabled. Once they are enabled you can operate and
configure them in the same way as any FortiGate-5001E interfaces. Normally the fabric interfaces are used for data
communication and the base interfaces are used for FGCP HA heartbeat communication. Although not recommended,
you can use base backplane interfaces for data and HA heartbeat communication at the same time.
FortiGate-5001E fabric and base backplane communication requires a FortiSwitch or FortiController in switch mode
installed in chassis slots 1 or 2. A FortiSwitch or FortiController in chassis slot 1 provides fabric communication on the
fabric1 interface and base communication on the base1 interface. A FortiSwitch or FortiController installed in chassis
slot 2 provides communication on the fabric2 and base2 interfaces.
Enter the following command to enable backplane data communication:
config system global
FortiGate-5001E System Guide 29
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
29
|
FortiGate-5001E quick configuration guide Fortinet Technologies Inc.
set show-backplane-intf enable
end
The fabric1, fabric2, base1 and base2 interfaces now appear in all Interface lists. You can now configure the base
backplane interfaces and add routes, firewall policies and other configuration settings using these interfaces.
On some chassis and with some hardware you may also have to change the fabric backplane interface speeds. Use the
following command to do this:
To set the speed to be compatible with a 40-gbyte backplane:
config system interface
edit fabric1
set speed 40000full
next
edit fabric2
set speed 40000full
end
To set the speed to be compatible with a 10-gbyte backplane:
config system interface
edit fabric1
set speed 10000full
next
edit fabric2
set speed 10000full
end
FortiGate-5001E System Guide 30
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
30
|
Cautions and Warnings Fortinet Technologies Inc.
Cautions and Warnings
Environmental Specifications
Rack Mount Instructions - The following or similar rack-mount instructions are included with the installation
instructions:
Instructions de montage en rack - Les instructions de montage en rack suivantes ou similaires sont incluses avec les
instructions d'installation:
Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, the operating ambient temperature of
the rack environment may be greater than room ambient. Therefore, consideration should be given to installing the
equipment in an environment compatible with the maximum ambient temperature (Tma) specified by the manufacturer.
Température ambiante élevée – S'il est installé dans un rack fermé ou à unités multiples, la température ambiante de
fonctionnement de l'environnement du rack peut être supérieure à la température ambiante de la pièce. Par conséquent,
il est important d’installer le matériel dans un environnement respectant la température ambiante maximale (Tma)
stipulée par le fabricant.
Reduced Air Flow - Installation of the equipment in a rack should be such that the amount of air flow required for safe
operation of the equipment is not compromised.
Ventilation réduite – Installation de l'équipement dans un rack doit être telle que la quantité de flux d'air nécessaire au
bon fonctionnement de l'équipement n'est pas compromise.
Mechanical Loading - Mounting of the equipment in the rack should be such that a hazardous condition is not achieved
due to uneven mechanical loading.
Chargement Mécanique – Montage de l'équipement dans le rack doit être telle qu'une situation dangereuse n'est pas
lié à un chargement mécanique inégal.
Circuit Overloading - Consideration should be given to the connection of the equipment to the supply circuit and the
effect that overloading of the circuits might have on overcurrent protection and supply wiring. Appropriate consideration
of equipment nameplate ratings should be used when addressing this concern.
Surtension – Il convient de prendre l’ensemble des précautions nécessaires lors du branchement de l’équipement au
circuit d’alimentation et être particulièrement attentif aux effets de la suralimentation sur le dispositif assurant une
protection contre les courts-circuits et le câblage. Ainsi, il est recommandé de tenir compte du numéro d’identification de
l’équipement.
Reliable Earthing - Reliable earthing of rack-mounted equipment should be maintained. Particular attention should be
given to supply connections other than direct connections to the branch circuit (e.g. use of power strips).
Fiabilité de la mise à la terre – Fiabilité de la mise à la terre de l'équipement monté en rack doit être maintenue. Une
attention particulière devrait être accordée aux connexions d'alimentation autres que les connexions directes au circuit
de dérivation (par exemple de l'utilisation de bandes de puissance).
FortiGate-5001E System Guide 31
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
31
|
Cautions and Warnings Fortinet Technologies Inc.
Blade Carriers, Cards and Modems must be Listed Accessories or Switch, Processor, Carrier and similar blades or
cards should be UL Listed or Equivalent.
Serveur-blades, cartes et modems doivent être des accessoires listés ou commutateurs, processeurs, serveurs et
similaire blades ou cartes doivent être listé UL ou équivalent.
Refer to specific Product Model Data Sheet for Environmental Specifications (Operating Temperature, Storage
Temperature, Humidity, and Altitude).
Référez à la Fiche Technique de ce produit pour les caractéristiques environnementales (Température de
fonctionnement, température de stockage, humidité et l'altitude).
Safety
Moving parts — Hazardous moving parts. Keep away from moving fan blades.
Pièces mobiles – Pièces mobiles dangereuses. Se tenir éloigné des lames mobiles du ventilateur.
Warning: Equipment intended for installation in Restricted Access Location.
Avertissement: Le matériel est conçu pour être installé dans un endroit où l’accès est restreint.
Warning: A readily accessible disconnect device shall be incorporated in the building installation wiring.
Avertissement: Un dispositif de déconnexion facilement accessible doit être incorporé dans l'installation électrique du
bâtiment.
Battery – Risk of explosion if the battery is replaced by an incorrect type. Do not dispose of batteries in a fire. They may
explode. Dispose of used batteries according to your local regulations. IMPORTANT: Switzerland: Annex 4.10 of
SR814.013 applies to batteries.
Batterie – Risque d'explosion si la batterie est remplacée par un type incorrect. Ne jetez pas les batteries au feu. Ils
peuvent exploser. Jetez les piles usagées conformément aux réglementations locales. IMPORTANT: Suisse: l'annexe
4.10 de SR814.013 s’appliquent aux batteries.
警告
本電池如果更換不正確會有爆炸的危險
請依製造商說明書處理用過之電池
Caution: Disconnect power supply cords before servicing
Attention: Débranchez les cordons de la source d’alimentation avant tout entretien.
Grounding — To prevent damage to your equipment, connections that enter from outside the building should pass
through a lightning / surge protector, and be properly grounded. Use an electrostatic discharge workstation (ESD) and/or
wear an anti-static wrist strap while you work. In addition to the grounding terminal of the plug, on the back panel, there is
another, separate terminal for earthing.
FortiGate-5001E System Guide 32
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
32
|
Cautions and Warnings Fortinet Technologies Inc.
Mise à la terre — Pour éviter d’endommager votre matériel, assurez-vous que les branchements qui entrent à partir de
l’extérieur du bâtiment passent par un parafoudre / parasurtenseur et sont correctement mis à la terre. Utilisez un poste
de travail de décharge électrostatique (ESD) et / ou portez un bracelet anti-statique lorsque vous travaillez. Ce produit
possède une borne de mise à la terre qui est prévu à l’arrière du produit, à ceci s’ajoute la mise à la terre de la prise.
This product has a separate protective earthing terminal provided on the back of the product in addition to the grounding
terminal of the attachment plug. This separate protective earthing terminal must be permanently connected to earth with
a green with yellow stripe conductor minimum size # 6 AWG and the connection is to be installed by a qualified service
personnel.
Ce produit a une borne de mise à la terre séparé sur le dos de l'appareil, en plus de la borne de mise à la terre de la fiche
de raccordement. Cette borne de mise à la terre séparée doit être connecté en permanence à la terre avec un
conducteur vert avec la taille bande jaune de minimum # 6 AWG et la connexion doit être installé par un personnel
qualifié.
Caution: Slide/rail mounted equipment is not to be used as a shelf or a work space.
Attention: Un équipement monté sur bâti ne doit pas être utilisé sur une étagère ou dans un espace de travail.
Fiber optic transceiver must be rated 3.3V, 22mA max, Laser Class 1, UL certified component.
Le transceiver optique doit avoir les valeurs nominales de 3.3 V, maximum 22 mA, Laser Class 1, homologué UL.
FortiGate-5001E System Guide 33
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
33
|
Regulatory Notices Fortinet Technologies Inc.
Regulatory Notices
Federal Communication Commission (FCC) – USA
This device complies with Part 15 of FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received; including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency
energy, and if it is not installed and used in accordance with the instruction manual, it may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which
case the user will be required to correct the interference at his own expense.
WARNING: Any changes or modifications to this product not expressly approved by the party responsible for
compliance could void the user’s authority to operate the equipment.
Industry Canada Equipment Standard for Digital Equipment (ICES) –
Canada
CAN ICES-3 (A) / NMB-3 (A)
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the
Radio Interference Regulations of the Canadian Department of Communications.
Cet appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils
numériques de la classe A prescrites dans le Règlement sur le brouillage radioélectrique édicte par le ministère des
Communications du Canada.
European Conformity (CE) - EU
This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user
may be required to take adequate measures.
FortiGate-5001E System Guide 34
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
34
|
Regulatory Notices Fortinet Technologies Inc.
Voluntary Control Council for Interference (VCCI) – Japan
この装置は、クラスＡ情報技術装置です。この装置を家庭環境で使用すると電波妨害を引き起こすことがあります。この場
合には使用者が適切な対策を講ずるよう要求されることがあります。ＶＣＣＩ－Ａ
Product Safety Electrical Appliance & Material (PSE) – Japan
日本では電気用品安全法(PSE)の規定により、同梱している電源コードは本製品の専用電源コードとして利用し、他の製
品に使用しないでください。
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan
這是甲類的資訊產品，在居住的環境中使用時，可能會造成射頻干擾，在這種情況下，使用者會被要求採取某些
適當的對策。
China
此为A级产品，在生活环境中，该产品可能会造成无线电干扰。这种情况下，可能需要用户对其采取切实可行的
措施。
FortiGate-5001E System Guide 35
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
35
|
Regulatory Notices Fortinet Technologies Inc.
FortiGate-5001E System Guide 36
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
36
|
Copyright© 2021 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., in the
U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be
trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and
other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein represents any binding
commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s
General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such
event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be
limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any commitment related to future deliverables, features or
development, and circumstances may change such that any forward-looking statements herein are not accurate. Fortinet disclaims in full any covenants, representations, and
guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most
current version of the publication shall be applicable.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/7b72a53e-1a0a-11e9-9685-f8bc1258b856/fortigate-5001E-security-system-guide.pdf
|
0
|
FortiGate 6000F Series System
Guide
FortiGate 6000F Series
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
1
|
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET VIDEO LIBRARY
https://video.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com
FORTINET TRAINING & CERTIFICATION PROGRAM
https://www.fortinet.com/training-certification
FORTINET TRAINING INSTITUTE
https://training.fortinet.com
FORTIGUARD LABS
https://www.fortiguard.com
END USER LICENSE AGREEMENT
https://www.fortinet.com/doc/legal/EULA.pdf
FEEDBACK
Email: techdoc@fortinet.com
October 23, 2024
FortiGate 6000F Series 7.0.12 System Guide
01-7012-464766-20241023
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
2
|
TABLE OF CONTENTS
Change log 5
FortiGate 6000F series hardware description 7
FortiGate 6001F model licensing 8
Applying your FortiGate 6001F FPC subscription license 8
Activating your FortiGate 6001F FPC perpetual license 9
Verifying your FortiGate 6001F FPC subscription and perpetual licenses 9
What to expect when your subscription license expires 9
Front panel interfaces 10
Interface groups and changing data interface speeds 10
Front panel LEDs 11
Front panel connectors 12
Console port 13
Connecting to the CLI of an individual FPC 14
NMI switch and NMI reset commands 15
FortiGate 6000F series back panel 15
FortiGate 6000F series schematic 16
FortiGate 6000F series hardware information 17
Shipping components 17
Optional accessories and replacement parts 18
Physical description of the FortiGate 6000F 18
FortiGate 6000F series hardware generations 19
Cooling fan trays 19
FortiGate 6000F AC power supply units (PSUs) 20
Connecting generation 2 FortiGate 6000F PSUs to high line AC power 21
Connecting generation 1 or 2 FortiGate 6000F PSUs to low line AC power 22
AC PSU LED states 22
Connecting FortiGate 6000F PSUs to AC power 23
Hot swapping an AC PSU 23
DC PSUs and supplying DC power to a FortiGate 6000F 24
DC PSU LED States 25
Crimping guidelines 25
Connecting a FortiGate 6000F DC PSU to DC power 26
Hot Swapping a DC PSU 27
Connecting the FortiGate 6000F to ground 27
FortiGate 6000F hardware assembly and rack mounting 29
Cautions and warnings 29
Cooling air flow and required minimum air flow clearance 29
FortiGate 6000F four post rack-mount installation 30
Installation steps 30
Sliding the FortiGate 6000F into the rack 32
Removing the FortiGate 6000F from a four-post rack 34
Surface-mount installation 35
Installing QSFP28, SFP28, SFP+, and SFP transceivers 35
FortiGate 6000F Series System Guide 3
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
3
|
Fortinet Technologies Inc.
To install transceivers 36
Getting started with FortiGate 6000F series 37
Confirming startup status 38
Default VDOM configuration and configuring the management interfaces 39
Changing data interface network settings 39
Resetting to factory defaults 39
Restarting the FortiGate 6000F 39
Changing the FortiGate 6001F, FortiGate 6501F, or FortiGate 6301F log disk and RAID
configuration 40
Managing individual FortiGate 6000F management boards and FPCs 41
Special management port numbers 41
HA mode special management port numbers 42
Connecting to individual FPC consoles 43
Connecting to individual FPC CLIs 44
Performing other operations on individual FPCs 44
Firmware upgrades 45
Firmware upgrade basics 45
Installing firmware on an individual FPC 46
Installing firmware from the BIOS after a reboot 48
Synchronizing the FPCs with the management board 49
Decommissioning a FortiGate 6000F 51
Before you begin 51
Decommissioning steps 55
Disable and erase the comlog (SMC-LAN-interface) 56
Securely erase and overwrite each FPC’s system flash 58
Erase the log disks (FortiGate 6001F, FortiGate 6301F, and FortiGate 6501F only) 60
Erase the management board system flash 61
Final decommissioning of the log disks (optional) 64
Cautions and warnings 65
Environmental specifications 65
Safety 66
Regulatory notices 68
Federal Communication Commission (FCC) – USA 68
Industry Canada Equipment Standard for Digital Equipment (ICES) – Canada 68
European Conformity (CE) - EU 68
Voluntary Control Council for Interference (VCCI) – Japan 69
Product Safety Electrical Appliance & Material (PSE) – Japan 69
Bureau of Standards Metrology and Inspection (BSMI) – Taiwan 69
China 69
Agência Nacional de Telecomunicações (ANATEL) – Brazil 70
Korea Certification (KC) – Korea 70
FortiGate 6000F Series System Guide 4
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
4
|
Change log Fortinet Technologies Inc.
Change log
Date Change description
October 23, 2024 New section: Decommissioning a FortiGate 6000F on page 51.
More information added about the FortiGate 6001F and how FortiGate 6001F licensing
works. See FortiGate 6001F model licensing on page 8.
The execute load-balance update and the execute load-balance loadbackup-image commands were removed from the FortiGate 6000F for FortiOS
7.4.0. All references to these commands have been removed from this document. The
section Installing firmware on an individual FPC on page 46 has been updated to
describe how to install firmware on an individual FPC from the FPC BIOS.
October 6, 2023 Added information about the FortiGate 6001F, a new FortiGate 6000F series model
that includes a total of ten FPCs, by default three of them are active. To increase
throughput you can purchase perpetual or subscription licenses for each of the
additional seven FPCs for a total of ten, see:
l FortiGate 6000F series hardware description on page 7.
l FortiGate 6001F model licensing on page 8.
l FortiGate 6000F series schematic on page 16.
l FortiGate 6000F series hardware generations on page 19.
March 28, 2023 Removed the Supported transceivers section. See the FortiGate 6000F datasheet or
contact Fortinet for current information about supported transceivers.
August 17, 2022 Added information about what happens to the RAID configuration of a FortiGate 6301F
or 6501F after installing firmware from the BIOS. See Installing firmware from the
BIOS after a reboot on page 48.
December 22, 2021 Added links to information about grounding the FortiGate 6000F to AC and DC power
sections.
July 15, 2021 Corrections and additions to Regulatory notices on page 68.
May 13, 2021 Added information about FortiGate 6000F DC models.
l The DC models are listed here FortiGate 6000F series hardware description on
page 7.
l Details about DC power are here: DC PSUs and supplying DC power to a
FortiGate 6000F on page 24.
January 21, 2021 Added information about FortiGate 6000F hardware generation 1 and generation 2,
see FortiGate 6000F series hardware generations on page 19.
January 14, 2021 Updates and corrections to FortiGate 6000F AC power supply units (PSUs) on page
20. Removed DC power content that was added incorrectly.
December 23, 2020 The section FortiGate 6000F AC power supply units (PSUs) on page 20 has been
updated for the FortiGate 6000F generation 2.
The new section Connecting generation 1 or 2 FortiGate 6000F PSUs to low line AC
power on page 22 describes FortiGate 6000F generation 1 AC PSUs.
FortiGate 6000F Series System Guide 5
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
5
|
Change log Fortinet Technologies Inc.
Date Change description
September 2, 2020 More information about FPC failure with power loss added to FortiGate 6000F AC
power supply units (PSUs) on page 20.
April 13, 2020 Updated Console port on page 13 and Shipping components on page 17 to include the
USB to RJ-45 console cable. Other minor changes.
October 25, 2019 Misc. fixes.
October 18, 2019 Misc. fixes.
October 11, 2019 New information added to: Console port on page 13 and FortiGate 6000F four post
rack-mount installation on page 30. Corrections to FortiGate 6000F series back panel
on page 15 and FortiGate 6000F AC power supply units (PSUs) on page 20.
FortiGate 6000F Series System Guide 6
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
6
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
FortiGate 6000F series hardware description
The FortiGate 6000F series is a collection of 3U 19-inch rackmount appliances that include twenty-four 1/10/25GigE
SFP28 and four 40/100GigE QSFP28 data network interfaces, as well as NP6 and CP9 processors to deliver high
IPS/threat prevention performance.
Currently, the following FortiGate 6000F series models are available:
l FortiGate 6500F and FortiGate 6500F-DC
l FortiGate 6501F and FortiGate 6501F-DC
l FortiGate 6300F and FortiGate 6300F-DC
l FortiGate 6301F and FortiGate 6301F-DC
l FortiGate 6001F and FortiGate 6001F-DC
All FortiGate 6000F series models have the same front and back panel configuration including the same network
interfaces. The differences are the processing capacity of the individual models. All FortiGate 6000F series models
include a management board (MBD) and internal Fortinet Processor Cards (FPCs) that contain NP6 and CP9 security
processors. The management board handles management tasks, separating management tasks from data processing
tasks that are handled by the FPCs. The FortiGate 6000F series uses session-aware load balancing to distribute
sessions to the FPCs. The FortiGate 6500F includes ten FPCs and the FortiGate 6300F includes six FPCs.
The FortiGate 6001F model includes a total of ten FPCs, by default three of them are active. To increase throughput you
can purchase perpetual or subscription licenses for each of the additional seven FPCs for a total of ten.
Also the FortiGate 6501F, 6301F, and 6001F models include two internal 1 TByte log disks in a RAID-1 configuration.
FortiGate 6000F Series 7.0.12 System Guide 7
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
7
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
FortiGate 6000F series front panel (FortiGate 6500F model shown)
FortiGate 6001F model licensing
The FortiGate 6001F model includes a total of ten FPCs, by default three of them are active. To increase throughput you
can purchase subscription or perpetual licenses for each of the additional seven FPCs for a total of ten.
l A subscription license provides access to one or more FPCs for the term of the subscription. Subscription licenses
are managed by FortiGuard.
l A perpetual license provides permanent access to one or more FPCs. Perpetual licenses are managed by applying
a license key.
Subscription and perpetual licenses can be purchased from Fortinet. The package you get when you purchase the
license includes instructions for applying the license to your FortiGate from the Fortinet Support website.
Applying your FortiGate 6001F FPC subscription license
To apply your FortiGate 6001F FPC subscription license, you must register your FortiGate 6001F and purchase a
FPC subscription license for it. From the Fortinet Support website you can apply the FPC perpetual license to the
FortiGate 6001F.
FortiGate 6000F Series 7.0.12 System Guide 8
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
8
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
The subscription license will then be applied to the registered FortiGate 6001F through FortiGuard. It can take some time
for the subscription license to be applied. From the FortiGate 6001F, you can enter the command execute updatenow to start a FortiGuard update instead of waiting for the next scheduled update.
Activating your FortiGate 6001F FPC perpetual license
To activate your FortiGate 6001F FPC perpetual license, you must register your FortiGate 6001F and purchase a
FPC perpetual license for it. From the Fortinet Support website you can apply the FPC perpetual license to the FortiGate
6001F and obtain your FPC perpetual license activation code or license key.
You can use the following command to apply your FPC perpetual license activation code or license key to activate FPCs
for your FortiGate 6001F:
execute upd-perpetual-license <license-key>
After you enter this command, the FortiGate 6001F restarts and the licensed FPCs will be available.
Verifying your FortiGate 6001F FPC subscription and perpetual licenses
You can use the diagnose load-balance status command or the Cluster Status dashboard widget to view the
number of FPCs that are available. These methods don't include any information about subscription or perpetual
licenses, but they will show you how many FPCs are available, including the licensed FPCs.
You can enter the get system status command to see the number of FPCs licensed by your perpetual license and
by your subscription license. In the following example, the FortiGate 6001F has a perpetual license for two FPCs and a
subscription license for three FPCs.
get system status
.
.
.
FPC perpetual/subscription license: 2/3
You can also enter the following command to check the number of FPCs that you have subscription licenses for and the
license expiration date. The following output shows a subscription license for three FPCs and that the license expires on
June 26, 2025.
diagnose load-balance fpc-license
==========================================================================
MBD SN: <sn>
subscription-license : 3
subscription-license: Thu Jun 26 2025
What to expect when your subscription license expires
When the subscription license expires, the licensed FPCs are powered down and the output of the diagnose loadbalance fpc-license command changes to the following:
diagnose load-balance fpc-license
==========================================================================
MBD SN: <sn>
FortiGate 6000F Series 7.0.12 System Guide 9
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
9
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
subscription-license : 0
subscription-expiration: Expired
There is a one hour grace period between the time the license expires and when the FPCs are shut down. If you run the
diagnose load-balance fpc-license command during that hour grace period, the FPCs shut down immediately.
Front panel interfaces
All FortiGate 6000F models have the following front panel interfaces:
l Twenty-four 1/10/25GigE SFP28 data network interfaces (1 to 24). The default speed of these interfaces is 10Gbps.
These interfaces are divided into the following interface groups: 1 - 4, 5 - 8, 9 - 12, 13 - 16, 17 - 20, and 21 - 24.
l Four 40/100GigE QSFP28 data network interfaces (25 to 28). The default speed of these interfaces is 40Gbps.
l Two front panel 1/10GigE SFP+ HA interfaces (HA1 and HA2) used for heartbeat, session sync, and management
communication between two and only two FortiGate 6000Fs in an HA cluster. The default speed of these interfaces
is 10Gbps. Operating them at 1Gbps is not recommended. A FortiGate 6000F cluster consists of two (and only two)
FortiGate 6000Fs of the same model. To set up HA, you can use a direct cable connection between the FortiGate
6000Fs HA1 interfaces and between their HA2 interfaces.
l Two 10/100/1000BASE-T out of band management Ethernet interfaces (MGMT1 and MGMT2).
l One front panel 1/10GigE SFP+ out of band management interface (MGMT3).
l One RJ-45 RS-232 serial console connection.
l One USB connector.
Interface groups and changing data interface speeds
Depending on the networks that you want to connect your FortiGate 6000F to, you may have to manually change the
data interface speeds. The port1 to port24 data interfaces are divided into the following groups:
l port1 - port4
l port5 - port8
l port9 - port12
l port13 - port16
l port17 - port20
l port21 - port24
All of the interfaces in a group operate at the same speed. Changing the speed of an interface changes the speeds of all
of the interfaces in that group. For example, if you change the speed of port18 from 10Gbps to 25Gbps the speeds of
port17 to port20 are also changed to 25Gbps.
The port25 to port28 interfaces are not part of an interface group. You can set the speed of each of these interfaces
independently of the other three.
Another example, the default speed of the port1 to port24 interfaces is 10Gbps. If you want to install 25GigE transceivers
in port1 to port24 to convert these data interfaces to connect to 25Gbps networks, you can enter the following from the
CLI:
config system interface
edit port1
set speed 25000full
next
FortiGate 6000F Series 7.0.12 System Guide 10
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
10
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
edit port5
set speed 25000full
next
edit port9
set speed 25000full
next
edit port13
set speed 25000full
next
edit port17
set speed 25000full
next
edit port21
set speed 25000full
end
Front panel LEDs
LED State Description
STATUS
Off The FortiGate 6000F is powered off.
Green The FortiGate 6000F is powered on and operating normally.
Flashing
Green
The FortiGate 6000F is starting up.
ALARM Red Major alarm. One or more analog sensors have surpassed a critical or nonrecoverable (NR) threshold causing an alarm. When a critical threshold
has been reached, it means that a condition has been detected that has
surpassed an operating tolerance. For example, a temperature has
increased above the allowed operating temperature range.
Amber Minor alarm. One or more analog sensors (excluding PSUs) has
surpassed a major or critical (CR) threshold. Any sensor, including sensors
on PSUs, has generated an alert. Sensor alert criteria is defined per
sensor. For analog sensors, alerts usually mean passing an upper critical
(UC) or lower critical (LC) threshold. For other sensors, an alert could
mean a flag bit is indicating an anomaly.
Off No alarms
HA
Off The FortiGate 6000F is operating in normal mode.
Green The FortiGate 6000F is operating in HA mode.
Red The FortiGate 6000F is operating in HA mode and the HA heartbeat cannot
find the other FortiGate 6000F in the HA cluster.
PWR Off The FortiGate 6000F is powered off.
Green The FortiGate 6000F is powered on and operating normally.
FortiGate 6000F Series 7.0.12 System Guide 11
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
11
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
LED State Description
1 to 24
Link/Activity
Green This interface is connected at 25Gbps /10Gbps /1Gbps with the correct
cable and the attached network device has power.
Flashing
Green
Network traffic on this interface.
Off No link is established.
25 to 28
Link/Activity
Green This interface is connected at 100Gbps /40Gbps with the correct cable and
the attached network device has power.
Flashing
Green
Network traffic on this interface.
Off No Link
MGMT1
MGMT2 Link/
Activity (Left
LED)
Green This interface is connected at 1Gbps or 100Mbps with the correct cable
and the attached network device has power.
Flashing
Green
Network traffic on this interface.
Off No link is established.
MGMT1
MGMT2
Speed (Right
LED)
Green This interface is connected at 1Gbps.
Amber This interface is connected at 100Mbps
Off No link is established.
MGMT3 Link/
Activity (Left
LED)
Green This interface is connected at 10Gbps or 1Gbps with the correct cable and
the attached network device has power.
Flashing
Green
Network activity at the interface.
Off No link is established.
MGMT3
(Right LED) Not used.
HA1 HA2
Link/Activity
Green This interface is connected at 10Gbps or 1Gbps with the correct cable and
the attached network device has power
Flashing
Green
Network activity at the interface.
Off No link is established.
Front panel connectors
You connect the FortiGate 6000F to your 25 Gbps or 10 Gbps networks using the 1 to 24 SFP28 front panel interfaces.
You can also connect the FortiGate 6000F to your 100 Gbps or 40 Gbps networks using the 25 to 28 front panel QSFP28
interfaces. The front panel also includes 10 GigE SPF+ HA heartbeat interfaces (HA1 and HA2), two Ethernet
FortiGate 6000F Series 7.0.12 System Guide 12
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
12
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
10/100/1000 copper management interfaces (MGMT1 and MGMT2), a 10 GigE SPF+ management interface (MGMT3),
an RJ-45 RS-232 serial console port, and a USB port. The USB port can be used with any USB key for backing up and
restoring configuration files.
Connector Type Speed Protocol Description
1 to 24 SFP28 1/10/25Gbps Ethernet 1/10/25GigE connection using
SFP28 or SPF+ transceivers. For
traffic interfaces.
25 to 28 QSFP28 40/100Gbps Ethernet 40/100GigE connections using
QSFP28 or QSFP+ transceivers.
For traffic interfaces.
MGMT1
MGMT2
RJ-45 10/100/1000Mbps Ethernet 10/100/1000BASE-T copper
connections for out of band
management or system
administration.
MGMT3 SFP+ 1/10Gbps Ethernet 1/10GigE connection using an
SFP+ or SFP transceiver. For out of
band management or system
administration.
HA1 HA2 SFP+ 1/10Gbps Ethernet 1/10GigE connection using SFP+ or
SFP transceivers. For HA heartbeat
and synchronization. 1GigE not
recommended.
CONSOLE RJ-45 9600bps
data bits: 8
parity: none
stop bits: 1
flow control: none
RS-232 Serial interface for console access.
USB USB 3.0
Type A
USB 3.0
USB 2.0
Standard USB connector.
Console port
Using standard terminal emulator software (such as PuTTY) and a RS-232 serial convertor, you can connect to the
FortiGate 6000F console port using the following serial settings:
You can use the USB to RJ-45 RS-232 cable included with your FortiGate 6000F Console port to connect to the
FortiGate 6000F CLI with these settings:
Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None
FortiGate 6000F Series 7.0.12 System Guide 13
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
13
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
From the Console port, you can connect to the management board (MBD) CLI of the FortiGate 6000F. You can also
press Ctrl+T to switch between the management board CLI and the CLIs of each of the FPCs in your FortiGate 6000F
(the new destination is displayed in the terminal window). The FortiGate 6500F has a management board and 10 FPCs;
11 consoles in total. The FortiGate 6300F has a management board and 6 FPCs; 7 consoles in total.
To use the CTRL+T shortcut keys to switch to the CLI of each FPC:
l Press CTRL+T once to see the current active slot (MBD or FPC#).
l Quickly double press CTRL+T to switch to the next slot. For example, of you are
connected to the management board, quickly press CTRL+T twice to switch to FPC1.
If this is the first time you are using the console connection, you might want to practice
switching slots to get the timing right.
You should only make configuration changes on the management board CLI. You can cycle through individual FPC
consoles to use diagnose, get, or execute commands to log into individual FPCs.
Once the console port is connected to the CLI that you want to use, press Enter to enable the CLI and log in. When your
session is complete you can press Ctrl+T to connect to another CLI.
Your FortiGate 6000F package includes a USB to RJ-45 serial cable that you can use to connect a management PC
USB port to the FortiGate 6000F console port.
Fortinet USB to RJ-45 serial cable RJ-45 pinout
RJ-45 Color Function
5 Green Ground
3 Black Rx
6 Yellow Tx
Connecting to the CLI of an individual FPC
Use the following steps to connect to the CLI of the FPC in slot 4: (FPC04)
1. Connect the console cable supplied with your FortiGate 6000F to the console port and to your PC USB port.
2. Start a terminal emulation program on the PC. Use these settings:
Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None.
3. Press Ctrl+T to enter console switch mode.
4. Repeat pressing Ctrl+T until you have connected to FPC04. Example prompt:
<Switching to Console: FPC04 (9600)>
FortiGate 6000F Series 7.0.12 System Guide 14
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
14
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
5. Login with an administrator name and password.
6. When your session is complete, enter the exit command to log out.
NMI switch and NMI reset commands
When working with Fortinet Support to troubleshoot problems with your FortiGate 6000F you can use the front panel
non-maskable interrupt (NMI) switch to assist with troubleshooting. Pressing this switch causes the software to dump
management board registers/backtraces to the console. After the data is dumped the management board reboots. While
the management board is rebooting, traffic is temporarily blocked. The management board should restart normally and
traffic can resume once the management board is up and running.
You can use the following command to dump registers/backtraces of one or more FPCs to the console. After the data is
dumped, the FPCs reboot. While the FPCs are rebooting, traffic is distributed to the remaining FPCs. The FPCs should
restart normally and traffic can resume once they are up and running.
execute load-balance slot nmi-reset <slot-number(s)>
Where <slot-number(s)> can be one or more FPC slot numbers or slot number ranges with no space and separated
by commas. For example:
execute load-balance slot nmi-reset 1,3-4
FortiGate 6000F series back panel
The FortiGate 6000F series back panel includes three hot swappable cooling fan trays and three hot swappable
redundant AC power supply units (PSUs). For more information on power connections and redundant power, see
FortiGate 6000F AC power supply units (PSUs) on page 20.
The FortiGate 6000F DC models include two hot swappable -48 to -60 VDC, 50A max DC PSUs. For DC power
information, see DC PSUs and supplying DC power to a FortiGate 6000F on page 24.
The back panel also includes the FortiGate 6000F ground connector that must be connected to ground.
FortiGate 6000F Series 7.0.12 System Guide 15
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
15
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
FortiGate 6000F back panel (FortiGate 6501F AC model shown)
FortiGate 6000F series schematic
FortiGate 6000F hardware includes a data plane and a management plane. The data plane processes customer network
data. The management plane handles management functions such as administrator logins, configuration and session
synchronization, SNMP, and other monitoring, HA heartbeat communication, and remote and (if supported) local disk
logging. Separating these two planes means that resources used for data processing are not compromised by
management activities.
In the data plane, two DP3 load balancers use session-aware load balancing to distribute sessions from the front panel
interfaces (port1 to 28) to Fortinet Processor Cards (FPCs). The DP3 processors communicate with the FPCs across the
3.2Tbps integrated switch fabric. Each FPC processes sessions load balanced to it. The FPCs send outgoing sessions
back to the integrated switch fabric and then out the network interfaces to their destinations.
The NP6 processor in each FPC enhances network performance with fastpath acceleration that offloads communication
sessions from the FPC CPU. The NP6 processor can also handle some CPU intensive tasks, like IPsec VPN
encryption/decryption. The CP9 processors in each FPC accelerate many common resource intensive security related
processes such as SSL VPN, Antivirus, Application Control, and IPS.
The management plane includes the management board, base backplane, management interfaces, and HA heartbeat
interfaces. Configuration and session synchronization between FPCs in a FortiGate 6000F occurs over the base
backplane. In an HA configuration, configuration and session synchronization between the FortiGate 6000Fs in the
cluster takes place over the HA1 and HA2 interfaces. Administrator logins, SNMP monitoring, remote logging to one or
more FortiAnalyzers or syslog servers, and other management functions use the MGMT1, MGMT2, and MGMT3
interfaces. You can use the 10Gbps MGMT3 interface for additional bandwidth that might be useful for high bandwidth
activities such as remote logging.
FortiGate 6000F Series 7.0.12 System Guide 16
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
16
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
FortiGate 6000F series hardware information
This section introduces FortiGate 6000F series hardware components and accessories.
Shipping components
The FortiGate 6000F ships pre-assembled with the following components:
l The 3U FortiGate 6000F.
l The AC version of the FortiGate 6000F includes three AC Power Supply Units (PSUs) installed in the back panel.
FortiGate 6000F Series 7.0.12 System Guide 17
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
17
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
l The DC version of the FortiGate 6000F includes two DC PSUs installed in the back panel.
l The AC version of the FortiGate 6000F includes three power cords with C15 power connectors.
l The DC version of the FortiGate 6000F includes two custom DC power cables that include a two prong connector
with a release tab on one end and double hole lug plates on the other end.
l Three cooling fan trays installed in the back panel.
l One set of two sliding rails for 4-post rack mounting.
l Six rubber feet.
l One USB to RJ-45 RS-232 console cable.
l One RJ-45 Ethernet cable.
l Two FG-TRAN-SFP+SR transceivers.
Optional accessories and replacement parts
The following optional accessories can be ordered separately:
SKU Description
FG-6000F-FAN FortiGate 6000F fan tray.
SP-FG4000F-PS 2000W AC PSU when connected to high line AC power (200VAC or higher). 1500W AC if
connected to low-line AC (120VAC or below).
SP-FG4000F-DC-PS 2000W DC PSU.
FG-7040E-PS-AC 1500W AC PSU. (FortiGate 6000F Generation 1)
You can also order the following:
l Transceivers
Physical description of the FortiGate 6000F
The FortiGate 6000F is a 3U appliance that can be installed in a standard 19-inch rack. The following table describes the
physical characteristics of the FortiGate 6000F chassis.
Form factor 3RU
Dimensions (H x W x D) 5.20 x 17.20 x 26.18 in (132 x 437 x 665 mm)
Rack mount type Sliding rail
FortiGate 6300F and 6301F weight 67.68 lbs 30.7 kg
FortiGate 6500F and 6501F weight 78.26 lbs 35.5 kg
FortiGate 6001F weight 78.26 lbs 35.5 kg
Operating temperature 32 to 104°F (0 to 40°C)
Storage temperature -31 to 158°F (-35 to 70°C)
Relative humidity 20% to 90% non-condensing
FortiGate 6000F Series 7.0.12 System Guide 18
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
18
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
Average noise level 57.43 dbA
Input voltage range 100 to 240 VAC (50 to 60 Hz)
Supplied power supply units (PSUs) 3xSP-FG4000F-PS (2+1 redundancy) or
2xSP-FG4000F-DC-PS (1+1 redundancy)
Max power consumption 1568W
Average power consumption 1328W
Max current (AC) 30A@100VAC, 20A@240VAC
Heat dissipation 5350 BTU/hr
Joules/hr 5645 KJ/hr
FortiGate 6000F series hardware generations
Two generations of FortiGate 6000F series hardware are now available. Both generations support the same software
features. Generation 2 has two hardware improvements:
l The FPCs include more memory.
l When connected to high-line AC power, generation 2 FortiGate 6000F series models provide 1+1 PSU redundancy.
When connected to high-line AC power, each PSU provides 2000W, which is enough power to run the entire system
including all FPCs.
For more information on FortiGate 6000F series generation 1 and generation 2, including supported firmware versions
and how to determine the generation of your FortiGate 6000F series hardware, see the Fortinet Community article:
Technical Tip: Information on FortiGate 6000F series Gen1 and Gen2.
For more information on generation 1 and generation 2 AC PSUs, see FortiGate 6000F AC power supply units (PSUs)
on page 20.
The FortiGate 6001F is a generation 2 appliance.
Cooling fan trays
The FortiGate 6000F contains three hot swappable cooling fan trays installed in the back of the appliance. When the fan
LED is green the fan tray is operating normally. If a fan tray LED turns red or goes off the fan tray should be replaced.
FortiGate 6000F Series 7.0.12 System Guide 19
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
19
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
Cooling Fan Tray
Fan trays are hot swappable. You can replace a failed fan tray while the FortiGate 6000F is operating. To replace a fan
tray, unscrew the four retention screws and use the handle to pull the fan tray out of the chassis. Install the new fan tray
by sliding it into place. As you slide the new fan into place it will power up. Tighten the retention screws.
The other fan trays will continue to operate and cool the chassis as a fan tray is being removed and replaced. However
an open fan tray slot will result in less air flow through the appliance so do not delay installing the replacement fan tray.
The FortiGate 6000F monitors the internal temperature of the appliance and adjusts the operating speed of the cooling
fans as required. When the device is first powered on all cooling fans run at full speed. Once the system is up and
running, the fan speeds are reduced to maintain an optimum temperature in the appliance.
During normal operation, all fan trays are active. If cooling requirements increase, the fan speed will increase.
FortiGate 6000F AC power supply units (PSUs)
The FortiGate 6000F back panel includes three hot swappable redundant AC PSUs (PSU1, PSU2, and PSU3). Two
generations of FortiGate 6000F models have been released. Generation 1 and generation 2 have different AC PSUs:
l Generation 2 FortiGate 6000F PSUs can be connected to high-line AC power (200VAC or higher) and each PSU
provides 2000W AC. A generation 2 FortiGate 6000F with two high line power feeds connected to PSU1 and PSU2
is a fully 1+1 redundant solution because a single PSU can fully power a FortiGate 6000F.
l Generation 1 FortiGate 6000F PSUs can be connected to low line AC power (120VAC or below) and each PSU
provides 1500W AC. Requires at least 2 PSUs to be connected to power. Connecting a third PSU provides 2+1
redundancy. If only one PSU is operating, some FPCs will be shut down and performance will be reduced.
l You can also connect generation 2 FortiGate 6000F PSUs to low-line AC power (120VAC or below) and each PSU
provides 1500W AC. Requires at least 2 PSUs to be connected to power. Connecting a third PSU provides 2+1
redundancy. If only one PSU is operating, some FPCs will be shut down and performance will be reduced.
Use a supplied C15 power cable to connect power to each PSU C16 power connector. C15/C16 power connectors are
used for high temperature environments and are rated up to 120°C.
FortiGate 6000F Series 7.0.12 System Guide 20
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
20
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
For more information on FortiGate 6000F generation 1 and generation 2, including supported
firmware versions and how to determine the generation of your FortiGate 6000F hardware,
see the Fortinet Knowledge base article: Technical Tip: Information on FortiGate 6000F series
Gen1 and Gen2.
Generation 1 AC PSU showing C16 power connector
Generation 2 AC PSU showing C16 power connector
Individual AC PSUs do not have to be connected to ground. Instead you can use the
information in Connecting the FortiGate 6000F to ground on page 27 to connect the FortiGate
6000F to ground.
Connecting generation 2 FortiGate 6000F PSUs to high line AC power
If you connect a generation 2 FortiGate 6000F to high-line AC power, each PSU provides 2000W AC, which is all the
power required by the FortiGate 6000F. Only two PSUs (PSU1 and PSU2) each connected to separate power feeds, are
FortiGate 6000F Series 7.0.12 System Guide 21
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
21
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
required for full 1+1 power redundancy. PSU3 may also be connected if you have three separate power feeds and
provides 1+1+1 redundancy. To maintain redundancy, you should replace any failed PSUs.
See FortiGate 6000F series back panel on page 15 for locations of the PSUs.
Recommended fully redundant configuration when connected to high-line AC power:
l Two FortiGate 6000Fs in a High Availability (HA) configuration connected to two power feeds.
l On both FortiGate 6000Fs, connect PSU1 and PSU2 to different power feeds.
Connecting generation 1 or 2 FortiGate 6000F PSUs to low line AC power
If you connect a generation 1 FortiGate 6000F or a generation 2 FortiGate 6000F PSU to low line AC power, each PSU
provides 1500W AC and at least two PSUs (PSU1 and PSU2) must be connected to power. PSU3 is a backup PSU and
provides 2+1 redundancy. All PSUs should be connected to AC power.
See FortiGate 6000F series back panel on page 15 for locations of the PSUs.
Recommended FortiGate 6000F low line AC power fully redundant configuration:
l Two FortiGate 6000Fs (Unit 1 and Unit 2) in a High Availability (HA) configuration with two power feeds (Feed A and
Feed B).
l Connect PSU1 and PSU2 of Unit 1 to Feed A. Connect PSU3 of Unit 1 to Feed B.
l Connect PSU1 and PSU2 of Unit 2 to Feed B. Connect PSU3 of Unit 2 to Feed A.
For normal operation of a FortiGate 6000F connected to low line AC power, at least 2 PSUs must be operating and
connected to power. If two PSUs fail and only one PSU is operating, the FortiGate 6000F will continue to operate but
only four FPCs will be running, the remaining FPCs are shut down. This means the performance of the FortiGate 6000F
is reduced until at least two PSUs are connected.
If only one PSU is operating, the FortiGate 6000F shuts down the FPCs starting with the FPC
with the highest slot number, until only four FPCs are running. Usually this results in the FPCs
in slots 1 to 4 running if there is only one PSU connected.
If one of the FPCs in slot 1 to 4 has previously shut down, the FortiGate 6000F keeps the four
operational FPCs in the lowest slot numbers running. For example, if the FPC in slot 2 has
previously shut down, if only one PSU is operating, the FPCs in slots 1, 3, 4, and 5 continue
running.
The FortiGate 6000F also keeps the primary FPC running. Usually the FPC in slot 1 is the
primary FPC, so if only one PSU is operating, the FPCs in slots 1 to 4 continue running.
However, if the FPC in another slot has become the primary FPC, then this FPC as well as the
three remaining FPCs with the lowest slot numbers will continue running. For example, if the
FPC in slot 6 has become the primary FPC, then when only one PSU is operating, the FPCs in
slots 1, 2, 3, and 6 continue running.
AC PSU LED states
The PSU LED indicates whether the PSU is operating correctly and connected to power.
FortiGate 6000F Series 7.0.12 System Guide 22
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
22
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
State Description
Off AC power not connected. If this LED is not lit, check to make sure the PSU is
connected to a power feed. If the power feed is good then the PSU has failed and
should be replaced.
Flashing green The PSU is in standby mode, not supplying power to the chassis.
Green Normal Operation with AC power connected.
Amber Fault condition (PSU shuts down). This can occur if power input or output is out of
the normal operating range, temperature is out of the normal range, or one or
more fans are not operating. This may be caused by a problem with the PSU. This
could also be caused by conditions external to the PSU, for example, if there is a
problem with the power supplied to the PSU or if the PSU has gotten too hot
because of insufficient ventilation.
Flashing amber Warning that power input or output, temperature, or fan operation is close to being
outside of the normal operating range. This may be caused by a problem with the
PSU. This could also be caused by conditions external to the PSU, for example, if
there is a problem with the power supplied to the PSU or if the PSU has gotten too
hot because of insufficient ventilation.
Connecting FortiGate 6000F PSUs to AC power
Use the following steps to connect a FortiGate 6000F PSU to AC power after connecting the chassis to ground.
1. Use the supplied C15 Power cables to connect each PSU C16 power connector to a separate surge protected
power supply.
You can install power cord clamps into the back of the chassis beside each PSU. Install the clamps by inserting
them into the holes adjacent each supply at the back of the chassis. Use the clamps to secure the AC power cords
so they are not accidentally disconnected.
2. As the FortiGate 6000F powers up, the status LED flashes green.
Once the FortiGate 6000F has started up and is operating correctly, the front and back panel LEDs should indicate
normal operation (see Confirming startup status on page 38).
Individual AC PSUs do not have to be connected to ground. Instead you can use the
information in Connecting the FortiGate 6000F to ground on page 27 to connect the
FortiGate 6000F to ground.
Hot swapping an AC PSU
Follow these steps to safely hot swap an AC PSU.
You can hot swap a PSU without affecting performance or interrupting traffic as long as one
PSU remains connected to power at all times.
FortiGate 6000F Series 7.0.12 System Guide 23
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
23
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
1. Attach an ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Turn off the power being supplied to the PSU and disconnect the power cord.
3. Press the latch towards the handle until the PSU is detached then pull it out of the FortiGate 6000F.
4. Insert a replacement PSU into the FortiGate 6000F and slide it in until it locks into place.
5. Use a supplied C15 power cable to connect power to the PSU C16 power connector.
6. Turn on power to the PSU.
7. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
DC PSUs and supplying DC power to a FortiGate 6000F
The DC version of the FortiGate 6000F includes two hot swappable -48 to -60 VDC, 50A max DC PSUs. Each PSU has
an internal 60A/170VDC fast blow fuse on the DC line input.
Only one PSU must be connected to power. The second PSU is a backup PSU that provides 1+1 redundancy. See
FortiGate 6000F series back panel on page 15 for locations of the PSUs. The diagram shows three AC PSUs, the DC
version replaces the AC PSUs with two DC PSUs in slots PSU1 and PSU2. PSU3 is covered by a metal panel.
Recommended fully redundant configuration:
l Two FortiGate 6000Fs in a High Availability (HA) configuration with two power feeds (A and B). FortiGate 6000F
supports HA with two and only two FortiGate 6000Fs.
l On both FortiGate 6000Fs, connect each PSU to a different power feed.
For normal operation of a single FortiGate 6000F, only one DC PSU must be operating and connected to power. If only
one DC PSU is operating, all components and all FPCs continue to operate normally. However, to maintain redundancy,
you should replace a failed DC PSU.
Each DC PSU is designed to be installed in a Telecom data center or similar location that has available -48VDC power
fed from a listed 50A circuit breaker. To improve redundancy you can connect each PSU to a separate power circuit.
DC PSU
Individual DC PSUs do not have to be connected to ground. Instead you can use the
information in Connecting the FortiGate 6000F to ground on page 27 to connect the FortiGate
6000F to ground.
FortiGate 6000F Series 7.0.12 System Guide 24
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
24
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
Fortinet supplies custom DC power cables that connect to the two-prong power connector on each DC PSU. The
connector clicks into a release tab that secures the cable into place. DC terminal rings on the supplied cable must be
securely and safely fastened to the your data center power supply terminals. The supplied DC power cables are
intended to be used only for in-rack wiring, must be routed away from sharp edges, and must be adequately fixed to
prevent excessive strain on the wires and terminals.
DC PSU Power ratings
Max Inrush Current 50A
Max Inrush Current Duration 200ms
Normal Input Voltage -48VDC to -60VDC
Maximum Input Voltage -40.8VDC to -72VDC
Input Current Average: 12.5A@48V for each PSU, Max: 50A
DC PSU LED States
State Description
Off DC power not connected.
Flashing green The PSU is in standby mode, not supplying power to the chassis.
Green Normal operation with DC power connected.
Amber Fault condition (PSU shuts down). This can occur if power input or output is out of
the normal operating range, temperature is out of the normal range, or one or
more fans are not operating. This may be caused by a problem with the PSU. This
could also be caused by conditions external to the PSU, for example, if there is a
problem with the power supplied to the PSU or if the PSU has gotten too hot
because of insufficient ventilation.
Flashing amber Warning that power input or output, temperature, or fan operation is close to being
outside of the normal operating range. This may be caused by a problem with the
PSU. This could also be caused by conditions external to the PSU, for example, if
there is a problem with the power supplied to the PSU or if the PSU has gotten too
hot because of insufficient ventilation.
Crimping guidelines
The DC power cord is a two prong connector with a release tab on one end and double hole lug plates on the other end.
The DC power source must have a 1/4" (0.64cm) stud to secure the lugs . The distance between the studs should be 5/8"
(1.59cm). The DC power source terminals should allow at least support 50A. If the DC power source does not meet
these requirements the cord must be cut and re-crimped to match the DC terminals.
Do not crimp energized wires.
FortiGate 6000F Series 7.0.12 System Guide 25
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
25
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
Follow these crimping guidelines:
l Strip the insulation from cable. Be careful not to nick cable strands which may later result in stands breaking.
l Cable end should be clean: wire brush or clean with emery cloth if necessary. Insert cable into connector until it
stops. The insertion length must approximate the stripped length of cable.
l Insert connector in die and compress between the markings beginning near the tongue of the connector. Using the
wrong installing die may result in a defective connection.
l After crimping, remove all sharp edges, flash, or burrs.
Connecting a FortiGate 6000F DC PSU to DC power
The following procedure describes how to connect a FortiGate 6000F DC PSU to DC power. Repeat this procedure to
connect each PSU.
You need the following equipment to connect the FortiGate 6000F DC PSUs to DC power:
l An electrostatic discharge (ESD) preventive wrist strap with connection cord.
l One of the supplied DC power cables, that include a two prong connector with a release tab on one end and black
and red double hole lug plates on the other end. Black for -48V and red for RTN.
Individual DC PSUs do not have to be connected to ground. Instead you can use the
information in Connecting the FortiGate 6000F to ground on page 27 to connect the FortiGate
6000F to ground.
To connect a DC PSU to DC power
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Make sure that the PSU and power cords are not energized.
3. Connect the black -48V power wire to your -48V DC power source using the ring terminal.
4. Connect the red RTN power wire from to your RTN connector using the ring terminal.
5. Plug the power cable into the FortiGate 6000F PSU connector.
Slide the connector in until the release tab clicks, locking the cable in place.
6. Make sure the power wires are secured using tie wraps if required.
7. If required, label the black wire -48V.
8. If required, label the red wire RTN.
9. Turn on power to the PSU.
10. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
FortiGate 6000F Series 7.0.12 System Guide 26
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
26
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
Hot Swapping a DC PSU
Follow these steps to safely hot swap a DC PSU.
You can hot swap a PSU without powering down the FortiGate 6000F as long as one PSU
continues to be connected to power and operating normally.
1. Attach an ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the chassis or frame.
2. Turn off the power being supplied to the DC PSU to be hot swapped.
3. Disconnect the power cable from the FortiGate 6000F DC PSU by pressing the release tab and unplugging the
cable.
4. To remove the PSU, press the latch towards the handle until the PSU is detached then pull it out of the chassis.
5. Insert a replacement PSU into the chassis and slide it in until it locks into place.
6. Plug power cord into the FortiGate 6000F PSU connector.
Slide the connector in until the release tab clicks, locking the cable in place.
7. Turn on power to the PSU.
8. Verify that the PSU status LED is solid green meaning that the PSU is powered up and operating normally.
Connecting the FortiGate 6000F to ground
The FortiGate 6000F appliance includes a ground terminal on the FortiGate 6000F back panel. The ground terminal
provides two connectors to be used with a double-holed lug such as Thomas & Betts PN 54850BE. This connector must
be connected to a local ground connection.
You need the following equipment to connect the FortiGate 6000F to ground:
l An electrostatic discharge (ESD) preventive wrist strap with connection cord.
l One green 6 AWG stranded wire with listed closed loop double-hole lug suitable for minimum 6 AWG copper wire,
such as Thomas & Betts PN 54850BE.
To connect the FortiGate 6000F chassis to ground
1. Attach the ESD wrist strap to your wrist and to an ESD socket or to a bare metal surface on the FortiGate 6000F.
2. Make sure that the FortiGate 6000F and ground wire are not energized.
3. Connect the green ground wire from the local ground to the ground connector on the FortiGate 6000F.
FortiGate 6000F Series 7.0.12 System Guide 27
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
27
|
FortiGate 6000F series hardware description Fortinet Technologies Inc.
4. Secure the ground wire to the FortiGate 6000F.
5. Optionally label the wire GND.
FortiGate 6000F Series 7.0.12 System Guide 28
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
28
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
FortiGate 6000F hardware assembly and rack mounting
The FortiGate 6000F appliance can be mounted in a standard 19-inch rack and requires 3U of vertical space in the rack.
The FortiGate 6000F can also be surface mounted.
Cautions and warnings
FortiGate 6000Fs must be protected from static discharge and physical shock. Only handle or work with FortiGate
6000Fs at a static-free workstation. Always wear a grounded electrostatic discharge (ESD) preventive wrist strap when
handling FortiGate 6000Fs.
If you install the FortiGate 6000F appliance in a closed or multi-unit rack assembly, the operating ambient temperature of
the rack environment may be greater than room ambient temperature. Make sure the operating ambient temperature
does not exceed the manufacturer's maximum rated ambient temperature.
To avoid personal injury or damage to the FortiGate 6000F appliance, it is recommended that two or more people install
the FortiGate 6000F into the rack.
Do not place heavy objects on the appliance.
Ensure there is enough room around the appliance to allow for sufficient air flow.
Cooling air flow and required minimum air flow clearance
When installing the FortiGate 6000F, make sure there is enough clearance for effective cooling air flow. The following
diagram shows the cooling air flow through the FortiGate 6000F and the location of fan trays. Make sure the cooling air
intake and warm air exhaust openings are not blocked by cables or rack construction because this could result in cooling
performance reduction and possible overheating and component damage.
FortiGate 6000F cooling air flow and minimum air flow clearance (appliance side view)
All cool air enters the appliance through the front panel and all warm air exhausts out the back. For optimal cooling allow
100 mm of clearance at the front and back of the chassis. This results in a total footprint of 850 mm from front to back.
Side clearance is not required.
FortiGate 6000F Series 7.0.12 System Guide 29
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
29
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
FortiGate 6000F four post rack-mount installation
This section describes how to use the sliding rails included with your FortiGate 6000F package to install the FortiGate
6000F in a 4-post rack.
The FortiGate 6000F is shipped with a left and a right rail assembly. Each rail assembly includes an inner rail, a middle
rail, and an outer rail. The inner rail attaches to the side of the FortiGate 6000F. The middle rail remains attached to the
outer rail which attaches to the rack. The middle rail is used to guide the inner rail into the outer rail.
Sliding rails
When mounted on the rails and fully slid into the rack, the FortiGate 6000F locks into place. You can press the system
release buttons that project out of the front of the rack to unlock the rails and slide the FortiGate 6000F out.
No tools are required to install the rails and the FortiGate 6000F. Once the FortiGate 6000F is slid into the rack you can
use a screw driver to install four rack screws to secure the FortiGate 6000F in the rack.
Installation steps
There are three steps to use the sliding rails to install the FortiGate 6000F in a four-post the rack:
1. Attach the right and left inner rails to the right and left sides of the FortiGate 6000F.
2. Attach the right and left outer rails to the right and left rack posts.
3. Slide the FortiGate 6000F into the rack.
As a supplement to the instructions below, you can view the following video:
https://video.fortinet.com/latest/rack-mount-sliding-rail-installation
FortiGate 6000F Series 7.0.12 System Guide 30
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
30
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
Tabs, holes, and clips on the right inner rail
Attaching the inner rails to the FortiGate 6000F
Use the following steps to install the right inner rail and then repeat them for the left inner rail.
1. Remove the FortiGate 6000F from its packaging and place it on a flat surface.
For example, on a lifting device in front of the rack that it will be installed into.
2. Remove the right rail assembly from the packaging, and begin sliding the right inner rail out of it.
3. Unlock the right inner rail release tab to release the inner rail and slide it completely out of its rail assembly.
4. Locate the four rail hooks on the right side of the FortiGate 6000F and the corresponding holes on the inner rail.
5. Align the holes with the hooks and press the hooks into the holes to attach the right inner rail to the right side of the
FortiGate 6000F.
FortiGate 6000F Series 7.0.12 System Guide 31
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
31
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
6. Slide the inner rail towards the front of the FortiGate 6000F until the inner rail metal clip clicks, locking the rail onto
the side of the FortiGate 6000F.
7. Repeat these steps to attach the left inner rail to the left side of the FortiGate 6000F.
Attaching the outer rails to the rack
The ends of outer rails wrap around the inside edge of the rack posts and the mounting pins click into place.
1. Align the front of right outer rail with the right front post of the rack.
2. Push the front mounting pins into the rack post holes.
3. Pull the securing plate over the rack post and close it to lock the pins in place.
4. Pull out the bracket on the back of the right outer rail to adjust its position until it matches up with the back post of the
rack.
5. Verify that the rail is level, then push the rear mounting pins into the rack post holes.
6. Repeat these steps for the left outer rail. Make sure it is installed at the same height as the right outer rail.
Sliding the FortiGate 6000F into the rack
Now that the inner and outer rails are attached, you can slide the FortiGate 6000F into the rack by matching the inner
rails with the outer rails.
1. Verify that the inner rail holes are properly connected to the FortiGate 6000F hooks and locked into place.
2. Verify that the outer rails are level, both at the same height, and securely attached to the rack.
3. Pull the middle rails out from the front of the outer rails until they lock into place.
FortiGate 6000F Series 7.0.12 System Guide 32
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
32
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
4. Use a lifting device to raise the FortiGate 6000F to allow you to align the inner rails with the middle rails.
5. Slide the inner rails into the middle rails until the lock out tabs on the inner rails click into the front of the middle rails.
Keep the rails aligned and apply even pressure to both sides of the FortiGate 6000F while doing this.
6. Slide the release tabs forward on both inner rails at the same time.
7. Push the FortiGate 6000F all the way into the rack until the system release buttons click into the locked position on
the front of the rack.
8. Use a screw driver to install four rack screws into the handle brackets on the front of the FortiGate 6000F to secure it
in the rack.
FortiGate 6000F Series 7.0.12 System Guide 33
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
33
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
Removing the FortiGate 6000F from a four-post rack
Make sure that a lifting device is available to slide the FortiGate 6000F on to when removing it from the rack. You will
need a screwdriver to remove the four rack screws.
The rack must be stable before sliding the FortiGate 6000F out. Failure to stabilize the rack
may cause it to tip over.
Do not pick up the FortiGate 6000F by the front handles. They are designed to pull the
FortiGate 6000F from the rack on the rails.
1. Power down the FortiGate 6000F and remove all cables connected to it.
2. Remove the four rack screws to allow the FortiGate 6000F to slide out of the rack.
3. Squeeze the system release buttons on the front of both inner rails at the same time to release the FortiGate 6000F.
4. Use the front handles to pull the FortiGate 6000F out of the rack until the rails lock in their fully extended position.
5. Raise the lifting device under the FortiGate 6000F.
6. Slide the system lock out tabs forward on both inner rails, and slowly slide the FortiGate 6000F away from the rack
and onto the lifting device.
Apply even pressure to both sides of the FortiGate 6000F while doing this. As you slide the FortiGate 6000F out, the
inner rails will slide out of the middle rails.
FortiGate 6000F Series 7.0.12 System Guide 34
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
34
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
7. Push the middle rail latch counter clockwise, and slide the middle rails back into the outer rails.
8. Push the metal clip on each inner rail toward the front of the FortiGate 6000F to release the inner rails from the
hooks on the side of the FortiGate 6000F and remove the inner rails.
Surface-mount installation
1. Make sure that the surface onto which the FortiGate 6000F is to be installed is clean, level, and stable and that there
is at least 100 mm of front and back clearance to allow for adequate cooling air flow.
2. Attach the six provided rubber feet to the bottom of the FortiGate 6000F.
3. Place the FortiGate 6000F in the designated location.
4. Verify that the spacing around the FortiGate 6000F conforms to requirements and that the FortiGate 6000F is level.
Installing QSFP28, SFP28, SFP+, and SFP transceivers
You must install QSFP28 or QSFP+ transceivers into the 25 to 28 interfaces before connecting them to 100Gbps or
40Gbps networks.
You must install SFP28, SFP+, or SPF transceivers into the 1 to 24 interfaces before connecting them to 25Gbps,
10Gbps. or Gigabit networks.
You may need to manually change interface speeds as described in Interface groups and
changing data interface speeds on page 10.
You must install the following types of SFP+ or SFP transceivers into the MGMT3, HA1, and HA2 interfaces before
connecting them to 10Gbps or Gigabit networks.
l 10GBASE-SR SFP+ (10Gbps)
l 10GBASE-LR SFP+ (10Gbps)
l 1000BASE SFP (1Gbps)
The HA1 and HA2 interfaces are used for heartbeat, session sync, and management
communication between two and only two FortiGate 6000Fs in HA mode. This communication
requires SFP+ 10 Gbps connections. Using to SFP 1 Gbps connections is not recommended.
FortiGate 6000F Series 7.0.12 System Guide 35
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
35
|
FortiGate 6000F hardware assembly and rack mounting Fortinet Technologies Inc.
To install transceivers
To complete this procedure, you need:
l A FortiGate 6000F
l Transceivers to install
l An electrostatic discharge (ESD) preventive wrist strap with connection cord
FortiGate 6000Fs must be protected from static discharge and physical shock. Only handle or
work with FortiGate 6000Fs at a static-free workstation. Always wear a grounded electrostatic
discharge (ESD) preventive wrist strap when handling FortiGate 6000Fs.
Handling the transceivers by holding the release latch can damage the connector. Do not force
transceivers into their cage slots. If the transceiver does not easily slide in and click into place,
it may not be aligned correctly. If this happens, remove the transceiver, realign it and slide it in
again.
1. Attach the ESD wrist strap to your wrist and to an available ESD socket or wrist strap terminal.
2. Remove the caps from the cage sockets on the FortiGate 6000F front panel.
3. Hold the sides of the transceiver and slide it into the cage socket until it clicks into place.
FortiGate 6000F Series 7.0.12 System Guide 36
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
36
|
Getting started with FortiGate 6000F series
This section is a quick start guide to connecting and configuring a FortiGate 6000F for your network.
Before using this chapter, your FortiGate 6000F should be mounted and connected to your grounding and power
system. In addition, your FortiGate 6000F should be powered up and the front and back panel LEDs should indicate
normal operation.
When your FortiGate 6000F is operating normally, the front panel LEDs should appear as follows.
LED State
Status Green
Alarm Off
HA Off
Power Green
Connected network interfaces Solid or flashing green.
During normal operation, the back panel PSU and fan try LEDs should all be solid green. This indicates that each
component has power and is operating normally.
Once the system has initialized, you have a few options for connecting to the FortiGate 6000F GUI or CLI:
l Log in to the management board GUI by connecting MGMT1 or MGMT2 to your network and browsing to
https://192.168.1.99 or https://192.168.2.99.
l Log in to the management board CLI by connecting MGMT1 or MGMT2 to your network and using an SSH client to
connect to 192.168.1.99 or 182.168.2.99.
l Log in to the management board CLI by connecting to the RJ-45 RS-232 CONSOLE port with settings:
BPS: 9600, data bits: 8, parity: none, stop bits: 1, flow control: none.
The FortiGate 6000F ships with the following factory default configuration.
Option Default Configuration
Administrator Account User
Name
admin
Password (none) For security reasons you should add a password to the admin
account before connecting the FortiGate 6000F to your network.
From the GUI, access the Global GUI and go to System >
Administrators, edit the admin account, and select Change Password.
From the CLI:
config global
config system admin
edit admin
set password <new-password>
end
FortiGate 6000F Series 7.0.12 System Guide 37
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
37
|
Getting started with FortiGate 6000F series Fortinet Technologies Inc.
Option Default Configuration
MGMT1 IP/Netmask 192.168.1.99/24
MGMT2 IP/Netmask 192.168.2.99/24
All configuration changes must be made from the management board GUI or CLI and not from individual FPCs.
All other management communication (for example, SNMP queries, remote logging, and so on) use the MGMT1 or
MGMT2 interfaces and are handled by the management board.
Confirming startup status
Before verifying normal operation and making configuration changes and so on you should wait until the FortiGate
6000F is completely started up and synchronized. This can take a few minutes.
To confirm that theFortiGate 6000F is synchronized, you can refer to the Cluster Status dashboard widget. If the system
is synchronized, the management board (slot 0) all of the FPCs (slots 1 to 6 or 1 to 10) should be visible and their
Configuration Status should be In Sync. The Cluster Status dashboard widget also indicates if any FPCs are not
synchronized.
The FortiGate 6000F uses the Fortinet Security Fabric for communication and synchronization
between the management board and the FPCs and for normal GUI operation. By default, the
Security Fabric is enabled and must remain enabled for normal operation.
You can also view the Sensor Information dashboard widget to confirm that the system temperatures are normal and
that all power supplies and fans are operating normally.
From the CLI you can use the diagnose sys confsync status | grep in_sy command to view the
synchronization status of the management board and FPCs. If all of the FPCs are synchronized, each output line should
include in_sync=1. If a line ends with in_sync=0, that FPC is not synchronized. The following example just shows a
few output lines:
diagnose sys confsync status | grep in_sy
FPC6KF3E17900200, Secondary, uptime=5385.45, priority=119, slot_id=2:1, idx=2, flag=0x4, in_sync=1
F6KF313E17900031, Secondary, uptime=5484.74, priority=2, slot_id=1:0, idx=0, flag=0x10, in_sync=1
F6KF313E17900032, Primary, uptime=5488.57, priority=1, slot_id=2:0, idx=1, flag=0x10, in_sync=1
FPC6KF3E17900201, Secondary, uptime=5388.78, priority=120, slot_id=2:2, idx=2, flag=0x4, in_sync=1
F6KF313E17900031, Secondary, uptime=5484.74, priority=2, slot_id=1:0, idx=0, flag=0x10, in_sync=1
...
FortiGate 6000F Series 7.0.12 System Guide 38
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
38
|
Getting started with FortiGate 6000F series Fortinet Technologies Inc.
Default VDOM configuration and configuring the management
interfaces
By default, when you first start up a FortiGate 6000F it is operating in Multi VDOM mode. The default Multi VDOM
configuration includes the root VDOM and a management VDOM named mgmt-vdom. The mgmt1, mgmt2, mgmt3,
ha1, and ha2 interfaces are in mgmt-vdom and all of the data interfaces are in the root VDOM.
You cannot delete or rename mgmt-vdom. You also cannot remove interfaces from it or add interfaces to it. You can
however, configure other settings such as routing required for management communication, interface IP addresses, and
so on. You can also add VLANs to the interfaces in mgmt-vdom and create a LAG that includes the mgmt1 and mgmt2
interfaces.
You can use the root VDOM for data traffic and you can also add more VDOMs for data traffic as required, depending on
your Multi VDOM license.
Changing data interface network settings
To change the IP address of any FortiGate 6000F data interface:
l From the GUI access the Global GUI and go to Network > Interfaces. Edit any interface to change its IP address
and other settings.
l From the CLI:
config system interface
edit <interface-name>
set ip <ip-address> <netmask>
end
Resetting to factory defaults
At any time during the configuration process, if you run into problems, you can reset the FortiGate 6000F to factory
defaults and start over. From the management board CLI enter:
config global
execute factoryreset
Restarting the FortiGate 6000F
To restart the FortiGate 6000F, connect to the management board CLI and enter the execute reboot command. After
you enter this command, the management board and all of the FPCs restart.
To restart an individual FPC, log in to the CLI of that FPC and run the execute reboot command.
FortiGate 6000F Series 7.0.12 System Guide 39
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
39
|
Getting started with FortiGate 6000F series Fortinet Technologies Inc.
Changing the FortiGate 6001F, FortiGate 6501F, or FortiGate 6301F
log disk and RAID configuration
The FortiGate 6001F, FortiGate 6501F, or FortiGate 6301F include two internal 1-TByte log disks. By default the disks
are in a RAID-1 configuration. In the RAID-1 configuration you can use the disks for disk logging only. You can use the
execute disk raid command to disable RAID and use one of the disks for disk logging and the other for other
purposes such as disk caching. You can also change the RAID level to RAID-0. Changing the RAID configuration
deletes all data from the disks and can disrupt disk logging so a best practice is set the RAID configuration when initially
setting up the FortiGate 6001F, FortiGate 6501F, or FortiGate 6301F.
From the CLI you can use the following command to show disk status:
execute disk list
Use the following command to disable RAID:
execute disk raid disable
RAID is disabled, the disks are separated and formatted.
Use the following command to change the RAID level to RAID-0:
execute disk raid rebuild-level 0
The disks are formatted for RAID-0.
Use the following command to rebuild the current RAID partition:
execute disk raid rebuild
The RAID is rebuilt at the current RAID level.
Use the following command to show RAID status. The following command output shows the disks configured for RAID-1.
execute disk raid status
RAID Level: Raid-1
RAID Status: OK
RAID Size: 1000GB
Disk 1: OK Used 953GB
Disk 2: OK Used 953GB
FortiGate 6000F Series 7.0.12 System Guide 40
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
40
|
Managing individual FortiGate 6000F management boards
and FPCs
You can manage individual FPCs using special management port numbers, FPC consoles, or the execute loadbalance slot manage command. You can also use the execute ha manage command to log in to the other
FortiGate 6000F in an HA configuration.
Special management port numbers
You may want to connect to individual FPCs to view status information or perform a maintenance task, such as installing
firmware or performing a restart. You can connect to the GUI or CLI of individual FPCs (or the management board) using
the MGMT1 interface IP address with a special port number.
You can use the config load-balance setting slbc-mgmt-intf command to
change the management interface used. The default is mgmt1 and it can be changed to
mgmt2, or mgmt3.
To enable using the special management port numbers to connect to individual FPCs, set
slbc-mgmt-intf to an interface that is connected to a network, has a valid IP address, and
has management or administrative access enabled. To block access to the special
management port numbers you can set slbc-mgmt-intf to an interface that is not
connected to a network, does not have a valid IP address, or has management or
administrative access disabled.
For example, if the MGMT1 interface IP address is 192.168.1.99 you can connect to the GUI of the first FPC (the FPC in
slot 1) by browsing to :
https://192.168.1.99:44301
The special port number (in this case, 44301) is a combination of the service port (for HTTPS, the service port is 443)
and the FPC slot number (in this example, 01).
You can view the special HTTPS management port number for and log in to the GUI of an FPC from the Configuration
Sync Monitor.
The following table lists the special ports you can use to connect to individual FPCs or the management board using
common management protocols. The FortiGate 6300F and 6301F have 7 slots (0 to 6) and the FortiGate 6500F , 6501F,
and 6001F have 11 slots (0 to 10). Slot 0 is the management board (MBD) slot. Slots 1 to 10 are FPC slots.
You can't change the special management port numbers. Changing configurable
management port numbers, for example the HTTPS management port number (which you
might change to support SSL VPN), does not affect the special management port numbers.
FortiGate 6000F Series 7.0.12 System Guide 41
Fortinet Technologies Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/ffef9904-1a11-11e9-9685-f8bc1258b856/fortigate-6000F-system-guide.pdf
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.