Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
dvp
New Contributor

HQIP NIC test fails

Hi all. I`m new at forum. Can anybody help with issue?

 

I got FortiWifi 40c. Running HQIP test on my device. Instructions say:

 

Instructions:

- Wire the network ports as following for NIC loopback test. [WAN1 -WAN2] [PORT1 - PORT2] [PORT3 - PORT4] [style="background-color: #ccffff;"][PORT5-selfloop][/style]

 

What does it mean port selfloop? Because when I strart my test, it fails: "Network Interface Controller Test:      fail X"

 

Information from log:

 

 

==> Network Interface Controller Test

Initializing wan2, MAC:08:5B:0E:15:78:D5 (Linked 1000M) Initializing wan1, MAC:08:5B:0E:15:78:D6 (Linked 1000M) Initializing internal1, MAC:08:5B:0E:15:78:D4 (Linked 1000M) Initializing internal2, MAC:08:5B:0E:15:78:D7 (Linked 1000M) Initializing internal3, MAC:08:5B:0E:15:78:D8 (Linked 1000M) Initializing internal4, MAC:08:5B:0E:15:78:D9 (Linked 1000M) Initializing internal5, MAC:08:5B:0E:15:78:DA (Not linked) Interface wan2 pair: [me=> wan2 08:5B:0E:15:78:D5] [he=> wan1 08:5B:0E:15:78:D6] Interface wan1 pair: [me=> wan1 08:5B:0E:15:78:D6] [he=> wan2 08:5B:0E:15:78:D5] Interface internal1 pair: [me=> internal1 08:5B:0E:15:78:D4] [he=> internal2 08:5B:0E:15:78:D7] Interface internal2 pair: [me=> internal2 08:5B:0E:15:78:D7] [he=> internal1 08:5B:0E:15:78:D4] Interface internal3 pair: [me=> internal3 08:5B:0E:15:78:D8] [he=> internal4 08:5B:0E:15:78:D9] Interface internal4 pair: [me=> internal4 08:5B:0E:15:78:D9] [he=> internal3 08:5B:0E:15:78:D8] netbt negotiation retry: 9 netbt negotiation retry: 8 netbt negotiation retry: 7 netbt negotiation retry: 6 netbt negotiation retry: 5 netbt negotiation retry: 4 netbt negotiation retry: 3 netbt negotiation retry: 2 netbt negotiation retry: 1 netbt negotiation retry: 0 Total 6 pairs configurated. Pairing-up Time: 21 Seconds NETBT device started. L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | < 64> wan2.tx: 5756 575 359 35 0 0 < 64> wan2.rx: 5756 1100 575 359 35 0 0 0 < 64> wan1.tx: 5855 532 365 33 0 0 < 64> wan1.rx: 5855 1225 532 365 33 0 0 0 < 64>internal1.tx: 5657 514 353 32 0 0 < 64>internal1.rx: 5657 1225 514 353 32 0 0 0 < 64>internal2.tx: 5657 514 353 32 0 0 < 64>internal2.rx: 5658 1225 514 353 32 0 0 0 < 64>internal3.tx: 5472 497 342 31 0 0 < 64>internal3.rx: 5472 1225 497 342 31 0 0 0 < 64>internal4.tx: 5298 481 331 30 0 0 < 64>internal4.rx: 5298 1225 481 331 30 0 0 0 < 64>internal5.tx: 0 0 0 0 0 0 < 64>internal5.rx: 0 0 0 0 0 0 0 0 < 64>internal5.er: round 1 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 1 rounds, failed: NORECV:2 NOSEND:1 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | < 128> wan2.tx: 7061 588 882 73 0 0 < 128> wan2.rx: 7060 1475 588 882 73 0 0 0 < 128> wan1.tx: 6961 580 870 72 0 0 < 128> wan1.rx: 6962 1475 580 870 72 0 0 0 < 128>internal1.tx: 7392 616 924 77 0 0 < 128>internal1.rx: 7392 1475 616 924 77 0 0 0 < 128>internal2.tx: 7089 590 886 73 0 0 < 128>internal2.rx: 7088 1475 590 886 73 0 0 0 < 128>internal3.tx: 7542 628 942 78 0 0 < 128>internal3.rx: 7542 1475 628 942 78 0 0 0 < 128>internal4.tx: 7051 587 881 73 0 0 < 128>internal4.rx: 7051 1475 587 881 73 0 0 0 < 128>internal5.tx: 0 0 0 0 0 0 < 128>internal5.rx: 0 0 0 0 0 0 0 0 < 128>internal5.er: round 2 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 2 rounds, failed: NORECV:4 NOSEND:2 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | < 256> wan2.tx: 6409 534 1602 133 0 0 < 256> wan2.rx: 6410 1500 534 1602 133 0 0 0 < 256> wan1.tx: 6176 514 1544 128 0 0 < 256> wan1.rx: 6176 1475 514 1544 128 0 0 0 < 256>internal1.tx: 5923 493 1480 123 0 0 < 256>internal1.rx: 5922 1475 493 1480 123 0 0 0 < 256>internal2.tx: 6395 532 1598 133 0 0 < 256>internal2.rx: 6395 1475 532 1598 133 0 0 0 < 256>internal3.tx: 5957 496 1489 124 0 0 < 256>internal3.rx: 5957 1475 496 1489 124 0 0 0 < 256>internal4.tx: 6433 536 1608 134 0 0 < 256>internal4.rx: 6433 1475 536 1608 134 0 0 0 < 256>internal5.tx: 0 0 0 0 0 0 < 256>internal5.rx: 0 0 0 0 0 0 0 0 < 256>internal5.er: round 3 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 3 rounds, failed: NORECV:6 NOSEND:3 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | < 512> wan2.tx: 5539 461 2769 230 0 0 < 512> wan2.rx: 5539 1400 461 2769 230 0 0 0 < 512> wan1.tx: 6062 505 3031 252 0 0 < 512> wan1.rx: 6061 1425 505 3030 252 0 0 0 < 512>internal1.tx: 5865 488 2932 244 0 0 < 512>internal1.rx: 5865 1425 488 2932 244 0 0 0 < 512>internal2.tx: 5569 464 2784 232 0 0 < 512>internal2.rx: 5569 1425 464 2784 232 0 0 0 < 512>internal3.tx: 5947 495 2973 247 0 0 < 512>internal3.rx: 5947 1425 495 2973 247 0 0 0 < 512>internal4.tx: 6298 524 3149 262 0 0 < 512>internal4.rx: 6298 1425 524 3149 262 0 0 0 < 512>internal5.tx: 0 0 0 0 0 0 < 512>internal5.rx: 0 0 0 0 0 0 0 0 < 512>internal5.er: round 4 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 4 rounds, failed: NORECV:8 NOSEND:4 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | <1024> wan2.tx: 4353 362 4353 362 0 0 <1024> wan2.rx: 4353 1487 362 4353 362 0 0 0 <1024> wan1.tx: 4176 348 4176 348 0 0 <1024> wan1.rx: 4176 1513 348 4176 348 0 0 0 <1024>internal1.tx: 4532 377 4532 377 0 0 <1024>internal1.rx: 4533 1512 377 4533 377 0 0 0 <1024>internal2.tx: 4365 363 4365 363 0 0 <1024>internal2.rx: 4366 1512 363 4366 363 0 0 0 <1024>internal3.tx: 4032 336 4032 336 0 0 <1024>internal3.rx: 4032 1513 336 4032 336 0 0 0 <1024>internal4.tx: 4261 355 4261 355 0 0 <1024>internal4.rx: 4262 1512 355 4262 355 0 0 0 <1024>internal5.tx: 0 0 0 0 0 0 <1024>internal5.rx: 0 0 0 0 0 0 0 0 <1024>internal5.er: round 5 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 5 rounds, failed: NORECV:10 NOSEND:5 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

L----------------------------------------------------------------------------------- Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc | <1518> wan2.tx: 3332 277 4939 411 0 0 <1518> wan2.rx: 3333 1459 277 4940 411 0 0 0 <1518> wan1.tx: 3221 268 4774 397 0 0 <1518> wan1.rx: 3220 1435 268 4773 397 0 0 0 <1518>internal1.tx: 3081 256 4567 380 0 0 <1518>internal1.rx: 3080 1435 256 4565 380 0 0 0 <1518>internal2.tx: 3334 277 4942 411 0 0 <1518>internal2.rx: 3333 1436 277 4940 411 0 0 0 <1518>internal3.tx: 3585 298 5314 442 0 0 <1518>internal3.rx: 3585 1435 298 5314 442 0 0 0 <1518>internal4.tx: 3237 269 4798 399 0 0 <1518>internal4.rx: 3236 1436 269 4797 399 0 0 0 <1518>internal5.tx: 0 0 0 0 0 0 <1518>internal5.rx: 0 0 0 0 0 0 0 0 <1518>internal5.er: round 6 Please check wired cables or switch device's settings NORECV NOSEND internal5 test 6 rounds, failed: NORECV:12 NOSEND:6 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0

NETBT device stopped.

<== Network Interface Controller Test - FAIL

==> NPU DDR Memory Test

 

Total 0 NP2 devices tested, 0 failed

 

Total 0 NP4 devices tested, 0 failed

 

 

 

 

 

 

 

 

Thank you for any help you can provide.

2 Solutions
ede_pfau
SuperUser
SuperUser

Hello,

 

and welcome to the forums.

As you have not cabled port5 all tests with that port will fail, and in summary the NIC test will fail. Therefore, you can savely ignore the results.

BTW, not even I have a loop plug to test a single port. If you want to be absolutely sure that port5 too is working correctly then wire port1 and port5 and leave port4 open, and then rerun the HQIP diags. This time, the NIC test will fail with port4 being defective. But you will get a positive result on port5, and thus, on all ports.


Ede


"Kernel panic: Aiee, killing interrupt handler!"

View solution in original post

Ede"Kernel panic: Aiee, killing interrupt handler!"
Dave_Hall
Honored Contributor

dvp@muk.ua wrote:

What does it mean port selfloop? [...]

I recall the old HQIP KB article use to have a diag on creating a loop-back plug, but I am assuming it's the same instructions is anywhere else - just take a standard JR45 end, connect pin 1 to 3 and 2 to 6.  (pic from this page.)

 

 

 

I have noticed some of the newer HQIP test images are trying to do away with the need to crate loop-back plugs.

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

View solution in original post

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
3 REPLIES 3
ede_pfau
SuperUser
SuperUser

Hello,

 

and welcome to the forums.

As you have not cabled port5 all tests with that port will fail, and in summary the NIC test will fail. Therefore, you can savely ignore the results.

BTW, not even I have a loop plug to test a single port. If you want to be absolutely sure that port5 too is working correctly then wire port1 and port5 and leave port4 open, and then rerun the HQIP diags. This time, the NIC test will fail with port4 being defective. But you will get a positive result on port5, and thus, on all ports.


Ede


"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
Dave_Hall
Honored Contributor

dvp@muk.ua wrote:

What does it mean port selfloop? [...]

I recall the old HQIP KB article use to have a diag on creating a loop-back plug, but I am assuming it's the same instructions is anywhere else - just take a standard JR45 end, connect pin 1 to 3 and 2 to 6.  (pic from this page.)

 

 

 

I have noticed some of the newer HQIP test images are trying to do away with the need to crate loop-back plugs.

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
ede_pfau
SuperUser
SuperUser

@Dave:

and I thought "what a brillant idea to run 2 tests and shift the missing port - 100% reliable result but no need for special hardware". I'm the only one thumbing that one up, again...


Ede


"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
Labels
Top Kudoed Authors