FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
bksol92
Staff
Staff
Article Id 407135
Description This article indicates the logs to check when network interfaces become undetectable on FortiManagers and FortiAnalyzers.
Scope FortiManager/FortiAnalyzer.
Solution

There are cases where certain network interfaces on physical FortiManagers and FortiAnalyzers are no longer detectable during kernel initialization. To determine if it is due to hardware failure, the device's kernel logs can be used as a reference to determine the failure.

 

In this example, a FortiManager-200F is no longer able to detect ports 1 and 2:

 

diagnose debug klog

<6>[ 6.012909] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
<6>[ 6.012909] e1000: Copyright (c) 1999-2006 Intel Corporation.
<6>[ 6.012916] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
<6>[ 6.012916] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
<6>[ 6.012922] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
<6>[ 6.012923] igb: Copyright (c) 2007-2014 Intel Corporation.
<6>[ 6.012935] pci 0000:00:1c.4: PCI->APIC IRQ transform: INT A -> IRQ 16
<6>[ 6.012943] igb 0000:14:00.0: PCI->APIC IRQ transform: INT A -> IRQ 16
<4>[ 6.014063] igb: probe of 0000:14:00.0 failed with error -3
<6>[ 6.014070] pci 0000:00:1c.5: PCI->APIC IRQ transform: INT B -> IRQ 17
<6>[ 6.014078] igb 0000:15:00.0: PCI->APIC IRQ transform: INT A -> IRQ 17
<4>[ 6.015189] igb: probe of 0000:15:00.0 failed with error -3

 

Only ports 3 and 4 remain in the working state:

 

<6>[ 36.919700] igb 0000:17:00.0 port3: renamed from eth1
<6>[ 36.936178] igb 0000:16:00.0 port4: renamed from eth0
<6>[ 37.986605] IPv6: ADDRCONF(NETDEV_UP): port3: link is not ready
<6>[ 37.986606] 8021q: adding VLAN 0 to HW filter on device port3
<6>[ 38.062584] IPv6: ADDRCONF(NETDEV_UP): port4: link is not ready
<6>[ 38.062585] 8021q: adding VLAN 0 to HW filter on device port4
<6>[ 40.904486] igb 0000:17:00.0 port3: igb: port3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
<6>[ 41.012189] IPv6: ADDRCONF(NETDEV_CHANGE): port3: link becomes ready
<6>[ 144.628234] igb 0000:17:00.0 port3: igb: port3 NIC Link is Down
<6>[ 149.940616] igb 0000:17:00.0 port3: igb: port3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
<6>[ 256.980223] igb 0000:17:00.0 port3: igb: port3 NIC Link is Down
<6>[ 264.296575] igb 0000:17:00.0 port3: igb: port3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
<6>[ 611.196254] igb 0000:17:00.0 port3: igb: port3 NIC Link is Down
<6>[ 614.284537] igb 0000:16:00.0 port4: igb: port4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
<6>[ 614.608272] IPv6: ADDRCONF(NETDEV_CHANGE): port4: link becomes ready
<6>[ 697.336185] igb 0000:16:00.0 port4: igb: port4 NIC Link is Down
<6>[ 700.660531] igb 0000:16:00.0 port4: igb: port4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
<6>[ 702.792531] igb 0000:17:00.0 port3: igb: port3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

 

Contributors