Document conventions
Fortinet technical documentation uses the conventions described below.
IP addresses
To avoid publication of public IP addresses that belong to Fortinet or any other organization, the IP addresses used in Fortinet technical documentation are fictional and follow the documentation guidelines specific to Fortinet. The addresses used are from the private IP address ranges defined in RFC 1918: Address Allocation for Private Internets, available at
Most of the examples in this document use the following IP addressing:
•IP addresses are made up of A.B.C.D
•A - can be one of 192, 172, or 10 - the
•B - 168, or the branch / device / virtual device number.
•Branch number can be 0xx, 1xx, 2xx - 0 is Head office, 1 is remote, 2 is other.
•Device or virtual device - allows multiple FortiGate units in this address space (VDOMs).
•Devices can be from x01 to x99.
•C - interface - FortiGate units can have up to 40 interfaces, potentially more than one on the same subnet
•001 - 099- physical address ports, and non
•
•D - usage based addresses, this part is determined by what device is doing
•The following gives 16 reserved, 140 users, and 100 servers in the subnet.
•001 - 009 - reserved for networking hardware, like routers, gateways, etc.
•010 - 099 - DHCP range - users
•100 - 109 - FortiGate devices - typically only use 100
•110 - 199 - servers in general (see later for details)
•200 - 249 - static range - users
•250 - 255 - reserved (255 is broadcast, 000 not used)
•The D segment servers can be farther broken down into:
•110 - 119 - Email servers
•120 - 129 - Web servers
•130 - 139 - Syslog servers
•140 - 149 - Authentication (RADIUS, LDAP, TACACS+, FSAE, etc)
•150 - 159 - VoIP / SIP servers / managers
•160 - 169 - FortiAnalyzers
•170 - 179 - FortiManagers
•180 - 189 - Other Fortinet products (FortiScan, FortiDB, etc.)
•190 - 199 - Other
•Fortinet products,
FortiGate Voice Version 4.0 MR1 Administration Guide