Chapter 18 Troubleshooting : ­Troubleshooting tools : FortiOS diagnostics : Hardware NIC
  
Hardware NIC
Monitor hardware network operations using the following command:
diag hardware deviceinfo nic <interface>
The information displayed by this command is important as errors at the interface are indicative of data link or physical layer issues which may impact the performance of the FortiGate unit.
The following is sample output when <interface> = internal:
System_Device_Name port5
Current_HWaddr 00:09:0f:68:35:60
Permanent_HWaddr 00:09:0f:68:35:60
Link up
Speed 100
Duplex full
[……]
Rx_Packets=5685708
Tx_Packets=4107073
Rx_Bytes=617908014
Tx_Bytes=1269751248
Rx_Errors=0
Tx_Errors=0
Rx_Dropped=0
Tx_Dropped=0
[…..]
 
The diag hardware deviceinfo nic command displays a list of hardware related error names and values. The following table explains the items in the list and their meanings.
 
Table 106: Possible hardware errors and meanings
Field
Definition
Rx_Errors = rx error count
Bad frame was marked as error by PHY.
Rx_CRC_Errors +
Rx_Length_Errors -
Rx_Align_Errors
This error is only valid in 10/100M mode.
Rx_Dropped or
Rx_No_Buffer_Count
Running out of buffer space.
Rx_Missed_Errors
Equals Rx_FIFO_Errors + CEXTERR (Carrier Extension Error Count). Only valid in 1000M mode, whichis marked by PHY.
Tx_Errors = Tx_Aborted_Errors
ECOL (Excessive Collisions Count). Only valid in half-duplex mode.
Tx_Window_Errors
LATECOL (Late Collisions Count). Late collisions are collisions that occur after 64-byte time into the transmission of the packet while working in 10 to100Mb/s data rate and 512-byte timeinto the transmission of the packet while working in the 1000Mb/s data rate. This register only increments if transmits are enabled and the device is in half-duplex mode.
Rx_Dropped
See Rx_Errors.
Tx_Dropped
Not defined.
Collisions
Total number of collisions experienced by the transmitter. Valid in half-duplex mode.
Rx_Length_Errors
Transmission length error.
Rx_Over_Errors
Not defined.
Rx_CRC_Errors
Frame CRC error.
Rx_Frame_Errors
Same as Rx_Align_Errors. This error is only valid in 10/100M mode.
Rx_FIFO_Errors
Same as Rx_Missed_Errors - a missed packet count.
Tx_Aborted_Errors
See Tx_Errors.
Tx_Carrier_Errors
The PHY should assert the internal carrier sense signal during every transmission. Failure to do so may indicate that the link has failed or the PHY has an incorrect link configuration. This register only increments if transmits are enabled. This register is not valid in internal SerDes 1 mode (TBI mode for the 82544GC/EI) and is only valid when the Ethernet controller is operating at full duplex.
Tx_FIFO_Errors
Not defined.
Tx_Heartbeat_Errors
Not defined.
Tx_Window_Errors
See LATECOL.
Tx_Single_Collision_Frames
Counts the number of times that a successfully transmitted packet encountered a single collision. The value only increments if transmits are enabled and the Ethernet controller is in half-duplex mode.
Tx_Multiple_Collision_Frames
A Multiple Collision Count which counts the number of times that a transmit encountered more than one collision but less than 16. The value only increments if transmits are enabled and the Ethernet controller is in half-duplex mode.
Tx_Deferred
Counts defer events. A defer event occurs when the transmitter cannot immediately send a packet due to the medium being busy because another device is transmitting, the IPG timer has not expired, half-duplex deferral events are occurring, XOFF frames are being received, or the link is not up. This register only increments if transmits are enabled. This counter does not increment for streaming transmits that are deferred due to TX IPG.
Rx_Frame_Too_Longs
The Rx frame is over size.
Rx_Frame_Too_Shorts
The Rx frame is too short.
Rx_Align_Errors
This error is only valid in 10/100M mode.
Symbol Error Count
Counts the number of symbol errors between reads - SYMERRS. The count increases for every bad symbol received, whether or not a packet is currently being received and whether or not the link is up. This register only increments in internal SerDes mode.