This document uses the conventions described in this section.
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
RFC 5737: IPv4 Address Blocks Reserved for Documentation
RFC 3849: IPv6 Address Prefix Reserved for Documentation
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.|
|Button, menu, text box, field, or check box label||
From Minimum log level, select Notification.
config system dns
set primary <address_ipv4>
FortiWeb# diagnose hardware logdisk info
disk number: 1
disk size: 31.46GB
raid level: no raid exists
partition number: 1
mount status: read-write
HTTP connections are not secure and can be intercepted by a third party.
Enter a name for the remote VPN peer or client, such as
Go to VPN > IPSEC > Auto Key (IKE).
For details, see the FortiWeb Administration Guide: https://docs.fortinet.com/fortiweb/admin-guides.
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.