Example text files
Here are three examples of what a text file might look like.
Example 1: Device
device_list_ver=8
# Device definitions. The lines beginning with '+' are
# associated with the device, and will cause an error if they
# appear out-of-context.
device|10.0.0.74|top|FortiGate|admin||root|My description.|1|1|
+meta|bogosity|10|
+vdom|vdom01|root|
+vdom|vdom02|root|
+vdom|vdom03|root|
+vdom|vdom04|root|
device|10.0.0.75|bottom|FortiGate-400C|admin|password|adom01|Your description.|0|1|5.0|GA|FG400C2905550018|0|
+meta|bogosity|12|
+vdom|vdom01|adom01|
Example 2: ADOM
device_list_ver=8
# ADOM definitions. These are exported only from the root ADOM,
# and can only be imported in the root ADOM. Import will abort
# with an error if this is imported in a non-root ADOM.
# The lines beginning with '+' are associated with the
# last-defined ADOM, and will cause an error if they appear
# out-of-context.
adom|root|GMS|1|
+meta|tag|my domain|
adom|adom01|GMS|1|
+meta|tag|your domain|
Example 3: Device group
device_list_ver=8
# Group definitions. Groups will be created in the order they
# appear here, so subgroups must be defined first, followed by
# top-level groups. Only two levels of nesting are supported.
group|group01|My description.|root|
+member|bottom||
+member|top|vdom03|
group|group02|Another description.|root|
+meta|supervisor|Philip J. Fry|
+member|top|vdom01|
+member|top|vdom02|
+subgroup|group01|
group|group03||adom01|
+meta|supervisor|Bender B. Rodriguez|
| Proper logging must be implemented when importing a list. If any add / discovery fails, there must be appropriate event logs generated so you can trace what occurred. |