Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Sample import files

Hosts, adapters, users, or devices can be imported through the hosts view using a .csv file. All of these items can be included in the same import file as long as the header row contains the appropriate database field names. Below are sample import files for each type as well as an import file containing records of all types.

Host import

The adap.mac field is required for this import.

adap.mac,siblings,adap.ip,host.owner,host.devType

00:13:CE:6C:56:75,00:13:CE:6C:56:75,192.168.20.45,Smith2010,Windows

00:15:70:D9:46:B0,00:15:70:D9:46:B0;00:15:70:D9:46:B1,,Orr2010,Linux

00:15:70:D9:46:B1,00:15:70:D9:46:B0;00:15:70:D9:46:B1,,Orr2010,Linux

Pingable device import

The adap.mac field is required for this import. The host.devType field is recommended to ensure that the correct icon displays. Use the host.topo field to display this device both in the Host View and Topology. Entering the name of the Topology container in the host.topo field triggers FortiNAC to display the device in the Topology. The device is automatically displayed in the Host View.

adap.mac,siblings,adap.ip,host.topo,host.devType

00:13:CE:6C:56:75,00:13:CE:6C:56:75,192.168.20.45,Blding_B,PBX

00:15:70:D9:46:B0,00:15:70:D9:46:B0,192.168.20.10,Blding_A,Camera

00:15:70:D9:46:B2,00:15:70:D9:46:B2,192.168.20.12,Blding_A,Printer

IP phone import

The adap.mac field is required for this import. The host.devType field is not required, however, since IP phones are treated differently to prevent dropped calls, it is recommended that you include this field.

adap.mac,host.devType

00:12:C2:6C:56:74,IP Phone

00:12:C2:D9:46:B0,IP Phone

User import

The user.uid field is required for this import.

user.uid,user.fn,user.ln

Hebert2010,Frank,Hebert

Miller2009,Tammy,Miller

Mixed record types import

When combining different record types into a single import file, all of the fields for each record type must exist in the header row. For fields that do not apply to a particular record type, you must still include commas. Required fields for each type must be included.

adap.mac,siblings,host.owner,host.devType,user.uid,user.fn,user.ln

,,,,Hebert2010,Frank,Hebert

00:12:C2:6C:56:74,,,IP Phone,,,

00:13:CE:6C:56:75,00:13:CE:6C:56:75,Smith2010,Windows,,,

Sample import files

Hosts, adapters, users, or devices can be imported through the hosts view using a .csv file. All of these items can be included in the same import file as long as the header row contains the appropriate database field names. Below are sample import files for each type as well as an import file containing records of all types.

Host import

The adap.mac field is required for this import.

adap.mac,siblings,adap.ip,host.owner,host.devType

00:13:CE:6C:56:75,00:13:CE:6C:56:75,192.168.20.45,Smith2010,Windows

00:15:70:D9:46:B0,00:15:70:D9:46:B0;00:15:70:D9:46:B1,,Orr2010,Linux

00:15:70:D9:46:B1,00:15:70:D9:46:B0;00:15:70:D9:46:B1,,Orr2010,Linux

Pingable device import

The adap.mac field is required for this import. The host.devType field is recommended to ensure that the correct icon displays. Use the host.topo field to display this device both in the Host View and Topology. Entering the name of the Topology container in the host.topo field triggers FortiNAC to display the device in the Topology. The device is automatically displayed in the Host View.

adap.mac,siblings,adap.ip,host.topo,host.devType

00:13:CE:6C:56:75,00:13:CE:6C:56:75,192.168.20.45,Blding_B,PBX

00:15:70:D9:46:B0,00:15:70:D9:46:B0,192.168.20.10,Blding_A,Camera

00:15:70:D9:46:B2,00:15:70:D9:46:B2,192.168.20.12,Blding_A,Printer

IP phone import

The adap.mac field is required for this import. The host.devType field is not required, however, since IP phones are treated differently to prevent dropped calls, it is recommended that you include this field.

adap.mac,host.devType

00:12:C2:6C:56:74,IP Phone

00:12:C2:D9:46:B0,IP Phone

User import

The user.uid field is required for this import.

user.uid,user.fn,user.ln

Hebert2010,Frank,Hebert

Miller2009,Tammy,Miller

Mixed record types import

When combining different record types into a single import file, all of the fields for each record type must exist in the header row. For fields that do not apply to a particular record type, you must still include commas. Required fields for each type must be included.

adap.mac,siblings,host.owner,host.devType,user.uid,user.fn,user.ln

,,,,Hebert2010,Frank,Hebert

00:12:C2:6C:56:74,,,IP Phone,,,

00:13:CE:6C:56:75,00:13:CE:6C:56:75,Smith2010,Windows,,,