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 7.2.9 CLI Reference
    7.2.9
    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

    Conventions

    Conventions

    This document uses the conventions described in this section.

    IP addresses

    To avoid IP conflicts that would occur if you used examples in this document with public IP addresses that belong to a real organization, the IP addresses used in this document are fictional. They belong to the private IP address ranges defined by these RFCs.

    RFC 1918: Address Allocation for Private Internets

    HTTPS://tools.ietf.org/html/rfc1918

    RFC 5737: IPv4 Address Blocks Reserved for Documentation

    HTTPS://tools.ietf.org/html/rfc5737

    RFC 3849: IPv6 Address Prefix Reserved for Documentation

    HTTPS://tools.ietf.org/html/rfc3849

    For example, even though a real network’s Internet-facing IP address would be routable on the public Internet, in this document’s examples, the IP address would be shown as a non-Internet-routable IP such as 192.0.2.108, 198.51.100.155, or 203.0.113.79.

    Cautions, notes, & tips

    This document uses the following guidance and styles for notes, tips and cautions.

    Warn you about procedures or feature behaviors that could have unexpected or undesirable results including loss of data or damage to equipment.
    Highlight important, possibly unexpected but non-destructive, details about a feature’s behavior.
    Present best practices, troubleshooting, performance tips, or alternative methods.

    Typographic conventions

    Convention Example
    Button, menu, text box, field, or check box label

    From Minimum log level, select Notification.
    CLI input

    config system dns

    set primary <address_ipv4>

    end
    CLI output

    FortiWeb# diagnose hardware logdisk info

    disk number: 1

    disk[0] size: 31.46GB

    raid level: no raid exists

    partition number: 1

    mount status: read-write
    Emphasis

    HTTP connections are not secure and can be intercepted by a third party.
    File content

    <HTML><HEAD><TITLE>Firewall Authentication</TITLE></HEAD>
    <BODY><H4>You must authenticate to use this service.</H4>
    Hyperlink

    HTTPS://support.fortinet.com

    Keyboard entry

    Enter a name for the remote VPN peer or client, such as Central_Office_1.
    Navigation

    Go to VPN > IPSEC > Auto Key (IKE).
    Publication

    For details, see the FortiWeb Administration Guide: HTTPS://docs.fortinet.com/fortiweb/admin-guides.

    Command syntax

    The CLI requires that you use valid syntax, and conform to expected input constraints. It will reject invalid commands.

    For command syntax conventions such as braces, brackets, and command constraints such as <address_ipv4>, see Notation.

    Previous
    Next

    Conventions

    Conventions

    This document uses the conventions described in this section.

    IP addresses

    To avoid IP conflicts that would occur if you used examples in this document with public IP addresses that belong to a real organization, the IP addresses used in this document are fictional. They belong to the private IP address ranges defined by these RFCs.

    RFC 1918: Address Allocation for Private Internets

    HTTPS://tools.ietf.org/html/rfc1918

    RFC 5737: IPv4 Address Blocks Reserved for Documentation

    HTTPS://tools.ietf.org/html/rfc5737

    RFC 3849: IPv6 Address Prefix Reserved for Documentation

    HTTPS://tools.ietf.org/html/rfc3849

    For example, even though a real network’s Internet-facing IP address would be routable on the public Internet, in this document’s examples, the IP address would be shown as a non-Internet-routable IP such as 192.0.2.108, 198.51.100.155, or 203.0.113.79.

    Cautions, notes, & tips

    This document uses the following guidance and styles for notes, tips and cautions.

    Warn you about procedures or feature behaviors that could have unexpected or undesirable results including loss of data or damage to equipment.
    Highlight important, possibly unexpected but non-destructive, details about a feature’s behavior.
    Present best practices, troubleshooting, performance tips, or alternative methods.

    Typographic conventions

    Convention Example
    Button, menu, text box, field, or check box label

    From Minimum log level, select Notification.
    CLI input

    config system dns

    set primary <address_ipv4>

    end
    CLI output

    FortiWeb# diagnose hardware logdisk info

    disk number: 1

    disk[0] size: 31.46GB

    raid level: no raid exists

    partition number: 1

    mount status: read-write
    Emphasis

    HTTP connections are not secure and can be intercepted by a third party.
    File content

    <HTML><HEAD><TITLE>Firewall Authentication</TITLE></HEAD>
    <BODY><H4>You must authenticate to use this service.</H4>
    Hyperlink

    HTTPS://support.fortinet.com

    Keyboard entry

    Enter a name for the remote VPN peer or client, such as Central_Office_1.
    Navigation

    Go to VPN > IPSEC > Auto Key (IKE).
    Publication

    For details, see the FortiWeb Administration Guide: HTTPS://docs.fortinet.com/fortiweb/admin-guides.

    Command syntax

    The CLI requires that you use valid syntax, and conform to expected input constraints. It will reject invalid commands.

    For command syntax conventions such as braces, brackets, and command constraints such as <address_ipv4>, see Notation.

    Previous
    Next