
About this document | Introduction |
Document conventions
The following document conventions are used in this guide:
•In the examples, private IP addresses are used for both private and public IP addresses.
•Notes and Cautions are used to provide important information:
Note: Highlights useful additional information.
Caution: Warns you about commands or procedures that could have unexpected or ! undesirable results including loss of data or damage to equipment.
Typographic conventions
Fortinet documentation uses the following typographical conventions:
Convention | Example |
|
|
Keyboard input | In the Gateway Name field, type a name for the remote VPN |
| peer or client (for example, Central_Office_1). |
CLI command syntax | execute restore config <filename_str> |
Document names | FortiMail Administration Guide |
|
|
File content | <HTML><HEAD><TITLE>Firewall |
| Authentication</TITLE></HEAD> |
| <BODY><H4>You must authenticate to use this |
| service.</H4> |
Menu commands | Go to |
| New. |
|
|
Program output | Welcome! |
Variables | • <xxx_str> indicates an ASCII string variable keyword. |
| • <xxx_integer> indicates an integer variable |
| keyword. |
| • <xxx_ipv4> indicates an IP address variable keyword. |
| • vertical bar and braces {} separate mutually exclusive |
| required keywords |
| For example: |
| set system opmode {gateway transparent |
| server} |
| This example indicates you can enter set system |
| opmode gateway or set system opmode |
| transparent or set system opmode server |
| FortiMail™ Secure Messaging Platform Version 3.0 MR4 CLI Reference |
16 |