Fortinet black logo

Administration Guide

Displaying detail Hardware NIC information

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>

or

diagnose netlink interface list <interface>
Sample output:

The following is sample output when the <interface> is set to port1:

# diagnose hardware deviceinfo nic port1
Name:            port1
...
HWaddr:          00:0c:xx:xx:xx:xx
Permanent Hwaddr:00:0c:xx:xx:xx:xx
State:           up
Link:            up
Mtu:             1500
Supported:       1000full 10000full
Advertised:
Speed:           10000full
Auto:            disabled
RX Ring:                 1024
TX Ring:                 512
Rx packets:              48758040
Rx bytes:                16071168530
Rx compressed:           0
Rx dropped:              3
Rx errors:               3
  Rx Length err:         0
  Rx Buf overflow:       0
  Rx Crc err:            0
  Rx Frame err:          0
  Rx Fifo overrun:       0
  Rx Missed packets:     0
Tx packets:              27153432
Tx bytes:                7107106138
Tx compressed:           0
Tx dropped:              0
Tx errors:               0
  Tx Aborted err:        0
  Tx Carrier err:        0
  Tx Fifo overrun:       0
  Tx Heartbeat err:      0
  Tx Window err:         0
Multicasts:              31747
Collisions:              0
# diagnose netlink interface list port1
if=port1 family=00 type=1 index=3 mtu=1500 link=0 master=0
flags=up broadcast run multicast
Qdisc=mq hw_addr=00:0c:29:fc:18:54 broadcast_addr=ff:ff:ff:ff:ff:ff
stat: rxp=61149 txp=81109 rxb=5839308 txb=52396373 rxe=0 txe=0 rxd=0 txd=0 mc=95 collision=0 @ time=1678486883
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0
misc rxc=0 txc=0
Field descriptions

The diagnose hardware deviceinfo nic and diagnose netlink interface list commands display lists of error names and values that are related to hardware.

The following table describes possible hardware errors:

Field

Description

Rx packets (rxp)

Number of received packets.

Tx packets (txp)

Number of transmitted packets.

Rx bytes (rxb)

Number of received bytes.

Tx bytes (txb)

Number of transmitted bytes.

Rx errors (rxe) = rx error count

Bad frame was marked as error by PHY.

Tx errors (txe) = Tx aborted errors

ECOL (Excessive Collisions Count); only valid in half-duplex mode.

Rx CRC errors +

Rx length errors -

Rx align errors

This error is only valid in 10/100M mode.

Rx dropped (rxd) or

Rx no buffer count

Running out of buffer space.

Tx dropped (txd)

Number of dropped packet.

Multicast (mc)

Number of multicast packets received.

Collisions

Total number of collisions experienced by the transmitter; valid in half-duplex mode.

Rx length errors (rxl)

Number of packets dropped due to invalid length.

Rx over errors (rxo)

Receive FIFO overflow event counter.

Rx CRC errors (rxc)

Number of received packets with Frame CRC error.

Rx frame errors (rxf)

Same as Rx_Align_Errors. This error is only valid in 10/100M mode.

Rx FIFO errors (rxfi)

Same as Rx_Missed_Errors - a missed packet count

Rx missed errors (rxm)

Equals Rx_FIFO_Errors + CEXTERR (Carrier Extension Error Count). Only valid in 1000M mode, which is marked by PHY.

Tx aborted errors (txa)

See Tx_Errors.

Tx carrier errors (txc)

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 (txfi)

Number of Frame transmission error due to underflow.

Tx heartbeat errors (txh)

Number of heartbeat error.

Tx window errors (txw)

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 compressed (misc rxc)

Number of received compressed packets.

Tx compressed (misc txc)

Number of transmitted compressed packets.

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:

  • 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 .
  • 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 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 (SYMERRS) between reads.

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.

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>

or

diagnose netlink interface list <interface>
Sample output:

The following is sample output when the <interface> is set to port1:

# diagnose hardware deviceinfo nic port1
Name:            port1
...
HWaddr:          00:0c:xx:xx:xx:xx
Permanent Hwaddr:00:0c:xx:xx:xx:xx
State:           up
Link:            up
Mtu:             1500
Supported:       1000full 10000full
Advertised:
Speed:           10000full
Auto:            disabled
RX Ring:                 1024
TX Ring:                 512
Rx packets:              48758040
Rx bytes:                16071168530
Rx compressed:           0
Rx dropped:              3
Rx errors:               3
  Rx Length err:         0
  Rx Buf overflow:       0
  Rx Crc err:            0
  Rx Frame err:          0
  Rx Fifo overrun:       0
  Rx Missed packets:     0
Tx packets:              27153432
Tx bytes:                7107106138
Tx compressed:           0
Tx dropped:              0
Tx errors:               0
  Tx Aborted err:        0
  Tx Carrier err:        0
  Tx Fifo overrun:       0
  Tx Heartbeat err:      0
  Tx Window err:         0
Multicasts:              31747
Collisions:              0
# diagnose netlink interface list port1
if=port1 family=00 type=1 index=3 mtu=1500 link=0 master=0
flags=up broadcast run multicast
Qdisc=mq hw_addr=00:0c:29:fc:18:54 broadcast_addr=ff:ff:ff:ff:ff:ff
stat: rxp=61149 txp=81109 rxb=5839308 txb=52396373 rxe=0 txe=0 rxd=0 txd=0 mc=95 collision=0 @ time=1678486883
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0
misc rxc=0 txc=0
Field descriptions

The diagnose hardware deviceinfo nic and diagnose netlink interface list commands display lists of error names and values that are related to hardware.

The following table describes possible hardware errors:

Field

Description

Rx packets (rxp)

Number of received packets.

Tx packets (txp)

Number of transmitted packets.

Rx bytes (rxb)

Number of received bytes.

Tx bytes (txb)

Number of transmitted bytes.

Rx errors (rxe) = rx error count

Bad frame was marked as error by PHY.

Tx errors (txe) = Tx aborted errors

ECOL (Excessive Collisions Count); only valid in half-duplex mode.

Rx CRC errors +

Rx length errors -

Rx align errors

This error is only valid in 10/100M mode.

Rx dropped (rxd) or

Rx no buffer count

Running out of buffer space.

Tx dropped (txd)

Number of dropped packet.

Multicast (mc)

Number of multicast packets received.

Collisions

Total number of collisions experienced by the transmitter; valid in half-duplex mode.

Rx length errors (rxl)

Number of packets dropped due to invalid length.

Rx over errors (rxo)

Receive FIFO overflow event counter.

Rx CRC errors (rxc)

Number of received packets with Frame CRC error.

Rx frame errors (rxf)

Same as Rx_Align_Errors. This error is only valid in 10/100M mode.

Rx FIFO errors (rxfi)

Same as Rx_Missed_Errors - a missed packet count

Rx missed errors (rxm)

Equals Rx_FIFO_Errors + CEXTERR (Carrier Extension Error Count). Only valid in 1000M mode, which is marked by PHY.

Tx aborted errors (txa)

See Tx_Errors.

Tx carrier errors (txc)

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 (txfi)

Number of Frame transmission error due to underflow.

Tx heartbeat errors (txh)

Number of heartbeat error.

Tx window errors (txw)

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 compressed (misc rxc)

Number of received compressed packets.

Tx compressed (misc txc)

Number of transmitted compressed packets.

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:

  • 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 .
  • 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 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 (SYMERRS) between reads.

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.