|
The first symptom is found when the ping test to the LAN interface has some packet lost, for example, ping lost to FortiGate interface default IP:
C:\Users\Helio>ping -t 192.168.1.99
Reply from 192.168.1.99: bytes=32 time=5ms TTL=255
Reply from 192.168.1.99: bytes=32 time=6ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.99: bytes=32 time=1ms TTL=255
Reply from 192.168.1.99: bytes=32 time<1m TTL=255
The HQIP test shows interface link being detected:
Interface MAC Linkage CurrentSpeed CurrentDuplex SettingSpeed Default(Supported)
--------------------------------------------------------------------------------------
lan E8:1C:BA:40:2F:7A Linked 1000 FULL auto (1000baseT_Full)
wan E8:1C:BA:40:2F:79 Linked 1000 FULL auto (1000baseT_Full)
lan4 E8:1C:BA:40:2F:7D Linked 1000 FULL auto (1000baseT_Full)
Network Interface Detection - [[ PASS ]]
But when the HQIP doing an interface loopback test, the below error is found:
Interface | Packets / Checked | Pkt/s | kBytes | kB/s | Drop/Err/Crc |
< 80> lan.tx: 2007 200 156 15 0 0
< 80> lan.rx: 5 1 0 0 0 0 0 0
< 80> lan.er: round 1 Please check wired cables or switch device's settings SEND/RECV below threshold (<80%)
lan test 1 rounds, failed: NORECV:2 NOSEND:0 SENDDROP:0 SENDERR:0 RECVDROP:0 RECVERR:0 CRCERR:0
< 80> wan.tx: 2002 182 156 14 0 0
< 80> wan.rx: 2000 2188 181 156 14 0 0 0
< 80> lan4.tx: 2002 182 156 14 0 0
< 80> lan4.rx: 2000 2180 181 156 14 0 0 0
It is important to confirm the network cables are working fine before any test. If such an error is found, due to hardware damage, the solution is to RMA FortiGate.
|
