Technical Tip: Specific network interface controller test in Hardware Quick Inspection Package (HQIP)

[mattchow_FTNT]

Description	This article describes how to verify specific network interface on HQIP test without connecting all of the interfaces with cables.
Scope	FortiGate.
Solution	HQIP test begins with connecting network ports instruction as shown below: Wire the network ports as follows for the NIC loopback test: [PORT1 - PORT2] [PORT3 - PORT4]... [PORT31 - PORT32] Network Interface Controller Test  shown 'PASS' on 'Fortinet Hardware Quick Inspection' Report if all interfaces connected successfully with cables without any issue as shown below:  ========================= Fortinet Hardware Quick Inspection Report ========================= BIOS Integrity Check: PASS System Configuration Check: PASS Memory Test: PASS CPU Test: PASS CPU/Memory Performance Test: PASS FortiASIC Test: PASS (2 ASICs) USB Test: N/A (0 USB Devices) USB Slave Test: fail X (0 USB Slave Devices) Boot Device Test: PASS Hard Disk Test: PASS (1/1 Hard Disks) Network Interface Controller Test: PASS <----- NPU DDR Memory Test: PASS (2 NPU Devices) LED Test: PASS In many cases, the user does not have sufficient cables, especially FortiGate high end model contains a lot of physical interfaces.  It is possible to skip the Fortinet Hardware Quick Inspection report and verify the specific interface by checking the 'Network Interface Controller Test' only. For example, It is necessary to test specific interface port 31 or port 32 only and ignore interfaces from port1 to port30. Although overall Network Interface Controller Test showed 'fail X' on the 'Fortinet Hardware Quick Inspection' Report because not all interfaces are connected with cables as shown below: ========================= Fortinet Hardware Quick Inspection Report ========================= BIOS Integrity Check: PASS System Configuration Check: PASS Memory Test: PASS CPU Test: PASS CPU/Memory Performance Test: PASS FortiASIC Test: PASS (2 ASICs) USB Test: N/A (0 USB Devices) USB Slave Test: fail X (0 USB Slave Devices) Boot Device Test: PASS Hard Disk Test: PASS (1/1 Hard Disks) Network Interface Controller Test: fail X <----- Failed because of not all interfaces such as port 1 to port 8 connected with cables. NPU DDR Memory Test: PASS (2 NPU Devices) LED Test: PASS It is still possible to check specific port31 or port32 statuses on the 'Network Interface Controller Test'. It is expected to see 'Not Linked' from port 1 to port 30  because no cables are connected on these ports, and 'Linked' status on port 31 and port 32 that has cables connected to each other as shown below: Network Interface Controller Test: Initializing port1, MAC:70:4C:A5:1B:A5:84 (Not linked) Interface port1 link status error! Initializing port2, MAC:70:4C:A5:1B:A5:85 (Not linked) Interface port2 link status error! Initializing port3, MAC:70:4C:A5:1B:A5:86 (Not linked) Interface port3 link status error! Initializing port4, MAC:70:4C:A5:1B:A5:87 (Not linked) Interface port4 link status error! Initializing port5, MAC:70:4C:A5:1B:A5:88 (Not linked) Interface port5 link status error! Initializing port6, MAC:70:4C:A5:1B:A5:89 (Not linked) Interface port6 link status error! Initializing port7, MAC:70:4C:A5:1B:A5:8A (Not linked) Interface port7 link status error! Initializing port8, MAC:70:4C:A5:1B:A5:8B (Not linked) Interface port8 link status error! Initializing port9, MAC:70:4C:A5:1B:A5:8C (Not linked) Interface port9 link status error! Initializing port10, MAC:70:4C:A5:1B:A5:8D (Not linked) Interface port10 link status error! Initializing port11, MAC:70:4C:A5:1B:A5:8E (Not linked) Interface port11 link status error! Initializing port12, MAC:70:4C:A5:1B:A5:8F (Not linked) Interface port12 link status error! Initializing port13, MAC:70:4C:A5:1B:A5:90 (Not linked) Interface port13 link status error! Initializing port14, MAC:70:4C:A5:1B:A5:91 (Not linked) Interface port14 link status error! Initializing port15, MAC:70:4C:A5:1B:A5:92 (Not linked) Interface port15 link status error! Initializing port16, MAC:70:4C:A5:1B:A5:93 (Not linked) Interface port16 link status error! Initializing port17, MAC:70:4C:A5:1B:A5:96 (Not linked) Interface port17 link status error! Initializing port18, MAC:70:4C:A5:1B:A5:97 (Not linked) Interface port18 link status error! Initializing port19, MAC:70:4C:A5:1B:A5:98 (Not linked) Interface port19 link status error! Initializing port20, MAC:70:4C:A5:1B:A5:99 (Not linked) Interface port20 link status error! Initializing port21, MAC:70:4C:A5:1B:A5:9A (Not linked) Interface port21 link status error! Initializing port22, MAC:70:4C:A5:1B:A5:9B (Not linked) Interface port22 link status error! Initializing port23, MAC:70:4C:A5:1B:A5:9C (Not linked) Interface port23 link status error! Initializing port24, MAC:70:4C:A5:1B:A5:9D (Not linked) Interface port24 link status error! Initializing port25, MAC:70:4C:A5:1B:A5:9E (Not linked) Interface port25 link status error! Initializing port26, MAC:70:4C:A5:1B:A5:9F (Not linked) Interface port26 link status error! Initializing port27, MAC:70:4C:A5:1B:A5:A0 (Not linked) Interface port27 link status error! Initializing port28, MAC:70:4C:A5:1B:A5:A1 (Not linked) Interface port28 link status error! Initializing port29, MAC:70:4C:A5:1B:A5:A2 (Not linked) Interface port29 link status error! Initializing port30, MAC:70:4C:A5:1B:A5:A3 (Not linked) Interface port30 link status error! Initializing port31, MAC:70:4C:A5:1B:A5:A4 (Linked 1000M)   <----- port 31 successfully connected to port32. Initializing port32, MAC:70:4C:A5:1B:A5:A5 (Linked 1000M)   <----- Port 32 successfully connected to port31. If port 31 or port 32 has a hardware issue or failure, the result will be 'Not linked' as shown below. It can be used for RMA as well: Initializing port31, MAC:70:4C:A5:1B:A5:A4 (Not linked)    <----- Loopback test connected to port32 Interface port31 link status error! Initializing port32, MAC:70:4C:A5:1B:A5:A5 (Not linked)   <----- Loopback test connected to port31        Interface port32 link status error!