Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • CLI Reference

    Home FortiWeb 6.2.1 CLI Reference
    6.2.1
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0

    hardware nic

    hardware nic

    Use this command to display a list of hardware specifications for the network interface card (NIC) physical ports on the FortiWeb appliance. (In the case of FortiWeb-VM, this will instead be for virtual hardware—the vNICs—and therefore the driver will be a virtual driver such as vmxnet, and the interrupt will be a virtual IRQ address.)

    If the FortiWeb’s network hardware has failed, this command can help to detect it. For example, if you know that the network cable is good and the configuration is correct, but this command displays Link detected: no), the physical network port may be broken.

    To use this command, your administrator account’s access control profile must have at least r permission to the sysgrp area. For details, see Permissions.

    Syntax

    diagnose hardware nic list [<interface_name>]

    Variable Description Default
    list [<interface_name>]

    Optionally, enter the name of a physical network interface, such as port1, to display its link status, configuration, hardware information, status, and connectivity statistics such as collision errors.

    If you omit the name of a NIC port, the CLI returns a list of all physical network interfaces, as well as the loopback interface (lo):

    lo

    port1

    port2

    port3

    port4

    Note: The detected physical link status from this command is not the same as its configured administrative status.

    For example, even though you have used config system interface to configure port1 with set status down, if the cable is physically plugged in, diagnose hardware nic list port1 will indicate correctly that the link is up (Link detected: yes).

    		 No default.

    Example

    diagnose hardware nic list

    Output similar to the following appears in the CLI:

    driver vmxnet

    version 2.0.9.0

    firmware-version N/A

    bus-info 0000:00:11.0

    Supported ports TP

    Supported link modes 1000baseT/Full

    Supports auto-negotiation: No

    Advertised link modes: Not reported

    Advertised auto-negotiation: No

    Speed: 1000Mb/s

    Duplex: Full

    Port: Twisted Pair

    PHYAD 0

    Transceiver: internal

    Auto-negotiation off

    Link detected yes

    Link encap Ethernet

    HWaddr 00:0C:29:FE:2B:47

    INET addr 10.1.1.221

    Bcast 10.1.1.221

    Mask 256.256.256.256

    FLAG UP BROADCAST RUNNING MULTICAST

    MTU 1500

    MEtric 1

    Outfill 0

    Keepalive 6846704

    Interrupt 18

    Base address 0x1400

    RX packets 171487

    RX errors 167784

    RX dropped 0

    RX overruns 0

    RX frame 0

    TX packets 202724

    TX errors 0

    TX dropped 0

    TX overruns 0

    TX carrier 0

    TX collisions 0

    TX queuelen 1000

    RX bytes 72772373 (69.4 Mb)

    TX bytes 32288070 (30.7 Mb)

    Related topics

    Previous
    Next

    hardware nic

    hardware nic

    Use this command to display a list of hardware specifications for the network interface card (NIC) physical ports on the FortiWeb appliance. (In the case of FortiWeb-VM, this will instead be for virtual hardware—the vNICs—and therefore the driver will be a virtual driver such as vmxnet, and the interrupt will be a virtual IRQ address.)

    If the FortiWeb’s network hardware has failed, this command can help to detect it. For example, if you know that the network cable is good and the configuration is correct, but this command displays Link detected: no), the physical network port may be broken.

    To use this command, your administrator account’s access control profile must have at least r permission to the sysgrp area. For details, see Permissions.

    Syntax

    diagnose hardware nic list [<interface_name>]

    Variable Description Default
    list [<interface_name>]

    Optionally, enter the name of a physical network interface, such as port1, to display its link status, configuration, hardware information, status, and connectivity statistics such as collision errors.

    If you omit the name of a NIC port, the CLI returns a list of all physical network interfaces, as well as the loopback interface (lo):

    lo

    port1

    port2

    port3

    port4

    Note: The detected physical link status from this command is not the same as its configured administrative status.

    For example, even though you have used config system interface to configure port1 with set status down, if the cable is physically plugged in, diagnose hardware nic list port1 will indicate correctly that the link is up (Link detected: yes).

    		 No default.

    Example

    diagnose hardware nic list

    Output similar to the following appears in the CLI:

    driver vmxnet

    version 2.0.9.0

    firmware-version N/A

    bus-info 0000:00:11.0

    Supported ports TP

    Supported link modes 1000baseT/Full

    Supports auto-negotiation: No

    Advertised link modes: Not reported

    Advertised auto-negotiation: No

    Speed: 1000Mb/s

    Duplex: Full

    Port: Twisted Pair

    PHYAD 0

    Transceiver: internal

    Auto-negotiation off

    Link detected yes

    Link encap Ethernet

    HWaddr 00:0C:29:FE:2B:47

    INET addr 10.1.1.221

    Bcast 10.1.1.221

    Mask 256.256.256.256

    FLAG UP BROADCAST RUNNING MULTICAST

    MTU 1500

    MEtric 1

    Outfill 0

    Keepalive 6846704

    Interrupt 18

    Base address 0x1400

    RX packets 171487

    RX errors 167784

    RX dropped 0

    RX overruns 0

    RX frame 0

    TX packets 202724

    TX errors 0

    TX dropped 0

    TX overruns 0

    TX carrier 0

    TX collisions 0

    TX queuelen 1000

    RX bytes 72772373 (69.4 Mb)

    TX bytes 32288070 (30.7 Mb)

    Related topics

    Previous
    Next