FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
pginete
Staff
Staff
Article Id 422244
Description

This article describes how to fix the 40G interfaces of FortiGate-1800F/1801F are down after the firmware upgrade to v7.2.8.

Scope FortiGate
Solution

Verify the current firmware version using the following command in the CLI.

 

Lab_FW1 # get system status
Version: FortiGate-1800F v7.2.8,build1639,240313 (GA.M)

 

Verify the speed configured on the interface(s) in the following example port37.

 

Lab_FW1 # show system interface port37   
edit "port37"
set vdom "root"
set type physical
set mediatype sr4
set monitor-bandwidth enable
set snmp-index 41
set speed 40000full      
next
end

 

Verify the current speed negotiated on the interface(s) in this example port37 using the following command.


Lab_FW1 # diagnose hardware deviceinfo nic port37
Description :FortiASIC NP7 Adapter
Driver Name :FortiASIC Unified NPU Driver
pid :37
oid :164
vid :38
macid :36
eif_id :127
promiscous :1
local_port :0
vlan_wa_done :0
mtu :1500
netdev oid :164
dev-flags :1983
dev-promis :1
Current_HWaddr 00:09:0f:09:00:29
Permanent_HWaddr 04:d5:90:c7:e2:04
==== Default Link Settings =====
auto-nego :Disable
s_speed :100000
s_duplex :Full
==== Current Link Settings =====
auto-nego :Disable
s_status :Up
s_speed :100000
s_duplex :Full
FEC :CL91 (0x3)
FEC_cap :OFF,CL91,CL74 (0x1c)
SerDes_if :SR4
SerDes_if_cap :SR4,LR4,CR4 (0xe00)
SerDes_dflt :9
pm_mode_setting :4
pm_mode :0x18
pm_mode_dflt :4
pm_port :Yes
medium_mode :0
==== Link Status ===============
Admin :Up
link_status :Down
Speed :N/A
Duplex :N/A
==== Netdev Status =============
dev_running :Yes
dev_carrier :Off
==== Host Counters =============
hrx_pkts :0
hrx_bytes :0
htx_pkts :0
htx_bytes :0
htx_drop :0
htx_e_busy :0
htx_e_noheadroom:0
htx_e_oid :0
htx_e_adapter :0
htx_e_pad :0
htx_e_frag :0
htx_e_other :0
==== Netdev Counters ===========
Rx Pkts :0
Rx Bytes :0
Tx Pkts :0
Tx Bytes :0
==== Switch Poll Counters ======
sw_tx_pkts :0
sw_tx_bytes :0
sw_tx_bc_pkts :0
sw_tx_mc_pkts :0
sw_rx_pkts :0
sw_rx_bytes :0
sw_rx_bc_bytes :0
sw_rx_mc_bytes :0
==== Switch Error Counters =====
rx_err :0
rx_crc_err :0
rx_len_err :0
rx_carrier_err :0
rx_over_err :0
rx_under_err :0
rx_drop_pkts :0
tx_collision_err:0
tx_drop_pkts :0
======Queue Counters ===========
uc_que0_pkts :0
uc_que1_pkts :0
uc_que2_pkts :0
uc_que3_pkts :0
uc_que4_pkts :0
uc_que5_pkts :0
uc_que6_pkts :0
uc_que7_pkts :0
--------------------------------
uc_drop_que0_pkts:0
uc_drop_que1_pkts:0
uc_drop_que2_pkts:0
uc_drop_que3_pkts:0
uc_drop_que4_pkts:0
uc_drop_que5_pkts:0
uc_drop_que6_pkts:0
uc_drop_que7_pkts:0
==== Transceiver Info ==========
tx_disable : N/A
rx_los : N/A
tx_fault : N/A
present : N/A
last_spd : 0

 

The issue is due to 40G interfaces (port37-port40) default speed being changed to 100G, even though the configured speed is 40G full.

 

The workaround is to change the speed of 40G interfaces to 100G and change it back to 40G. This is a known issue tracked under ID 1014624, which was resolved in v7.2.9.

 

This issue is not present in v7.4.