Displaying detail Hardware NIC information
Monitoring the hardware NIC is important because interface errors indicate data link or physical layer issues which may impact the performance of the FortiGate.
To monitor hardware network operations in the CLI:
diagnose hardware deviceinfo nic <interface>
Sample output:
The following is sample output when the <interface> is set to lan:
System_Device_Name lan
Current_HWaddr 00:09:0f:68:35:60
Permanent_HWaddr 00:09:0f:68:35:60
State up
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
[……]
Error descriptions
The diagnose hardware deviceinfo nic command displays a list of error names and values that are related to hardware.
The following table describes possible hardware errors:
|
Field |
Description |
|---|---|
|
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, which is marked by PHY |
|
Tx_Errors = Tx_Aborted_Errors |
ECOL (Excessive Collisions Count); only valid in half-duplex mode |
|
Tx_Window_Errors |
Late Collisions (LATECOL) Count Late collisions are collisions that occur after 64-byte time into the transmission of the packet while working in 10 to 100 Mb/s data rate and 512-byte time into the transmission of the packet while working in the 1,000 Mb/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 isn't valid in internal SerDes 1 mode (TBI mode for the 82544GC/EI) and is valid only 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 increments only if transmits are enabled and the Ethernet controller is in half-duplex mode. |
|
Tx_Multiple_Collision_Frames |
A Multiple Collision Count which indicates the number of times that a transmit encountered more than one collision, but less than 16. The value increments only if transmits are enabled and the Ethernet controller is in half-duplex mode. |
|
Tx_Deferred |
Counts defer events. A deferred event occurs when the transmitter cannot immediately send a packet due to:
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 oversized |
|
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 that's received, whether or not a packet is currently being received and whether or not the link is up. This register increments only in internal SerDes mode. |