nios_csv_ref_6.2
DESCRIPTION
nios csv guideTRANSCRIPT
Infoblox CSV Import Reference
NIOS 6.2
for Infoblox Core Network Services Appliances
Copyright Statements© 2011, Infoblox Inc.— All rights reserved.The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior
written permission of Infoblox, Inc.
The information in this document is subject to change without notice. Infoblox, Inc. shall not be liable for any
damages resulting from technical errors or omissions which may be present in this document, or from use of this
document.
This document is an unpublished work protected by the United States copyright laws and is proprietary to Infoblox,
Inc. Disclosure, copying, reproduction, merger, translation, modification, enhancement, or use of this document by
anyone other than authorized employees, authorized users, or licensees of Infoblox, Inc. without the prior written
consent of Infoblox, Inc. is prohibited.
For Open Source Copyright information, refer to the Infoblox Administrator Guide.
Trademark StatementsInfoblox, the Infoblox logo, Grid, NIOS, bloxTools, NetMRI and PortIQ are trademarks or registered trademarks of
Infoblox Inc.
All other trademarked names used herein are the properties of their respective owners and are used for identification
purposes only.
Company InformationInfoblox is located at:4750 Patrick Henry DriveSanta Clara, CA 95054-1851, USA
Web: www.infoblox.comsupport.infoblox.com
Phone: 408.625.4200 Toll Free: 888.463.6259 Outside North America: +1.408.716.4300 Fax: 408.625.4201
Product InformationHardware Models: Infoblox-250-A, -550-A, -1050-A, -1550-A, -1552-A, -1852-A, -2000-A, and -4010
Document Number: 400-0374-000 Rev. A
Document Updated: July 25, 2011
Warranty InformationYour purchase includes a 90-day software warranty and a one year limited warranty on the Infoblox appliance, plus
an Infoblox Warranty Support Plan and Technical Support. For more information about Infoblox Warranty information,
refer to the Infoblox Web site, or contact Infoblox Technical Support.
Preface
This preface describes the document conventions of this guide, and provides information about how to find
additional product information, including accessing Infoblox Technical Support. It includes the following sections:
• Document Overview on page 4
— Documentation Conventions on page 4
• Related Documentation on page 4
• Customer Care on page 5
— User Accounts on page 5
— Software Upgrades on page 5
— Technical Support on page 5
NIOS 6.2 CSV Import Reference (Rev. A) 3
Preface
Document Overview
The CSV import reference provides general guidelines and file format information about CSV import. It was last
updated on July 25, 2011. For updated documentation, visit our Support site at
http://www.infoblox.com/en/support/support-center-login.html
Documentation Conventions
The text in this guide follows the following style conventions.
Related Documentation
Other Infoblox appliance documentation:
• Infoblox CLI Guide
• Infoblox API Documentation
• Infoblox NIOS Administrator Guide
• Infoblox IBOS Administrator Guide
• Infoblox-500, Infoblox-1000 and Infoblox-1200 Quick Start
• Infoblox User Guide for the Infoblox-1050, 1550, and 1552 Appliances
• Infoblox User Guide for the Infoblox-500, -550 Appliance
• Infoblox Installation Guide for the Infoblox-550, -1050, -1550, and -1552 Appliances
• Infoblox Installation Guide for the Infoblox-550-A, -1050-A, -1550-A, and -1552-A Appliances
• Infoblox Installation Guide for the Infoblox-1852-A Appliance
• Infoblox Installation Guide for the Infoblox-250 Appliance
• Infoblox Installation Guide for the Infoblox-250-A Appliance
• Infoblox Installation Guide for the Infoblox-2000 Appliance
• Infoblox Installation Guide for the Infoblox-2000-A Appliance
• Infoblox Installation Guide for the Infoblox-4010 Appliance
• Quick Start Guide for Installing vNIOS Software on Riverbed Services Platforms
• Quick Start Guide for Installing vNIOS Software on Cisco Application eXtension Platforms
• Infoblox Installation Guide for vNIOS Software on VMware
• Quick Start Guide for Installing vIBOS Software on VMware Platforms
• Infoblox Safety Guide
To provide feedback on any of the Infoblox technical documents, please e-mail [email protected].
Style Usage
bold Indicates examples of the field names.
data Signifies the data in a CSV file.
4 CSV Import Reference (Rev. A) NIOS 6.2
Customer Care
Customer Care
This section addresses user accounts, software upgrades, licenses and warranties, and technical support.
User Accounts
The Infoblox appliance ships with a default user name and password. Change the default admin account password
immediately after the system is installed to safeguard its use. Make sure that the NIOS appliance has at least one
administrator account with superuser privileges at all times, and keep a record of your account information in a safe
place. If you lose the admin account password, and did not already create another superuser account, the system will
need to be reset to factory defaults, causing you to lose all existing data on the NIOS appliance. You can create new
administrator accounts, with or without superuser privileges. For more information, refer to the Infoblox Administrator Guide.
Software Upgrades
Software upgrades are available according to the Terms of Sale for your system. Infoblox notifies you when an
upgrade is available. Register immediately with Infoblox Technical Support at
http://www.infoblox.com/en/support/product-registration.html to maximize your Technical Support.
Technical Support
Infoblox Technical Support provides assistance via the Web, e-mail, and telephone. The Infoblox Support web site at
http://www.infoblox.com/en/support/support-center-login.html provides access to product documentation and
release notes, but requires the user ID and password you receive when you register your product online at:
http://www.infoblox.com/en/support/product-registration.html.
NIOS 6.2 CSV Import Reference (Rev. A) 5
Preface
6 CSV Import Reference (Rev. A) NIOS 6.2
Chapter 1 CSV Import Reference
This chapter provides general guidelines and file format information about each supported object type for CSV
import. You must follow the format and syntax described in this section to ensure a successful data import.
This appendix includes the following sections:
• Guidelines for CSV Import on page 7
— General Guidelines on page 7
— Data Specific Guidelines on page 8
• CSV File Format on page 9
• Supported Object Types on page 11
Guidelines for CSV Import
You can create a data file using a text editor, such as Microsoft Notepad, or an application that supports CSV file
format, such as Microsoft Excel.
General Guidelines
Follow these rules to start a data file:
• Specify the version number in the first line of the data file. For example, enter “version 1.0” in the first line.
• Use a new line to enter data for each row. Separate each data field with a supported separator, such as a
comma, semicolon, space, or tab.
• Do not include blank lines in the data file
• Field names: Specify the field names in the second line. You can include multiple rows of field names as long as
you define the fields before the data. The first column in the field name row must be defined as “Header.” The
rest of the columns are field names of the data. Columns without a field name are ignored. If multiple field
names are specified, the latest field names are used to import the data.
• Use the overwrite function, not the merge function, to overwrite existing data. When you use the merge function,
the appliance does not overwrite existing data, even if the data file contains new data.
• When you import a small file, the appliance processes the import quickly. Under this circumstance, the
appliance may generate an error message when you try to stop the import because the import is completed
before you can stop it.
• When you stop an import, the appliance finishes importing the data row that it is currently processing before it
stops the import.
• The error files of the last two imports are stored on the appliance. You can download these files using the API
import_id method. For information, refer to the Infoblox API Documentation.
NIOS 6.2 CSV Import Reference (Rev. A) 7
CSV Import Reference
• When you use Microsoft Excel to create or view a data file, ensure that you review the settings of the file. Some
data, such as dates, may show up in a different format depending on your settings.
• All operations triggered by a CSV import are recorded in the audit log.
Data Specific Guidelines
Follow these guidelines to enter data:
• The appliance uses double quotes (“) as the escape characters in CSV import. If you want to include supported
separators in a field, you must enclose the data in a pair of double quotes (“ “). This applies to the field names
and data. For example, if you want to use the field name ADMGRP-CSV ,; Import, you must enter “ADMGRP-CSV
,; Import” as the value. Otherwise, the import fails. When you enter “123””123”, the imported data is
123””123, and when you enter “\\”, the imported data is \\.
• If you have an empty value in the last field, you must still include the separator at the end of the data row.
Otherwise, the corresponding column and all its data are not imported, and the appliance generates an error.
• For each supported object type, you must include all the required fields in the data file. For information, see
Supported Object Types on page 11. Note that all required fields are marked with an asterisk (*) in an exported
file.
Note: If you want to modify a required field XXX (for either the overwrite or merge function), you must add a
corresponding field, _new_XXX, to include the new value. For example, “fqdn” is a required field in an A
record. If you want to update this field, you must include a new field “_new_fqdn” and define the new
value here. The appliance overwrites the existing data in the required field using the values you specify in
the new field.
• When you perform an overwrite function, you must define all boolean and integer data types in each supported
object type in order for the appliance to overwrite existing data.
• You can perform a CSV import of an object even if it has been scheduled for addition, modification, or deletion.
• Inherited fields: The appliance uses the following conventions to override inherited fields:
— When a value is specified in a field, the appliance overrides the inherited value with the new value.
— When a value is set to “ “ or an empty value, the appliance does not override the inherited value.
— When a value is set to a string with a value of \<empty\>, the appliance overrides the inherited value with an
empty value.
• Extensible attributes: A field name of EA-XXX indicates an extensible attribute, where XXX is the attribute name.
The value of an extensible attribute can be a string, a list, an integer, an email address, a URL, or a date in
YYYY-MM-DD format. Note that extensible attributes do not support time zones. Following are some examples:
• “EA-Site” is a predefined string type for locations. It can have a value of “Santa Clara”.
• “EA-User” is a user defined list type for employee types. It can have a list of values, such as
“Local,Remote,Temp”. Note that only one value can be specified when importing the extensible attribute.
• “EA-Building” is a predefined integer type for building numbers. It can have a value of “5”.
• “EA-TechPubs” is a user defined email address type. It can have a value of “[email protected]”.
• “EA-IB” is a user defined URL type. It can have a value of “www.infoblox.com”.
• “EA-Date” is a user defined date type attribute. It can have a value of “2010-11-20”.
• Admin permissions: A field name of ADMGRP-XXX indicates the admin permission of a specific admin group,
where XXX is the name of the admin group. The value of an admin permission can be a string or a list of strings
with subtypes. If there is a single value in the permission, use RW, RO, or DENY. If there is a subtype in the
permission, use a list format, such as “RW, ARecord/RO”.
• DHCP options: A field name of OPTION-XXX-nn indicates a DHCP option, where XXX is the vendor name of the
option and nn is the option number. If the option is of the DHCP vendor class, you can omit -XXX in the field
name. For example, OPTION-1 implies vendor class = DHCP and option number = 1, and OPTION-CISCO-122
implies vendor class = CISCO and option number = 122.
8 CSV Import Reference (Rev. A) NIOS 6.2
CSV File Format
CSV File Format
A CSV file is typically created and edited using a spreadsheet, though you can create a CSV file in a text editor using
any supported separator. You can include more than one object type in a single CSV file when you add or modify data.
For information, see Supported Object Types on page 11. You can also organize field names and data in a CSV file
using different formats, as shown in the following examples. For additional information about how to create a CSV
file, see Guidelines for CSV Import on page 7.
You can create one CSV file to update data of multiple object types (Network and Host Record), as illustrated in CSV File Example 1. In this example, you define the field names you want to modify for the two object types in rows 1 and
2. You then include the corresponding data as shown in rows 3 to 6.
Table 1.1 CSV File Example 1
In CSV File Example 1, the field name HEADER-NETWORK identifies the first row as a header row for the Network
objects. The field names ADDRESS, NETMASK, EA-Gateway, and EA-Secondary Address (in rows B1 to E1) tell NIOS
how to interpret a row of network data in the CSV file. Each row of data that begins with “Network” in column A is
identified as a network data row. Therefore, NIOS interprets rows 3 and 4 as network data rows, in which column B
contains the network addresses, column C contains the network masks, and columns D and E contain extensible
attribute values for gateway and secondary address.
Similarly, the field name HEADER-HostRecord identifies the second row as a header row for the Host Record objects.
This header declaration tells NIOS that for each subsequent row of data that begins with “HostRecord” in column A,
column B contains the FQDN of the host, and column C contains the host address. Therefore, NIOS interprets rows 5
and 6 as host record data rows that contain the FQDNs of the hosts in column B and the host addresses in column C.
Alternatively, you can organize the information in CSV File Example 1 so that the data rows immediately follow the
header rows, as shown in CSV File Example 2.
Table 1.2 CSV File Example 2
A B C D E
1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address
2 HEADER-HostRecord FQDN* ADDRESSES
3 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
4 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
5 HostRecord host1.dhcp.corp100.com 172.20.2.21
6 HostRecord host2.dhcp.corp100.com 172.20.2.22
A B C D E
1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-HostRecord FQDN* ADDRESSES
5 HostRecord host1.dhcp.corp100.com 172.20.2.21
6 HostRecord host2.dhcp.corp100.com 172.20.2.22
NIOS 6.2 CSV Import Reference (Rev. A) 9
CSV Import Reference
You can also specify multiple header declarations for the same object type, as shown in CSV File Example 3. In this
example, you specify the field names (in row 1) and data (in rows 2 and 3) to modify the extensible attributes
(EA-Gateway and EA-Secondary Address) of two network addresses. You then specify the field names (in row 4) and
data (in rows 5 and 6) to add new extensible attributes (EA-Gateway and EA-Host Range) of two other network
addresses.
Table 1.3 CSV File Example 3
The examples in this section are illustrated using tables that resemble spreadsheet layouts. However, all other
examples in this appendix use the comma separated value text file format. For example, the following is the CSV file
notation equivalent of CSV File Example 2 on page 9.
HEADER-NETWORK,ADDRESS*,NETMASK*,EA-Gateway,EA-Secondary Address
NETWORK,10.251.133.128,255.255.255.192,10.251.133.129
NETWORK,10.176.80.255,255.255.252.0,10.176.80.1,172.16.213.0
HEADER-HostRecord,FQDN*,ADDRESSES
HostRecord,host1.dhcp.corp100.com,172.20.2.21
HostRecord,host2.dhcp.corp100.com,172.20.2.22
A B C D E
1 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Secondary Address
2 NETWORK 10.251.133.128 255.255.255.192 10.251.133.129
3 NETWORK 10.176.80.255 255.255.252.0 10.176.80.1 172.16.213.0
4 HEADER-NETWORK ADDRESS* NETMASK* EA-Gateway EA-Host Range
5 NETWORK 10.176.90.0 255.255.255.128 10.176.90.1 10.176.90.4-126
6 NETWORK 10.176.90.128 255.255.255.128 10.176.90.129 10.176.90.132-254
10 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Supported Object Types
This section describes the supported object types and their corresponding fields for CSV import and export. It also
includes examples of how to create data files. Ensure that you review this information before you import or export a
data file.
Note: All inherited fields follow the override conventions described in Data Specific Guidelines on page 8.
Table 1.4 Supported DNS Object Types
Table 1.5 Supported DHCP Object Types
DNS Object Type Required Fields & Syntax
Authoritative Zone Authoritative DNS Zone on page 12.
A Record A Record on page 15
AAAA Record AAAA Record on page 17
CNAME Record CNAME Record on page 18
DNAME Record DNAME Record on page 19
MX Record MX Record on page 20
NAPTR Record NAPTR Record on page 22
NS Record NS Record on page 23
PTR Record PTR Record on page 25
SRV Record SRV Record on page 27
TXT Record TXT Record on page 26
Host Record Host Record on page 29
IPv4 Host Address IPv4 Host Address on page 31
IPv6 Host Address IPv6 Host Address on page 33
Rulesets NXDOMAIN and Blacklist Rulesets on page 35
NXDOMAIN Rule NXDOMAIN Rule on page 36
Blacklist Rule Blacklist Rule on page 36
DNS64 Synthesis Group DNS64 Synthesis Group on page 37
DHCP Object Type Required Fields & Syntax
IPv4 Network IPv4 Network on page 38
IPv6 Network IPv6 Network on page 41
IPv4 Shared Network IPv4 Shared Network on page 43
IPv6 Shared Network IPv6 Shared Network on page 45
IPv4 DHCP Range IPv4 DHCP Range on page 47
NIOS 6.2 CSV Import Reference (Rev. A) 11
CSV Import Reference
Authoritative DNS Zone
IPv6 DHCP Range IPv6 DHCP Range on page 51
IPv4 Fixed Address and Reservation IPv4 Fixed Address/Reservation on page 52
IPv6 Fixed Address IPv6 Fixed Address on page 55
DHCP MAC Filter DHCP MAC Filter on page 57
MAC Filter Address Item MAC Filter Address on page 58
Option Filter Option Filter on page 60
Option Filter Match Rule Option Filter Match Rule on page 61
Relay Agent Filter Relay Agent Filter on page 63
NAC Filter NAC Filter on page 64
IPv4 Option Space IPv4 Option Space on page 65
IPv6 Option Space IPv6 Option Space on page 66
IPv4 Option Definition IPv4 Option Definition on page 66
IPv6 Option Definition IPv6 Option Definition on page 67
Field Name Data TypeRequired (Yes/N0)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-AuthZone String Yes
fqdn FQDN Yes Name name Example: test.com
zone_format String Yes Valid values are FORWARD, IPV4,and IPV6
view String No DNS view views If no view is specified, the Default view is used.
prefix String No prefix Prefix is used for reverse-mapping RFC2317
zones only. If you include a prefix in a
forward-mapping zone, the appliance ignores
the prefix. No error message is generated.
_new_prefix String No Add this field to overwrite the prefix field when
you select the overwrite or merge option.
grid_primary Grid member No Grid Primary primary Use the hostname of the grid member in this
field. Example: infoblox.localdomain
grid_primary_stealth Boolean No Stealth stealth Example: FALSE
external_primaries Server list No External
Primary
primary Data must be in the following format:
“name/ip/stealth/use_2x_tsig/use_tsig/tsig_name/tsig_key”. Only name and ip are required fields. If no
value is specified for stealth, use_2x_tsig, and
use_tsig, the default value FALSE is used. If
either use_2x_tsig or use_tsig is TRUE,
tsig_name and tsig_key are required. If both
use_2x_tsig and use_tsig are TRUE, only
use_tsig = TRUE and the tsig key name and key
are imported. Example: "ext1.test.com/1.1.1.1/FALSE"
DHCP Object Type Required Fields & Syntax
12 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
grid_secondaries Member
server list
No Grid
Secondary
secondaries Data must be in the following format:
“hostname/stealth/lead/grid_ replicate”.
Only hostname is required. If you do not
specify values for stealth, lead, and
grid_replicate, the default value FALSE is used.Example: "member1.localdomain/FALSE
/TRUE/FALSE"
external_secondaries Server list No External
Secondary
secondaries Data must be in the following format:
“name/ip/stealth/use_2x_tsig/use_tsig/tsig_name/tsig_key”. Only name and ip
are required fields. If no value is specified for
stealth, use_2x_tsig, and use_tsig, the default
value FALSE is used. If either use_2x_tsig or
use_tsig is TRUE, tsig_name and tsig_key are
required. If both use_2x_tsig and use_tsig are
TRUE, only use_tsig = TRUE and the tsig key
name and key are imported. Example: "sec1.com/1.1.1.1/FALSE/FALSE/FALSE/foo/sdfssdf86ew"
ns_group String No Name server
group
ns_group Example: name-ns-group1
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
create_underscore_zones
Boolean No Automatically
create
underscore
zones
create_underscore_zones
Example: FALSE
allow_active_dir List of IP
addresses
No Allow
unsigned
updates from
these domain
controllers
enable_ad_server The Valid value is a list of IP addresses.
Example: “1.1.1.1, 10.0.0.1”
soa_refresh Unsigned
integer
No Refresh soa_refresh When you modify this field to override an
inherited value, you must include values for all
SOA timer fields. The appliance updates all the
SOA timers when you update any of them.
soa_retry Unsigned
integer
No Retry soa_retry Ensure that you include this field when you
override the soa_refresh field.
soa_expire Unsigned
integer
No Expire soa_expire Ensure that you include this field when you
override the soa_refresh field.
soa_default_ttl Unsigned
integer
No Default TTL soa_default_ttl Ensure that you include this field when you
override the soa_refresh field.
soa_negative_ttl Unsigned
integer
No Negative-
caching TTL
soa_negative_ttl Ensure that you include this field when you
override the soa_refresh field.
soa_mname FQDN No SOA MNAME
field
soa_mname Example: infoblox.localdomain
soa_email Email
address
No Email address
for SOA
MNAME field
soa_email Example: [email protected]
soa_serial_number Unsigned
integer
No Serial Number soa_serial_number
disable_forwarding Boolean No Don’t user
forwarders...
disable_forwarding Example: TRUE
Field Name Data TypeRequired (Yes/N0)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 13
CSV Import Reference
Examples
This section contains examples of how to create data files for DNS zones. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding DNS Zones
This example shows how to add a forward mapping zone, corp100.com, with a grid primary and a grid secondary,
where the gird secondary = hostname/stealth/lead/grid_replicate.
header-authzone,fqdn*,zone_format*,comment,grid_primary,grid_primary_stealth,grid_secondaries
authzone,corp100.com,FORWARD,USA,grid.infoblox.com,FALSE,member.infoblox.com/False/False
allow_update_forwarding
Boolean No Allow updates
from
forward_to Example: FALSE
update_forwarding ACL No Allow updates
from...
Permission
table
forward_to Data must be in the following formats: ip address/permissionnetwork/network cidr/permissionANY/permissionTSIG-XXX/permissionPermission can be ALLOW or DENY
If the first value is not Any or TSIG-, it is
assumed to be an IP or network address.Example:
"10.0.0.10/Allow,11.0.0.0/16/Deny,TSIG-foo
/sdfdsfwhsdgfsw8sdf/Allow"
allow_transfer ACL No Allow zone
transfers to
allow_transfer Example: "12.0.0.12/Deny,1234::/64/Allow"
allow_update ACL No Allow updates
from
allow_update Example: “13.0.0.0/8/Allow”
allow_query ACL No Allow queries
from
allow_query Example: “127.0.0.1/Allow”
notify_delay Unsigned
integer
No notify_delay This field specifies the seconds of delay the
notify messages are sent to the secondaries.
The valid value is between 5 and 86400
seconds.Example: 10
EA-Site String No Extensible
attribute
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and examples,
see Data Specific Guidelines on page 8.
EA-Users List No Extensible
attribute
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an admin
permission of a specific admin group. For
information about data format and examples,
see Data Specific Guidelines on page 8.
Field Name Data TypeRequired (Yes/N0)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
14 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
This example shows how to create a data file to add an IPv4 reverse mapping zone, 100.0.0.0/8, with a grid primary
and an external secondary, where the external secondary = name/ip/stealth/use_2x_tsig/use_tsig/tsig_name/tsig_key.
header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary,grid_primary_stealth
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/False/False/False/None/None,grid.infoblox.com,FALSE
This example shows how to create a data file to add an IPv6 reverse-mapping zone, 1234::/64, with an external
primary and a grid secondary, where the external primary = name/ip/stealth/use_2x_tsig/use_tsig/
tsig_name/tsig_key.
header-authzone,fqdn*,zone_format*,external_primaries,grid_secondaries
authzone,1234::/64,IPV6,ns1.com/1.1.1.1/False/False/False/None/None, member.infoblox.com/False/False/False
Overwriting DNS Zone Data
This example shows how to overwrite a comment from “USA” to “Japan” and remove the grid secondary.
header-authzone,fqdn*,zone_format*,comment,grid_primary,grid_primary_stealth,grid_secondaries
authzone,corp100.com,FORWARD,Japan,grid.infoblox.com,FALSE
This example shows how to overwrite a grid primary from “grid.infoblox.com” to “member.infoblox.com”.
header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary,grid_primary_stealth
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/False/False/False/None/None,member.infoblox.com,FALSE
Merging DNS Zone Data
This example shows how to merge the extensible attribute “Site” = “HQ” and add the RW permission to an admin
group “DNS_admins”.
header-authzone,fqdn*,zone_format*,ADMGRP-DNS_admins,EA-site
authzone,corp100.com,FORWARD,RW,HQ
This example shows how to add an external secondary with these values:
“ns3.com/2.2.2.2/False/False/False/None/None”.
header-authzone,fqdn*,zone_format*,external_secondaries,grid_primary,grid_primary_stealth
authzone,100.0.0.0/8,IPV4,ns2.com/2.2.2.2/False/False/False/None/None,ns3.com/2.2.2.2/False/False/False/None/None,FALSE
A Record
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
Header-ARecord String Yes Example: ARecord
fqdn FQDN Yes Name name This field combines the A record name
and the zone name to form the FQDN.
Example: a1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used.
NIOS 6.2 CSV Import Reference (Rev. A) 15
CSV Import Reference
Examples
This section contains examples of how to create data files for A records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding an A Record
This example shows how to add an A record, bind_a.corp100.com, with the extensible attribute Site = Infoblox, and
the permission, DNS_Adams = RO.
header-arecord,address*,fqdn*,ADMGRP-DNS_Admins,EA-Site
arecord,100.0.0.1,bind_a.corp100.com,RO,Infoblox
Overwriting A Record Data
This example shows how to to modify the permission of the admin group DNS_Adams from RO to DENY in an existing
A record, bind_a.corp100.com.
header-arecord,address*,fqdn*,ADMGRP-DNS_Admins
arecord,100.0.0.1,bind_a.corp100.com,DENY
Merging DNS Zone Data
This example shows how to merge the TTL value = 1280 to an existing A record, bind_a.corp100.com.
header-arecord,address*,fqdn*,ttl
arecord,100.0.0.1,bind_a.corp100.com,1280
address IP address Yes IP Address ipv4addr Example: 192.138.1.1
_new_address IP address No Add this field to overwrite the address
field when you select the overwrite or
merge option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 7200
EA-Site String No Extensible
attribute Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users List No Extensible
attribute Users
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
16 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
AAAA Record
Examples
This section contains examples of how to create data files for AAAA records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an AAAA Record
This example shows how to add an AAAA record, bind_aaaa.corp100.com, with a comment = add by superuser, and
TTL = 3600.
header-aaaarecord,address*,fqdn*,comment,ttl
aaaarecord,1234:1234::1,bind_aaaa.corp100.co,add by superuser,3600
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
Header-AaaaRecord String Yes Example: AaaaRecord
fqdn FQDN Yes Name zone This field combines the AAAA record
name and the zone name to form the
FQDN. Example: aaaa1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
address IPv6 address Yes IP Address ipv6addr Example: 100::10
_new_address IPv6 address No Add this field to overwrite the address
field when you select the overwrite or
merge option.
comment String No Comment comment
disabled Boolean No Disable disabled Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 7200
EA-Site String No Extensible
attribute Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users List No Extensible
attribute Users
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 17
CSV Import Reference
Overwriting AAAA Record Data
This example shows how to modify an existing AAAA record from address 1234:1234::1 to 1234:1234::2, and TTL
from 3600 to 3800.
header-aaaarecord,address*,_new_address,fqdn*,ttl
aaaarecord,1234:1234::1,1234:1234:2,bind_aaaa.corp100.com,3800
Merging AAAA Record Data
This example shows how to disable an existing AAAA record.
header-aaaarecord,address*,fqdn*,disabled
aaaarecord,1234:1234::2,bind_aaaa.corp100.com,TRUE
CNAME Record
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-CnameRecord String Yes Example: CnameRecord
fqdn FQDN Yes Alias zone This field combines the CNAME record
name and the zone name to form the
FQDN. Example: c1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
canonical_name Domain
name
Yes Canonical Name canonical Example: www.corp100.com
comment String No Comment comment
disabled Boolean No Disable disabled Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible
attribute Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
18 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for CNAME records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a CNAME Record
This example shows how to add a CNAME record, bind_cname.corp100.com, to the Default DNS view.
header-cnamerecord,fqdn*,canonical_name*,view
cnamerecord,bind_cname.corp100.com,somewhere.corp100.com,default
Overwriting CNAME Record Data
This example shows how to override a canonical name from somewhere.corp100.com to somewhere2.corp100.com.
header-cnamerecord,fqdn*,canonical_name*
cnamerecord,bind_cname.corp100.com,somewhere2.corp100.com
Merging CNAME Record Data
This example shows how to merge the following data: admin group DNS_Admins with RW permission and extensible
attribute Site = New York.
header-cnamerecord,fqdn*,ADMGRPDNS_Admins,EA-Site
cnamerecord,bind_cname.corp100.com,RW,New York
DNAME Record
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
Header-DnameRecord String Yes Example: DnameRecord
fqdn FQDN Yes Alias zone This field combines the DNAME record
name and the zone name to form the
FQDN. Example: d1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
target Domain
name
Yes Target target Example: d1.foo.com
comment String No Comment comment
disabled Boolean No Disable disabled Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible
attribute Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 19
CSV Import Reference
Examples
This section contains examples of how to create data files for DNAME records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a DNAME Record
This example shows how to add a DNAME record, bind_dname.corp100.com, with target =
bind_dname.corp200.com, extensible attribute Site = HQ, and disabled = TRUE.
header-dnamerecord,fqdn*,target*,disabled,EA-Site
dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,TRUE,HQ
Overwriting DNAME Record Data
This example shows how to enable the existing DNAME record, bind_dname.corp100.com, and add admin group
DNS_Adams with RO permission.
header-dnamerecord,fqdn*,target*,disabled,ADMGRPDNS_Admins
dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,FALSE,RO
Merging DNAME Record Data
This example shows how to add a comment to the existing DNAME record, bind_dname.corp100.com, and change
the TTL to 3860.
header-dnamerecord,fqdn,target*,comment,ttl
dnamerecord,bind_dname.corp100.com,bind_dname.corp200.com,Add by DNS admin,3860
MX Record
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
Header-MxRecord String Yes Example: MxRecord
fqdn FQDN Yes Mail
Destination
zone This field combines the MX record name
and the zone name to form the FQDN.
Example: MX1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
mx Domain
name
Yes Mail Exchange exchanger Example: mailer.foo.com
_new_mx Domain
name
No Add this field to overwrite the mx field
when you select the overwrite or merge
option.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
20 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for MX records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding an MX Record
This example shows how to add an MX record, bind_mx.corp100.com, with a mail exchanger, exchange.corp100.com
and priority = 20.
header-mxrecord,fqdn*,mx*,priority*
mxrecord,bind_mx.corp100.com,exchange.corp100.com,20
Overwriting MX Record Data
This example shows how to overwrite an existing MX record with a new fqdn, bind_mx2.corp100.com, and a new mail
exchanger, new_exchange.corp100.com.
header-mxrecord,fqdn*,_new_fqdn,mx*,_new_mx
mxrecord,bind_mx.corp100.com,bind_mx2.corp100.com,exchange.corp100.com,new_exchange.corp100.com
Merging MX Record Data
This example shows how to merge data to the existing MX record, bind_mx2.corp100.com, by adding inherited TTL
value and extensible attributes Site = USA.
header-mxrecord,fqdn*,mx*,priority*,ttl,EA-Site
mxrecord,bind_mx2.corp100.com,new_exchange.corp100.com,20,USA
priority Unsigned
integer
Yes Preference pref Example: 10
_new_priority Unsigned
integer
No Add this field to overwrite the priority
field when you select the overwrite or
merge option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible
attribute Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible
attribute
Country
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 21
CSV Import Reference
NAPTR Record
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-NaptrRecord String Yes Example: NaptrRecord
fqdn FQDN Yes Domain name This field combines the domain name and
the zone name to form the FQDN. Example: aptr1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
order Unsigned integer Yes Order order Example: 10
_new_order Unsigned integer No Add this field to overwrite the order field
when you select the overwrite or merge
option.
preference Unsigned integer Yes Preference preference Example: 20
_new_preference Unsigned integer No Add this field to overwrite the preference
field when you select the overwrite or
merge option.
flags String Yes Flags flags You can leave this field empty. Example: U
_new_flags String No Add this field to overwrite the flags field
when you select the overwrite or merge
option.
services String Yes Service services You can leave this field empty. Example: SIP+D2U
_new_services String No Add this field to overwrite the services field
when you select the overwrite or merge
option.
regexp String Yes REGEX regexp You can leave this field empty. Example: http://([^/:]+)!\1!i
_new_regexp String No Add this field to overwrite the regexp field
when you select the overwrite or merge
option.
replacement String Yes Replacement replacement Example: corp100.com
_new_replacement String No Add this field to overwrite the replacement
field when you select the overwrite or
merge option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned integer No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible
attribute Site
extensible_attrib
utes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines on
page 8.
22 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for NPATR records. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a NAPTR Record
This example shows how to add a NAPTR record, bind_naptr.corp100.com, with order = 10, preference = 20, and
replacement = corp200.com.
header-naptrrecord,fqdn*,order*,preference*,replacement*
naptrrecord,bind_naptr.corp100.com,10,20,corp200.com
Overwriting NAPTR Record Data
This example shows how to overwrite the FQDN of an existing NAPTR record from bind_naptr.corp100.com to
bind_naptr2.corp100.com.
header-naptrrecord,fqdn*,_new_fqdn order*,preference*,replacement*
naptrrecord,bind_naptr.corp100.com,bind_naptr2.corp100.com,10,20,corp200.com
This example shows how to override the preference of an existing NAPTR record from 20 to 25 and replacement from
corp200.com to corp300.com.
header-naptrrecord,fqdn*,order*,preference*,_new_preference,replacement*,_new_replacement
naptrrecord,bind_naptr.corp100.com,10 20 25,corp200.com,corp300.com
Merging NAPTR Record Data
This example shows how to merge Service = http+E2U and TTL = 3600 seconds to an existing NAPTR record.
header-naptrrecord,fqdn*,order*,preference*,replacement*,services,ttl
naptrrecord,bind_naptr.corp100.com,10,25,Corp300.com,http+E2U,3600
NS Record
EA-Users String No Extensible
attribute Country
extensible_attrib
utes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-NsRecord String Yes Example: NsRecord
fqdn FQDN Yes Zone name This field combines the domain name
and the zone name to form the FQDN.
Example: test.corp100.com
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 23
CSV Import Reference
Examples
This section contains examples of how to create data files for NS records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding an NS Record
This example shows how to add an NS record corp100.com in the Default DNS view with DNAME (name server) =
ns1.corp100.com, name server address = 100.0.0.101, and TRUE for adding a PTR Record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
nsrecord,corp100.com,default,ns1.corp100.com,“100.0.0.101/TRUE”
This example shows how to add an NS record corp200.com in the Internal DNS view with DNAME (name server) =
ns1.corp200.com and two name server addresses: 200.0.0.101 with TRUE for adding a PTR Record and 200.0.0.102
with TRUE for adding a PTR record.
header-nsrecord,fqdn*,view,dname*,zone_nameservers*
nsrecord,corp200.com,Internal,ns1.corp200.com,“200.0.0.101/TRUE,200.0.0.102/TRUE”
Overwriting NS Record Data
This example shows how to overwrite the DNAME of an existing NS record from ns1.corp100.com to
ns2.corp100.com.
header-nsrecord,fqdn*,dname*,_new_dname,zone_nameservers*
nsrecord,corp100.com,ns1.corp100.com,ns2.corp100.com,“100.0.0.101/TRUE”
This example shows how to overwrite the zone name servers of an existing NS record to 100.0.0.101/TRUE and
100.0.0.102/TRUE.
header-nsrecord,fqdn*,dname*,zone_nameservers*
nsrecord,corp100.com,ns2.corp100.com,“100.0.0.101/TRUE,100.0.0.102/TRUE”
Merging NS Record Data
This example shows how to merge zone name servers 100.0.0.101/TRUE and 100.0.0.102/TRUE to an NS record.
header-nsrecord,fqdn*,dname*,zone_nameservers*
nsrecord,corp200.com,ns1.corp200.com,“100.0.0.101/TRUE,100.0.0.102/TRUE”
dname Domain name Yes Name Server nameserver Example: ns1.corp100.com
_new_dname Domain name No Add this field to overwrite the dname
field when you select the overwrite or
merge option.
zone_nameservers Server list Yes Name server list addresses Data must be in the following format:
“IPAddress1/auto_create_ptr1,
IPAddress2/auto_create_ptr2”
Example: “10.0.0.4/TRUE,
10.0.0.44/FALSE, 10.0.0.55/TRUE”
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
24 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
PTR Record
Examples
This section contains examples of how to create data files for PTR records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding a PTR Record
This example shows how to add a PTR record.
header-ptrrecord,dname*,fqdn
ptrrecord,ptr.corp100.com,1.0.0.100.in-addr.arpa
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-PtrRecord String Yes Example: PtrRecord
fqdn FQDN No Domain Name namezone
This field is required if you do not use
the address field. Either the IP address
or FQDN is required. Example:
10.0.0.10.in.addr.arpa
_new_fqdn Reverse FQDN No Add this field to overwrite the fqdn
field when you use the overwrite or
merge option.
view String No DNS View views If no view is specified, the Default view
is used. Example: Default
address IP address No IP Address ipv4addripv6addr
This field is required if you do not use
the fqdn field. Either the IP address or
FQDN is required. Example: 10.0.0.11
_new_address IP address No Add this field to overwrite the address
field when you use the overwrite or
merge option.
dname FQDN Yes Name ptrdname Example: ss.dd.ff
_new_dname FQDN No Add this field to overwrite the dname
field when you select the overwrite or
merge option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field.Example: 28800
EA-Site String No Extensible attribute
Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file.
For information about data format and
examples, see Data Specific
Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data
format and examples, see Data
Specific Guidelines on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 25
CSV Import Reference
Overwriting PTR Record Data
This example shows how to overwrite an existing PTR record with a new FQDN, 2.0.0.100.in-addr.arpa.
header-ptrrecord,dname*,fqdn
ptrrecord,ptr.corp100.com,2.0.0.100.in-addr.arpaThis example shows how to overwrite an existing PTR record with a new IP address, 100.0.0.3.
header-ptrrecord,dname*,address
ptrrecord,ptr.corp100.com,100.0.0.3
Merging PTR Record Data
This example shows how to change the DNAME of a PTR record from ptr.corp100.com to ptr2.corp100.com, and to
add comment = East Asia.
header-ptrrecord,dname*,_new_dname,comment
ptrrecord,ptr.corp100.com,ptr2.corp100.com,East Asia
TXT Record
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-TxtRecord String Yes Example: TxtRecord
fqdn FQDN Yes Name namezone
This field combines the record name and
the zone name to form the FQDN.Example: t1.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
text String No Text text You can leave this field empty.
_new_txt String No Add this field to overwrite the txt field
when you select the overwrite or merge
option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible attribute
Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
26 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for TXT record data import. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a TXT Record
This example shows how to add a TXT record, bind_txt.corp100.com, with text = this is a TXT record and TTL set to
3600 seconds.
header-txtrecord,fqdn*,text,ttl
txtrecord,bind_txt.corp100.com,this is a TXT record,3600
Overwriting TXT Record Data
This example shows how to overwrite the text field of a TXT record.
header-txtrecord,fqdn*,text,_new_text
txtrecord,bind_txt.corp100.com,this is a TXT record,this is a new TXT record
Merging TXT Record Data
This example shows how to add comment = USA and disabled = TRUE to an existing TXT record.
header-txtrecord,fqdn*,text,comment,disabled
txtrecord,bind_txt.corp100.com,this is a TXT record,USA,TRUE
SRV Record
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-SrvRecord String Yes Example: SrvRecord
fqdn FQDN Yes Service namezone
This field combines the service name and the
zone name to form the FQDN.Example: _http._tcp.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field
when you select the overwrite or merge
option.
view String No DNS View views If no view is specified, the Default view is
used. Example: Default
priority Unsigned
integer
Yes Priority priority Example: 10
_new_priority Unsigned
integer
No Add this field to overwrite the priority field
when you select the overwrite or merge
option.
weight Unsigned
integer
Yes Weight weight Example: 20
_new_weight Unsigned
integer
No Add this field to overwrite the weight field
when you select the overwrite or merge
option.
port Unsigned
integer
Yes Port port Example: 80
_new_port Unsigned
integer
No Add this field to overwrite the port field when
you select the overwrite or merge option.
target Domain name Yes Target target Example: foo.test.com
NIOS 6.2 CSV Import Reference (Rev. A) 27
CSV Import Reference
Examples
This section contains examples of how to create data files for SRV records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding a SRV Record
This example shows how to add a new SRV record.
header-srvrecord,fqdn*,port*,priority*,target*,weight*
srvrecord,bind_srv.corp100.com,80,10,srv.corp100.com,20
Overwriting SRV Record Data
This example shows how to overwrite the following data of a SRV record: port from 80 to 88 and priority from 10 to 20.
header-srvrecord,fqdn*,port*,_new_port,priority*,_new_priority,target*,weight*
srvrecord,bind_srv.corp100.com,80,88,10,20,srv.corp100.com,20
This example shows how to overwrite the following data of a SRV record: target from srv.corp100.com to
srv2corp100.com and weight from 20 to 30.
header-srvrecord,fqdn*,port*,priority*,target*,_new_target,weight*,_new_weight
srvrecord,bind_srv.corp100.com,88,20,srv.corp100.com,sv2.corp100.com,20,30
Merging SRV Record Data
This example shows how to merge the following data to a SRV record: comment = USA and disabled = TRUE.
header-srvrecord,fqdn*,port*,priority*,target*,weight*,comment,disabled
srvrecord,bind_srv.corp100.com,80,10,srv.corp100.com,20,USA,TRUE
_new_target Domain name No Add this field to overwrite the target field
when you select the overwrite or merge
option.
comment String No Comment comment
disabled Boolean No Disable disable Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information, see
Data Specific Guidelines on page 8.Example: 28800
EA-Site String No Extensible
attribute Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines on
page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin group.
For information about data format and
examples, see Data Specific Guidelines on
page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
28 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Host Record
If only one IPv4 address is specified in the host record, you can add DHCP options to the host address.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-HostRecord String Yes Example: HostRecord
fqdn FQDN Yes Name namezone
This field combines the host record name and
the zone name to form the FQDN.Example: h2.corp100.com
_new_fqdn FQDN No Add this field to overwrite the fqdn field when
you select the overwrite or merge option.
view String No DNS View views If no view is specified, the Default view is used.
Example: Default
addresses IP address or IP
address list
No IP Addresses ipv4addr You must specify a value in this field or in the
ipv6_addresses field. Example: ‘1.2.3.4’ or
“1.2.3.4, 5.6.7.8”. If there are multiple
addresses in the host record, use HostAddress
to specify the parameters for each address. For
information, see IPv4 Host Address on page 31
and IPv6 Host Address on page 33.
ipv6_addresses IP address or IP
address list
No IP Addresses ipv6addr You must specify a value in this field or in the
addresses field. If there are multiple addresses
in the host record, use HostAddress to specify
the parameters for each address. For
information, see IPv4 Host Address on page 31
and IPv6 Host Address on page 33.
aliases Alias list No Aliases aliases Example: www.infoblox.com
configure_for_dns Boolean No Enable in DNS configure_for_dns
Example: TRUE
comment String No Comment comment
disabled Boolean No Disable disabled Example: FALSE
ttl Unsigned
integer
No TTL ttl This is an inherited field. For information, see
Data Specific Guidelines on page 8.Example: 28800
mac_address MAC address No MAC Address mac_address This field applies to the host address. This is
required if the IP address is configured for DHCP.
Example: aA:Bb:c2:DD:E1:FF
configure_for_dhcp Boolean No DHCP check box configure_for_dhcp
This field applies to the host address. Example: TRUE
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp This field applies to the host address. Example: FALSE
broadcast_address String No Broadcast
Address
This field applies to the host address.
boot_file String No Boot File boot_file This field applies to the host address.
boot_server String No Boot Server boot_server This field applies to the host address.
next_server String No Next Server next_server This field applies to the host address.
lease_time Unsigned
integer
No Lease Time lease_time This field applies to the host address.
pxe_lease_time_enabled
Boolean No Enable PXE
Lease Time
This field applies to the host address.
NIOS 6.2 CSV Import Reference (Rev. A) 29
CSV Import Reference
Examples
This section contains examples of how to create data files for host records. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding a Host Record
This example shows how to add a new host record, host1, in zone corp100.com and DNS view Initial.
header-hostrecord,addresses,fqdn*,view
hostrecord,100.0.0.101,host1.corp100.com,Inital
This example shows how to add a new host record, host2, in zone corp100.com with aliases = www.corp100.com,
comment = USA, and TTL = 3600 seconds.
header-hostrecord,addresses,fqdn*,aliases,comment,ttl
hostrecord,100.0.0.102,host2.corp100.com,www.corp100.com,USA,3600
Overwriting Host Record Data
This example shows how to overwrite the FQDN of an existing host record from host1.corp100.com to
new_host1.corp100.com, and to change the TTL to 128 seconds.
header-hostrecord,addresses,fqdn*,_new_fqdn,ttl
hostrecord,100.0.0.101,host1.corp100.com,new_host1.corp100.com,1280
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time This field applies to the host address.
domain_name FQDN No Domain Name domain_name This field applies to the host address.
domain_name_servers
IP list No Name Server This field applies to the host address.Example: “5.6.7.8,1.2.3.4”
routers IP list No Router This field applies to the host address.Example: “2.0.0.2,1.2.3.4”
match_option String No match_client This field applies to the host address. Data must
be in the following format:
MAC_ADDRESS/RESERVED
ignore_dhcp_param
_request_list
Boolean No Ignore
Optionalist
ignore-dhcp_option_list_request
This field applies to the host address.
OPTION-1 String No Custom DHCP
Options
options This field applies to the host address.Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
options This field applies to the host address.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, optioncode/number 200
EA-Site String No Extensible
attribute Site
extensible_attributes
EA-Site is an example of a predefined extensible
attribute. You can add other predefined
attributes to the data file. For information about
data format and examples, see Data Specific
Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an admin
permission of a specific admin group. For
information about data format and examples,
see Data Specific Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
30 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
This example shows how to overwrite the aliases of a host record from www.corp100.com to www.corp200.com and
comment from USA to Japan.
header-hostrecord,addresses*,fqdn*,aliases,comment
hostrecord,100.0.0.102,host2.corp100.com,www.corp200.com,Japan
Merging Host Record Data
This example shows how to disable an existing host record.
header-hostrecord,addresses*,fqdn*,disabled
hostrecord,100.0.0.101,new_host1.corp100.com,TRUE
This example shows how to add additional aliases to a host record.
header-hostrecord,addresses*,fqdn*,aliases
hostrecord,100.0.0.102,host2.corp100.com www.corp200.com,http.corp200.com
IPv4 Host Address
Use this object type to define parameters for each IP address in an IPv4 host record. The appliance updates an
existing host address when you use the “add” mode in an import. For information about host records, refer to the
Infoblox Administrator Guide.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-HostAddress String Yes Example: HostAddress
parent FQDN Yes Example: h1.corp100.com
view String No DNS View views If no view is specified, the Default view is used.
Example: Default
address IP address Yes IP Address ipv4addr Example: 10.0.0.11
_new_address IP address No Add this field to overwrite the address field
when you select the overwrite or merge option.
mac_address MAC address No MAC Address mac_address This is required if the IP address is configured
for DHCP. Example: aA:Bb:c2:DD:E1:FF
configure_for_dhcp Boolean No DHCP check box configure_for_dhcp
Example: TRUE
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp Example: FALSE
broadcast_address String No Broadcast
Address
boot_file String No Boot File boot_file
boot_server String No Boot Server boot_server
next_server String No Next Server next_server
lease_time Unsigned
integer
No Lease Time lease_time
pxe_lease_time_enabled
Boolean No Enable PXE Lease
Time
Example: TRUE
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time
domain_name FQDN No Domain Name domain_name
domain_name_servers
IP list No Name Server Example: [5.6.7.8,1.2.3.4]
NIOS 6.2 CSV Import Reference (Rev. A) 31
CSV Import Reference
Examples
This section contains examples of how to create data files for host addresses. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Host Address
This example shows how to import the host address 100.0.0.1 in host record h1.corp100.com with a MAC address,
enabled DHCP, and a domain name.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,domain_name
hostaddres,h1.corp100.com,100.0.0.1,aa:aa:aa:aa:aa:aa,TRUE,corp200.com
This example shows how to import the host address 100.0.0.2 in host record h2.corp100.com with a MAC address,
and two routers with addresses 1.1.1.1 and 2.2.2.2.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,routers
hostaddress,h2.corp100.com,100.0.0.2,bb:aa:aa:aa:aa:aa,False,1.1.1.1,2.2.2.2
Overwriting IPv4 Host Address Data
This example shows how to overwrite the MAC address and domain name of a host address, and to set configure
DHCP to TRUE.
header-hostaddress,parent*,address*,mac_address,configure_for_dhcp,domain_name
hostaddress,h1.corp100.com,100.0.0.1,cc:aa:aa:aa:aa:aa,FALSE,corp300.com
This example shows how to overwrite the router address of a host address from 1.1.1.1,2.2.2.2 to 1.1.1.1.
header-hostaddress,parent*,address*,routers
hostaddress,h2.corp100.com,100.0.0.2,1.1.1.1
Merging IPv4 Host Address Data
This example shows how to merge the following data of a host address: change a new address from 100.0.0.1 to
100.0.0.10, change bootp to DENY, and add lease time.
header-hostaddress,parent*,address*,_new_address,deny_bootp,lease_time
hostaddress,h1.corp100.com,100.0.0.1,100.0.10,FALSE,3600
routers IP list No Router Example: [2.0.0.2,1.2.3.4]
match_option String No match_client Data must be in the following format:
MAC_ADDRESS/CLIENT_IDENTIFIER/RESERVED
ignore_dhcp_param_
request_list
Boolean No Ignore Optionlist ignore-dhcp_option_list_request
OPTION-1 String No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines on
page 8.Example: ‘255.0.0.0’ implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines on
page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, optioncode/number 200
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
32 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
This example shows how to merge the broadcast address, PXE lease time, and enabled ignore option list to an IPv4
host address.
header-hostaddress,parent*,address*,broadcast_address,pxe_lease_time,ignore_dhcp_param_request_list
hostaddress,h2.corp100.com,100.0.0.2,6.6.6.6,1280,TRUE
IPv6 Host Address
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-IPv6HostAddress String Yes Example: IPv6hostaddress
view String No DNS View view If no view is specified, the Default view is
used. Example: Default
parent String Yes Example: 2000::/64
address_type Enumeration No address_type Valid values are ADDRESS, PREFIX, or BOTH. If
no value is specified, ‘ADDRESS’ (default) is
used. Example: PREFIX
address IPv6 address Yes IPv6 Address ipv6addr Example: 1001::001
_new_address IPv6 address No Add this field to overwrite the address field
when you select the overwrite or merge
option.
ipv6_prefix IPv6 prefix No ipv6prefix This field is required if address_type is
‘ADDRESS’ or ‘BOTH’.Example: 2000:1111::
_new_ipv6_prefix IPv6 prefix No Add this field to overwrite the ipv6_prefix field
when you select the overwrite or merge
option.
ipv6_prefix_bits Integer No IPv6_prefix_bits
This field is required if address_type is
‘ADDRESS’ or ‘BOTH’.Example: 32
configure_for_dhcp Boolean No DHCP check box configure_for_dhcp
Example: TRUE
match_option String No match_client Only ‘DUID’ is allowed.Example: DUID
duid String No DUID duid Example: 0001
domain_name FQDN No Domain Name
domain_name_servers IPv6 address
list
No Name Server Example: ‘2000::10,3000::10’
valid_lifetime Unsigned
integer
No Valid Lifetime valid_lifetime Example: 43200
preferred_lifetime Unsigned
integer
No Preferred
Lifetime
preferred_lifetime
Example: 604800
OPTION-7 Integer No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines on
page 8.Example: ‘12’ name implies option space =
‘DHCPv6’, option code/number 7
NIOS 6.2 CSV Import Reference (Rev. A) 33
CSV Import Reference
Examples
This section contains examples of how to create data files for IPv6 host addresses. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv6 Host Address
This example shows how to import an IPv6 host address to a host record in the Default DNS view.
header-IPv6hostaddress,parent*,address*,view
IPv6hostaddress,h1.corp100.com,1001::001,Default
Overwriting IPv6 Host Address Data
This example shows how to overwrite an IPv6 host address.
header-IPv6hostaddress,parent*,address*,_new_address
IPv6hostaddress,h1.corp100.com,1001::001,2000::10
Merging IPv6 Host Address Data
This example shows how to merge a DUID to an IPv6 host address.
header-IPv6hostaddress,parent*,address*,duid
IPv6hostaddress,h1.corp100.com,2000::10,0001
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines on
page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
34 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
NXDOMAIN and Blacklist Rulesets
Examples
This section contains examples of how to create data files for NXDOMAIN and blacklist rulesets. All examples use
comma as the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an NXDOMAIN Ruleset
This example shows how to import an NXDOMAIN ruleset.
header-Ruleset,name*,type*,comment,disabled
nxdomainruleset,NXD,NXDOMAIN,This is an NXDOMAIN ruleset,FALSE
Adding a Blacklist Ruleset
This example shows how to import a blacklist ruleset.
header-Ruleset,name*,type*,disabled,comment
blacklistruleset,blacklistrule1,BLACKLIST,FALSE,This is a blackset ruleset
Overwriting Blacklist Ruleset Data
This example shows how to overwrite the name of a blacklist ruleset.
header-Ruleset,name*,_new_name,type*
blacklistruleSet,blacklistrule1,blacklistrule2,BLACKLIST
Merging NXDOMAIN Ruleset Data
This example shows how to merge an admin permission to a NXDOMAIN ruleset.
header-Ruleset,name*,type*,ADMGRP-JoeSmith
nxdomainruleSet,NXD,NXDOMAIN,RW
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-Ruleset String Yes Example: Ruleset
name String Yes Name name Example: ruleset1
_new_name String No Example: ruleset1-new
type String Yes type You can use this field for NXDOMAIN rules or
blacklist rules. Valid value is NXDOMAIN or
BLACKLIST.
Example: NXDOMAIN
disabled Boolean No Disable disabled Example: FALSE
comment String No Comment comment
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an admin
permission of a specific admin group. For
information about data format and examples,
see Data Specific Guidelines on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 35
CSV Import Reference
NXDOMAIN Rule
Examples
This section contains examples of how to create data files for NXDOMAIN rules. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an NXDOMAIN Rule
This example shows how to import an NXDOMAIN rule.
header-nxdomainrule,action*,parent*,pattern*
nxdomainrule,REDIRECT,NXD,*foo.com
Overwriting NXDOMAIN Rule Data
This example shows how to overwrite the action of an NXDOMAIN rule.
header-nxdomainrule,action*,parent*,pattern*
nxdomainRule,REDIRCT,NXD,*bar.com
Blacklist Rule
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-nxdomainrule String Yes Example: NxdomainRule
parent String Yes Name nxdomain_rules This field indicates the ruleset to which the
NXDOMAIN rule belongs. Example:
nxdomain-ruleset1
pattern String Yes Pattern pattern Use this to match domain names. You cannot
use the characters * and ,, in the domain
name. Example: foo
_new_pattern String No Example: foo-new
action String Yes Action action The valid value is PASS or REDIRECT.
Example: PASS
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-blacklistrule String Yes Example: BlacklistRule
parent String Yes Name blacklist_rulesets Example: blacklist-ruleset1
domain_name String Yes Domain Name Use this to match domain names. You
cannot use the characters * and ,, in the
domain name. The domain name cannot
exceed 255 characters. Example:
www.foo.com
_new_domain_name String No Example: www.bar.com
action String Yes Action blacklist_action The valid value is PASS or REDIRECT.
Example: PASS
36 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for blacklist rules. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a Blacklist Rule
This example shows how to import a blacklist rule.
header-blacklistrule,parent*,domain_name*,action*
BlacklistRule,BlackList,foobar.com,REDIRECT
Overwriting Blacklist Rule Data
This example shows how to overwrite the action of a blacklist rule.
header-blacklistrule,parent*,domain_name*,action*
BlacklistRule,BlackList,foobar.com,PASS
DNS64 Synthesis Group
Examples
This section contains examples of how to create data files for DNS64 synthesis groups. All examples use comma as
the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a DNS64 Synthesis Group
This example shows how to import a DNS64 Synthesis Group.
header-Dns64SynthesisGroup,name*,prefix*,mappedDns64SynthesisGroup,DNS64Group1,64:FF9B::/96,10.0.0.0/8/Allow
Overwriting DNS64 Synthesis Group Data
This example shows how to overwrite the mapped IPv4 address of a DNS64 synthesis group.
header-Dns64SynthesisGroup,name*,prefix*,mappedDns64SynthesisGroup,DNS64Group1,64:FF9B::/96,10.1.1.0/24/Allow
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-Dns64Synthesis
Group
String Yes Example: Dns64SynthesisGroup
name String Yes Name name Example: group1
prefix IPv6 network Yes Prefix prefix Example: 64:FF9B::/96
comment String No Comment comment
clients Access
control list
No Name clients Valid values are IPv4 and IPv6 addresses and
networks only. The default value is ‘Any’.Example: 2000::/64/Allow
mapped Access
control list
No Mapped IPv4
Address ->
Name
mapped Valid values are IPv4 addresses and networks
only. The default value is ‘Any’.Example: 10.0.0.0/8/Allow
exclude Access
control list
No Excluded IPv6
Address ->
Name
exclude Valid values are IPv6 addresses and networks
only. The default is ‘None’. Example: 2000::/Allow
disabled Boolean No Disabled disable Example: FALSE
NIOS 6.2 CSV Import Reference (Rev. A) 37
CSV Import Reference
IPv4 Network
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Comments
Header-Network String Yes Example: Network
address IP address Yes Address network Example: 10.0.0.11
netmask Netmask Yes Netmask network Example: 255.255.0.0
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
comment String No Comment comment
auto_create_reversezone
Boolean No Automatically
create reverse
mapping zone
auto_create_reversezone
Example: TRUE
is_authoritative Boolean No Authoritative authority Example: FALSE
boot_file String No Boot File bootfile Example: bootfile1
boot_server String No Boot Server bootserver Example: abc.corp100.com
ddns_domainname
String No DDNS Domain
Name
ddns_domainname
Example: ddns.corp100.com
generate_hostname
Boolean No Generate Hostname ddns_generate_hostname
Example: TRUE
always_update_dns
Boolean No DNS Zones
Associations
ddns_server_always_updates
Example: FALSE
update_static_leases
Boolean No Fixed Address
Updates
ddns_update_fixed_
address
Example: FALSE
update_dns_on_lease_renewal
Boolean No Update DNS on
DHCP Lease
Renewal
override_update_dns_on_lease_renewal
Example: TRUE
ddns_ttl Unsigned
integer
No DDNS Update TTL ddns_ttl This is an inherited field. For information,
see Data Specific Guidelines on page 8.Example: 1200
enable_option81 Boolean No Option 81 Support ddns_use_option81 Example: TRUE
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp Example: FALSE
broadcast_address
String No Broadcast Address
disabled Boolean No Disabled disable Example: FALSE
enable_ddns Boolean No Enable DDNS
Updates
enable_ddns Example: FALSE
enable_thresholds Boolean No Enable DHCP
Thresholds
enable_dhcp_thresholds
When you set this field to TRUE, you must
enter values in the
range_high_water_mark and
range_low_water_mark fields. You cannot
leave those fields empty. Otherwise, the
appliance generates an error.
38 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
enable_threshold_
email_ warnings
Boolean No Enable Email
Warnings
enable_email_
warnings
When you use the merge function, the
appliance preserves the existing value in
this field. When you use the overwrite
function, you must include a value (TURE
or FALSE). Otherwise, the appliance
generates an error.Example: TRUE
enable_threshold_
snmp_ warnings
Boolean No Enable SNMP
Warnings
enable_snmp_
warnings
When you use the merge function, the
appliance preserves the existing value in
this field. When you use the overwrite
function, you must include a value (TURE
or FALSE). Otherwise, the appliance
generates an error.Example: TRUE
range_high_water
_mark
Integer No High Water Mark high_water_mark When you set enable_thresholds to TRUE,
you must enter values in this field and in
the range_low_water_mark field. You
cannot leave these fields empty.
Otherwise, the appliance generates an
error.
Example: 80
ignore_client_requested_
options
Boolean No Ignore Optionlist ignore_dhcp_option_list_request
Example: TRUE
range_low_water_
mark
Integer No Low Water Mark low_water_mark When you set enable_thresholds to TRUE,
you must enter values in this field and in
the range_high_water_mark field. You
cannot leave these fields empty.
Otherwise, the appliance generates an
error.
Example: 10
next_server String No Next Server nextserver Example: blue.domain.com
lease_time Unsigned
integer
No Lease Time Example: 1100
enable_pxe_lease
_time
Boolean No Enable PXE lease
time
Example: FALSE
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time Example: 1100
recycle_leases Boolean No Lease Deletion recycle_leases This field is set to TRUE by default. Ensure
that you use the overwrite option if you
want to change the value to FALSE.
Merging data from an import preserves the
default value.
threshold_email_addresses
address list
No Email Addresses Example:
"'[email protected]','[email protected]'"
dhcp_members Grid member
list
No Members members Example:
"host1.infoblox.com,host2.infoblox.com"
routers IP address
list
No Routers Example: "10.0.0.1,10.0.0.100,"
domain_name FQDN No Domain Name
domain_name_servers
IP address
list
No DNS Servers Example: "10.2.3.4,11.2.3.4"
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Comments
NIOS 6.2 CSV Import Reference (Rev. A) 39
CSV Import Reference
Examples
This section contains examples of how to create data files for networks. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Network
This example shows how to import network 100.0.0.0/24 in the network view External with auto create reverse zone
enabled and a comment.
header-network,address*,netmask*,network_view,auto_create_reversezone,comment
network,100.0.0.0,255.255.255.0,External,TRUE,This is comment field
Overwriting IPv4 Network Data
This example shows how to overwrite the following data in an existing network: enable the network to be
“authoritative” and to add boot files bppt_file_001 and boot server 1.2.3.4.
header-network,address*,netmask*,is_authoritative,boot_file,boot_server
network,100.0.0.0,255.255.255.0,True,boot_file_001,1.2.3.4
Merging IPv4 Network Data
This example shows how to merge the following data to an existing network: DDNS domain name, enable generate
hostname, and disable always update DNS.
header-network,address*,netmask*,ddns_domainname,generate_hostname,always_update_dns
network,100.0.0.0,255.255.255.0,ddns.corp100.com,TRUE,FALSE
zone_associations Zone list No Example: test.com/TRUE
OPTION-1 String No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8. Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible Attribute
Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible Attribute
User
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Comments
40 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
IPv6 Network
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-IPv6Network String Yes Example: IPv6Network
address IPv6 address Yes Address ipv6addr Example: 2001::
cidr Prefix Yes Netmask Example: 32
network_view String No Network View network_view If no view is specified, the Default
view is used. Example: Default
comment String No Comment comment Example: This is an IPv6 network.
disabled Boolean No Disabled disable Example: TRUE
auto_create_reversezone Boolean No Automatically
create
reverse-mapping
zone
auto_create_reversezone
Example: TRUE
zone_associations Zone list No DNS Zone
Associations
zone_associations
Example: test.com/TRUE
dhcp_members Grid member
list
No Members members Example: “host1.infoblox.com,
host2.infoblox.com
domain_name String No Domain Name Example: testdomain.com
domain_name_servers IP address list No Name Server Example: ‘2000::10,3000::10’
valid_lifetime Integer No Valid Lifetime valid_lifetime Example: 43200
Preferred_lifetime Integer No Preferred
Lifetime
preferred_lifetime
Example: 604800
recycle_leases Boolean No recycle_leases Example: FALSE
enable_ddns Boolean No Enable DDNS
Updates
enable_ddns Example: TRUE
always_update_dns Boolean No FQDN Support ddns_server_always_updates
Example: TRUE
ddns_domain_name String No DDNS Domain
Name
ddns_domainname
Example: ddnsdomain.com
ddns_ttl Unsigned
integer
No DDNS Update
TTL
ddns_ttl Example: 3600
generate_hostname Boolean No Generate
Hostname
override_ddns_generate_hostname
Example: TRUE
update_dns_on_lease_renewal Boolean No Lease Renewal
Update
override_update_dns_on_lease_renewal
Example: TRUE
OPTION-7 Integer No Custom DHCP
Options
override_options
This is an example of a DHCP option.
For information, see Data Specific
Guidelines on page 8.Example: ‘12’ name implies option
space = ‘DHCPv6’, option
code/number 7
NIOS 6.2 CSV Import Reference (Rev. A) 41
CSV Import Reference
Examples
This section contains examples of how to create data files for IPv6 networks. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv6 Network
This example shows how to import an IPv6 network 3333::/64 in the Default DHCP view.
header-IPv6network,address*,cidr*,network_view,comment,auto_create_reversezone
IPv6network,3333::,64,Default,This is a comment,TRUE
Overwriting IPv6 Network Data
This example shows how to overwrite the following data of an IPv6 network: address and cidr.
header-IPv6network,address*,_new_address,cidr*,_new_cidr
IPv6network,3333::,2222::,64,32
Merging IPv6 Network Data
This example shows how to merge the extensible attribute State and admin group USA_admins to an IPv6 network.
header-IPv6network.address*,cidr*,EA-State,ADMGRP-USA_admins
IPv6network,3333::,64,CA,RW
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
override_options
This is an example of a DHCP option.
For information, see Data Specific
Guidelines on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible
attribute Site
extensible_attributes
EA-Site is an example of a
predefined extensible attribute. You
can add other predefined attributes
to the data file. For information
about data format and examples,
see Data Specific Guidelines on
page 8.
EA-Users String No Extensible
attribute Users
extensible_attributes
EA-Users is an example of a user
defined attribute. You can add other
user defined attributes to the data
file. For information about data
format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of
an admin permission of a specific
admin group. For information about
data format and examples, see Data
Specific Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
42 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
IPv4 Shared Network
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-SharedNetwork String Yes Example: SharedNetwork
name String Yes Name name Example: Site Network
_new_name String No Add this field to overwrite the name field
when you select the overwrite or merge
option.
networks List Yes Example: “10.1.1.0/24,10.1.2.0/24,”
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
is_authoritative Boolean No Authoritative authority Example: FALSE
boot_file String No Boot File bootfile Example: bootfile1
boot_server String No Boot Server bootserver Example: abc.corp100.com
comment String No Comment comment
generate_hostname Boolean No Generate
Hostname
ddns_generate_hostname
Example: TRUE
always_update_dns Boolean No DNS Zones
Associations
ddns_server_always_updates
Example: FALSE
update_static_leases Boolean No Fixed Address
Updates
ddns_update_fixed_address
Example: FALSE
update_dns_on_lease_renewal
Boolean No Update DNS on
DHCP Lease
Renewal
override_update_dns_on_lease_renewal
Example: TRUE
ddns_ttl Integer No DDNS Update TTL ddns_ttl This is an inherited field.Example: 1200
enable_option81 Boolean No Option 81
Support
ddns_use_option
81
Example: TRUE
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp Example: FALSE
disabled Boolean No Disable disable Example: FALSE
enable_ddns Boolean No Enable DDNS
Updates
enable_ddns Example: FALSE
ignore_client_requested_ options
Boolean No Ignore Optionlist ignore_dhcp_option_list_reque
st
Example: TRUE
next_server String No Next Server nextserver Example: blue.domain.com
lease_time Unsigned
integer
No Lease Time Example: 1100
enable_pxe_lease_time
Boolean No Enable PXE lease
time
Example: FALSE
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time Example: 1100
routers IP address
list
No Routers Example: "10.0.0.1,10.0.0.100"
NIOS 6.2 CSV Import Reference (Rev. A) 43
CSV Import Reference
Examples
This section contains examples of how to create data files for shared networks. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Shared Network
This example shows how to import a new shared Network in the Default DHCP view.
header-SharedNetwork,name*,networks*,network_view,comment,OPTION-2
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24”,Default,This is a comment.,128
Overwriting IPv4 Shared Network Data
This example shows how to overwrite a shared network with additional networks.
header-SharedNetwork,name*,networks*
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24,30.0.0.0/24”
domain_name FQDN No Domain Name domain_name
domain_name_servers IP address
list
No Name Server Example: "10.2.3.4,11.2.3.4"
OPTION-2 Integer No Custom DHCP
Options
options Example: 50
OPTION-1 String No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
No Extensible
Attribute Site
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible
Attribute Users
extensible
attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines on
page 8.
EA-Users String No Permissions
Admin
Group/Role
extensible
attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
44 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Merging IPv4 Shared Network Data
This example shows how to merge the extensible attribute Site and a new admin group DHCP_admins with RW
permission to an IPv4 shared network.
header-SharedNetwork,name*,networks*,EA-Site,ADMGRP-DHCP_admins
SharedNetwork,Sharednetwork01,”10.0.0.0/24,20.0.0.0/24”,USA,RW
IPv6 Shared Network
Note: This object is supported in CSV export only.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-IPv6SharedNet
work
String Yes Example: IPv6SharedNetwork
name String Yes Name name Example: IPv6Shared01
_new_name String No Add this field to overwrite the name field
when you select the overwrite or merge
option.
networks List Yes Select Network networks Example: “2000::/64,3000::/64”
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
comment String No Comment comment
disabled Boolean No Disabled disable Example: FALSE
domain_name String No Domain Name Example: testdomain.com
domain_name_servers IP address
list
No Name Server Example: “2000::10,3000::10”
valid_lifetime Integer No Valid Lifetime valid_lifetime Example: 43200
Preferred_lifetime Integer No Preferred Lifetime preferred_lifetime
Example: 604800
enable_ddns Boolean No Enable DDNS
Updates
enable_ddns Example: TRUE
always_update_dns Boolean No DNS Zones
Associations
ddns_server_always_updates
Example: TRUE
ddns_domain_name String No DDNS Domain
Name
ddns_domainname
Example: DDNSdomain
ddns_ttl Integer No DDNS Update TTL override_ddns_ttl This is an inherited field.Example: 1200
generate_hostname Boolean No Generate
Hostname
override_ddns_generate_hostname
Example: TRUE
update_dns_on_lease_renewal
Boolean No Update DNS on
DHCP Lease
Renewal
override_update_dns_on_lease_renewal
Example: TRUE
NIOS 6.2 CSV Import Reference (Rev. A) 45
CSV Import Reference
OPTION-7 Integer No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ‘12’ name implies option space =
‘DHCPv6’, option code/number 7
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible
attribute Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines on
page 8.
EA-Users String No Extensible
attribute Users
extensible_attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
46 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
IPv4 DHCP Range
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-DhcpRange String Yes Example: DhcpRange
start_address IP address Yes Start start_addr Example: 10.0.0.11
_new_start_address IP address No Add this field to overwrite the
start_address field when you select the
overwrite or merge option.
Example: 10.0.0.55
end_address IP address Yes End end_addr Example: 10.0.0.22
_new_end_address IP address No Add this field to overwrite the
end_address field when you select the
overwrite or merge option.
Example: 10.0.0.66
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
name String No Name name
comment String No Comment comment
is_authoritative Boolean No Authoritative authority Example: FALSE
boot_file String No Boot File bootfile Example: bootfile1
boot_server String No Boot Server bootserver Example: abc.corp100.com
ddns_domainname String No DDNS Domain
Name
ddns_domainname Example: ddns.corp100.com
generate_hostname Boolean No Generate
Hostname
ddns_generate_hostname
Example: TRUE
deny_all_clients Boolean No deny_all_clients Example: FALSE
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp Example: FALSE
disabled Boolean No Disabled disable Example: FALSE
domain_name_servers IP address list No Name Servers Example: "10.2.3.4,11.2.3.4,"
enable_ddns Boolean No Enable DDNS
Updates
enable_ddns Example: FALSE
enable_thresholds Boolean No Enable DHCP
Thresholds
enable_dhcp_thresholds
When you set this field to TRUE, you must
enter values in the
range_high_water_mark and
range_low_water_mark fields. You
cannot leave those fields empty.
Otherwise, the appliance generates an
error.
enable_threshold_email_ warnings
Boolean No Enable Email
Warnings
enable_email_
warnings
When you use the merge function, the
appliance preserves the existing value in
this field. When you use the overwrite
function, you must include a value (TURE
or FALSE). Otherwise, the appliance
generates an error.Example: TRUE
NIOS 6.2 CSV Import Reference (Rev. A) 47
CSV Import Reference
enable_threshold_snmp_ warnings
Boolean No Enable SNMP
Warnings
enable_snmp_
warnings
When you use the merge function, the
appliance preserves the existing value in
this field. When you use the overwrite
function, you must include a value (TURE
or FALSE). Otherwise, the appliance
generates an error.Example: TRUE
threshold_email_addresses
email address
list
No Email Addresses Example:
"'[email protected]','[email protected]'"
range_high_water_mark
Integer No High Water Mark high_water_mark When you set enable_thresholds to TRUE,
you must enter values in this field and in
the range_low_water_mark field. You
cannot leave these fields empty.
Otherwise, the appliance generates an
error.
Example: 80
ignore_client_requested_ options
Boolean No Ignore Optionlist ignore_dhcp_option_list_reques
t
Example: TRUE
range_low_water_mark Integer No Low Water Mark low_water_mark When you set enable_thresholds to TRUE,
you must enter values in this field and in
the range_high_water_mark field. You
cannot leave these fields empty.
Otherwise, the appliance generates an
error.
Example: 10
next_server String No Next Server nextserver Example: blue.domain.com
lease_time Unsigned
integer
No Lease Time Example: 1100
enable_pxe_lease_time
Boolean No Enable PXE lease
time
Example: FALSE
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time Example: 1100
use_unknown_clients Boolean No Allow/Deny
Clients: Unknown
Clients
unknown_client_option
Example: FALSE
unknown_clients_option
String No Unknown Clients
drop-down
unknown_client_option
Example: Allow
use_known_clients Boolean No Allow/Deny
Clients: Known
Clients
known_clients_option
Example: TRUE
known_clients_option String No Known Clients
drop-down
known_clients_option
Example: Deny
recycle_leases Boolean No Lease Deletion recycle_leases This field is set to TRUE by default. Ensure
that you use the overwrite option if you
want to change the value to FALSE.
Merging data from an import preserves
the default value.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
48 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
update_dns_on_lease_renewal
Boolean No Update DNS on
DHCP Lease
Renewal
override_update_dns_on_lease_renewal
Example: TRUE
always_update_dns Boolean No DNS Zones
Associations
always_update_dns
Example: FALSE
exclusion_ranges IP address
range
No Exclusion Ranges exclude This field indicates the start to end
address range. You can also include a
comment. The valid format is start
address-end address/comment.
Example: “10.1.0.200-10.1.0.254/’The
range for printers’,10.2.3.3-10.2.3.30/”
member Grid member No Served by Grid
Member
member Example: member.infoblox.com
server_association_type
Sting No Valid values are MEMBER, NONE, and
FAILOVER
failover_association String No Served by
Failover
Association
failover_assoc
broadcast_address IP address No Broadcast
Address
Example: 10.0.0.1
routers IP address list No Routers Example: "10.0.0.1,10.0.0.100,"
domain_name FQDN No Domain Name domain_name
mac_filter_rules List of MAC
filter rules
No Filter Type/Action Example: "MACfiltername1/allow,
MACfiltername2/deny"
nac_filter_rules List of NAC
Filter rules
No Filter Type/Action Example: "NACfiltername1/allow,
NACfiltername2/deny"
relay_agent_filter_rules List of relay
agent filter
rules
Filter Type/Action Example: "RAfiltername1/allow,
RAfiltername2/deny"
option_filter_rules List of option
filter rules
Filter Type/Action Example: "Optionfiltername1/allow,
Optionfiltername2/deny"
OPTION-2 Integer No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: 50
OPTION-1 String No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 49
CSV Import Reference
Examples
This section contains examples of how to create data files for DHCP ranges. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding a DHCP Range
This example shows how to import a new DHCP range, Range01, with starting IP of 100.0.0.1 and ending IP
100.0.0.254. The range is assigned to a member, master.corp100.com.
header-DhcpRange,start_address*,end_address*,name,comment,member
DhcpRange,100.0.0.1,100.0.0.254,Range01,This is a comment.,master.corp100.com
Overwriting DHCP Range Data
This example shows how to overwrite the starting address and the name of an existing DHCP range,.
header-DhcpRange,start_address*,_new_start_address,end_address*,name
DhcpRange,100.0.0.100,100.0.0.150,100.0.0.254,Range02
Merging DHCP Range Data
This example shows how to merge an exclusion range 100.0.0.100 to 100.0.0.110 to an existing DHCP range, and to
replace a member assignment with a failover association, Failover01.
header-DhcpRange,start_address*,end_address*,exclusion_ranges,failover_association
DhcpRange,100.0.0.100,100.0.0.254,100.0.0.100-100.0.0.110,Fileaover01
EA-Site String No Extensible
Attribute Site
extensible
attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible
Attribute Users
extensible
attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
50 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
IPv6 DHCP Range
Note: This object is supported in CSV export only.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-IPv6DhcpRange String Yes Example: IPv6DhcpRange
address_type Enumeration No address_type Valid values are ADDRESS, PREFIX, and
BOTH. If no value is specified, ‘ADDRESS’
(default) is used.Example: PREFIX
parent String No Select Network network This field is required when address_type
is ‘PREFIX’.Example: 2000::/16
start_address IP address No Address Start start_addr This field is required if address_type is
‘ADDRESS’ or ‘BOTH’.Example: 2000::1
_new_start_address IP address No Add this field to overwrite the
start_address field when you select the
overwrite or merge option.
end_address IP address No Address End end_addr This field is required if address_type is
‘ADDRESS’ or ‘BOTH’.Example: 2000::1
_new_end_address IP address No Add this field to overwrite the
end_address field when you select the
overwrite or merge option.
ipv6_start_prefix IPv6 address
prefix
No Prefix Delegated
Start
ipv6_start_prefix This field is required if address_type is
‘PREFIX’ or ‘BOTH’.Example: 2000:1111::
_new_ipv6_start_prefix IPv6 address
prefix
No Add this field to overwrite the
ipv6_start_address field when you select
the overwrite or merge option.
ipv6_end_prefix IPv6 address
prefix
No Prefix Delegated
End
ipv6_end_prefix This field is required if address_type is
‘PREFIX’ or ‘BOTH’.Example: 2000:1111::
_new_ipv6_end_prefix IPv6 address
prefix
No Add this field to overwrite the
ipv6_end_address field when you select
the overwrite or merge option.
ipb6_prefix_bits Integer No ipv6_prefix_bits This field is required if address_type is
‘PREFIX’ or ‘BOTH’.Example: 32
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
name String No Name name
comment String No Comment comment Example: This is an IPv6 DHCP range.
disabled Boolean No Disabled disable Example: FALSE
member Grid member No Grid Member member Example: member.infoblox.com
server_association_type
Sting No server_association
_type
Valid values are MEMBER and NONE. If no
value is specified, None (default) is used.
NIOS 6.2 CSV Import Reference (Rev. A) 51
CSV Import Reference
IPv4 Fixed Address/Reservation
Note: You can use the fixed address header to import reservations. When you import a reservation, you must specify
00:00:00:00:00:00 in the mac_address field.
exclusion_ranges IP address
range
No Exclusion Ranges exclude This field indicates the start to end
address range. You can also include a
comment. The valid format is: start
address-end address/comment.
Example: “2000::1-2000::5/’The range
for printers’”
recycle_leases Boolean No Lease Deletion recycle_leases This field is set to TRUE by default. Ensure
that you use the overwrite option if you
want to change the value to FALSE.
Merging data from an import preserves
the default value.
EA-Site String No Extensible
Attribute Site
extensible
attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible
Attribute Users
extensible
attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-FixedAddress String Yes Example: FixedAddress
ip_address IP address Yes IP Address ipv4addr Example: 10.0.0.11
_new_ip_address IP address No Add this field to overwrite the
ip_address field when you use the
overwrite or merge option.
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
name String No Name name
always_update_dns Boolean No DNS Zones
Associations
always_update_dns
Example: FALSE
boot_file String No Boot File bootfile Example: bootfile1
boot_server String No Boot Server bootserver Example: abc.corp100.com
prepared_zero Boolean No Example: FALSE
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
52 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
comment String No Comment comment
ddns_domainname String No DDNS Domain
Name
ddns_domainname Example: ddns.corp100.com
deny_bootp Boolean No Deny BOOTP
Requests
deny_bootp Example: FALSE
broadcast_address IP address No Broadcast Address Example: 10.0.0.1
routers IP address
list
No Routers Example: "10.0.0.1,10.0.0.100,"
domain_name FQDN No Domain Name
domain_name_servers
IP address
list
No Name Servers Example: "10.2.3.4,11.2.3.4,"
dhcp_client_identifier
String No Client Identifier dhcp_client_identifier
disabled Boolean No Disabled disable Example: FALSE
enable_ddns Boolean No Enable DDNS
Updates
Example: FALSE
ignore_client_requested_ options
Boolean No Ignore Optionlist ignore_dhcp_option_list_request
Example: TRUE
circuit_id String No agent_circuit_id This field is required when match_option
= CIRCUIT_ID.Example: 11
remote_id String No agent_remote_id This field is required when match_option
= REMOTE_ID.Example: xyz
mac_address MAC
address
NoYes for
reservation
MAC Address mac This field is required if match_option =
MAC_ADDRESS, or if you are importing a
reservation. For reservations, you must
enter 00:00:00:00:00:00 in this field.Example: aa:bb:cc:dd:ee:ff
match_option String No match_client Data must be in the following format:
['MAC_ADDRESS','CLIENT_ID','CIRCUIT_I
D','REMOTE_ID']
next_server String No Next Server nextserver Example: blue.domain.com
lease_time Unsigned
integer
No Lease Time Example: 1100
enable_pxe_lease_time
Boolean No Enable PXE lease
time
Example: FALSE
ddns_hostname String No ddns_hostname Example: host1.test.com
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time Example: 1100
OPTION-2 Integer No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific
Guidelines on page 8.Example: 50
OPTION-1 String No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific
Guidelines on page 8.Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 53
CSV Import Reference
Examples
This section contains examples of how to create data files for IPv4 fixed addresses. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Fixed Address
This example shows how to import a new IPv4 fixed address.
header-FixedAddress,ip_address*,network_view,mac_address*,match_option,remote_id,EA-Site
FixedAddress,100.0.0.1,Default,aa:aa:aa:aa:aa:aa,Remote_ID,xyz,USA
Overwriting IPv4 Fixed Address Data
This example shows how to overwrite the MAC address of an existing IPv4 fixed address from aa:aa:aa:aa:aa:aa to
bb:aa:aa:aa:aa:aa.
header-FixedAddress,ip_address*,mac_address*
FixedAddress,100.0.0.1,bb:aa:aa:aa:aa:aa
This example shows how to overwrite the address of an existing IPv4 fixed address from 100.0.0.1 to 100.0.0.10.
header-FixedAddress,ip_address*,_new_ip_address,mac_address*
FixedAddress,100.0.0.1,100.0.0.10,bb:aa:aa:aa:aa:aa
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
options This is an example of a DHCP option. For
information, see Data Specific
Guidelines on page 8.Example: dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible Attribute
Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible Attribute
Users
extensible_attributes
EA-Users is an example of a user defined
attribute this is of a List type
(enumeration list). You can add other
user defined attributes to the data file.
For information about data format and
examples, see Data Specific Guidelines
on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
54 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Merging IPv4 Fixed Address Data
This example shows how to merge a new comment to an existing IPv4 fixed address.
header-FixedAddress,ip_address,mac_address*,comment
FixedAddress,100.0.0.10,bb:aa:aa:aa:aa:aa,A new comment here.
This example shows how to merge new routers addresses and the domain name to an existing IPv4 fixed address.
header-FixedAddress,ip_address*,mac_address*,routers,domain_name
FixedAddress,100.0.0.10,bb:aa:aa:aa:aa:aa,”2.2.2.2,4.4.4.4”,ns1.corp100.com
Adding an IPv4 Reservation
This example shows how to import a new IPv4 reservation.
header-FixedAddress,ip_address*,network_view,mac_address*,EA-Site
FixedAddress,100.0.0.1,Default,00:00:00:00:00:00,USA
IPv6 Fixed Address
Note: This object is supported in CSV export only.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-IPv6FixedAdd
ress
String Yes Example: IPv6FixedAddress
address_type Enumeration No Address address_type Valid values are ADDRESS, PREFIX, and
BOTH. If no value is specified, ADDRESS
(default) is used.Example: PREFIX
parent String No Select Network network This field is required when address_type
is ‘PREFIX’. Example: 2000::/16
ip_address IP address No Address ipv6addr This field is required if address_type is
‘ADDRESS’ or ‘BOTH’.Example: 2000::5
_new_ip_address IP address No Add this field to overwrite the ip_address
field when you select the overwrite or
merge option.
ipv6_prefix IPv6 address
prefix
No Prefix Delegated ipv6prefix This field is required if address_type is
‘PREFIX’ or ‘BOTH’.Example: 2000:1111::
_new_ipv6_prefix IPv6 address
prefix
No Add this field to overwrite the ipv6_prefix
field when you select the overwrite or
merge option.
ipv6_prefix_bits Integer No ipv6prefix_bits This field is required if address_type is
‘PREFIX’ or ‘BOTH’.Example: 32
network_view String No Network View network_view If no view is specified, the Default view is
used. Example: Default
name String No Name name Example: IPv6FixedAddr
comment String No Comment comment
disabled Boolean No Disabled disable Example: FALSE
NIOS 6.2 CSV Import Reference (Rev. A) 55
CSV Import Reference
Examples
This section contains examples of how to create data files for IPv6 fixed addresses. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv6 Fixed Address
This example shows how to import a new IPv6 fixed address.
header-IPv6FixedAddress,address_type,ip_address,network_view,match_option,EA-Site
IPv6FixedAddress,ADDRESS,2000::5,Default,DUID,USA
match_option String No match_client Only ‘DUID’ is allowed.Example: DUID
duid String No DUID duid Example: 0001
domain_name FQDN No Domain Name Example: ns1.corp100.com
domain_name_servers
IPv6 address
list
No Name Servers Example: 2000::10,3000::10
valid_lifetime Unsigned
integer
No Valid Lifetime valid_lifename Example: 43200
preferred_lifetime Unsigned
integer
No Preferred Lifename preferred_lifetime Example: 604800
OPTION-7 Integer No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ‘12’ name implies option space
= ‘DHCPv6’, option code/number 7
OPTION-XXXX-200 Option
information
No Custom DHCP
Options
override_options
This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible Attribute
Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible Attribute
Users
extensible_attributes
EA-Users is an example of a user defined
attribute this is of a List type
(enumeration list). You can add other user
defined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
56 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Overwriting IPv6 Fixed Address Data
This example shows how to overwrite an existing IPv6 fixed address from 2000::5 to 2000::1.
header-IPv6FixedAddress,address_type,ip_address,_new_ip_address
IPv6FixedAddress,ADDRESS,2000::5,2000::1
Merging IPv6 Fixed Address Data
This example shows how to merge a new comment to an existing IPv6 fixed address.
header-IPv6FixedAddress,ip_address,comment
IPv6FixedAddress,2000::1,A new comment.
This example shows how to merge a new domain name to an existing IPv6 fixed address.
header-IPv6FixedAddress,ip_address,domain_name
IPv6FixedAddress,2000::1,ns1.corp100.com
DHCP MAC Filter
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-DhcpMacFilter String Yes Example: DhcpMacFilter
name String Yes Name name Example: MAC filter 1
_new_name String No Add this field to overwrite the name
field when you select the overwrite or
merge option.
never_expires Boolean No Never Expires Example: TRUE
expiration_interval Integer No Automatically expires
in
default_mac_address
_expiration
Example: 3624
enforce_expiration_time Boolean No Enforce Expiration
Times
enforce_expiration_times
Example: FALSE
comment String No Comment comment
EA-Site String No Extensible Attribute
Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add
other predefined attributes to the
data file. For information about data
format and examples, see Data
Specific Guidelines on page 8.
EA-Users String No Extensible Attribute
Users
extensible_attributes EA-Users is an example of a user
defined attribute. You can add other
user defined attributes to the data
file. For information about data
format and examples, see Data
Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions Admin
Group/Role
permission ADMGRP-JoeSmith is an example of
an admin permission of a specific
admin group. For information about
data format and examples, see Data
Specific Guidelines on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 57
CSV Import Reference
Examples
This section contains examples of how to create data files for DHCP MAC filters. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a DHCP MAC Filter
This example shows how to import a DHCP MAC filter.
header-dhcpmacfilter,name*,never_expires,expiration_interval,enforce_expiration_time,comment
dhcpmacfilter,MacFilter01,FALSE,3600,TRUE,This is a comment.
Overwriting DHCP MAC Filter Data
This example shows how to overwrite the MAC filter name from MacFilter01 to MacFilter02.
header-dhcpmacfilter,name*,_new_name
dhcpmacfilter,MacFilter01,MacFilter02
Merging DHCP MAC Filter Data
This example shows how to merge extensible attributes Site and Users, as well as admin group DHCP_admins with a
RO permission.
header-dhcpmacfilter,name*,EA-Site,EA-Users,ADMGRPDHCP_admins
dhcpmacfilter,MacFilter02,USA,John Smith,RO
MAC Filter Address
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-MacFilterAddress String Yes Example: MacFilterAddress
parent String Yes MAC Address
Filter
filter_name Example: MAC filter 1
mac_address MAC address Yes MAC Address mac_address Example: aa:bb:cc:dd:ee:ff
_new_mac_address MAC address No Add this field to overwrite the
mac_address field when you select the
overwrite or merge option.
is_registered_user Boolean No Register as User Example: TRUE
registered_user String No Register as User Example: John Doe
guest_first_name String No Register as Guest:
First Name
Example: John
guest_middle_name String No Register as Guest:
Middle Name
Example: Doe
guest_last_name String No Register as Guest:
Last Name
Example: Doe
guest_email Email address No Register as Guest:
Email Address
Example: [email protected]
guest_phone String No Register as Guest:
Phone Number
Example: 408-111-1111
guest_custom_field1 String No Register as Guest:
Custom Field 1
58 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for DHCP MAC filters. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a DHCP MAC Filter
This example shows how to import MAC filter address, aa:aa:aa:aa:aa:aa, to MacFilter01.
header-macfilteraddress,parent*,mac_address*,is_registered_user,never_expires,comment
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,FALSE,TRUE,This is a comment.
Overwriting DHCP MAC Filter
This example shows how to overwrite a MAC filter address with an expiration time.
header-macfilteraddress,parent*,mac_address*,never_expires,expire_time
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,FALSE,2010-12-30T10:30:00Z
Merging DHCP MAC Filter
This example shows how to merge extensible attributes Site and Users to an existing MAC filter address.
header-macfilteraddress,parent*mac_address*,EA-Site,EA-Users
macfilteraddress,MacFilter01,aa:aa:aa:aa:aa:aa,USA,John Smith
guest_custom_field2 String No Register as Guest:
Custom Field 2
guest_custom_field3 String No Register as Guest:
Custom Field 3
guest_custom_field4 String No Register as Guest:
Custom Field 4
never_expires Boolean No Never Expires Example: FALSE
expire_time Date/Time No Expires On Data must be in this format: "CCYY-MM-DDThh:mm:ss[Z(+-)hh:mm]"Example: 2009-02-29T10:30:00Z
comment String No Comment comment
EA-Site String No Extensible
Attribute Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible
Attribute Users
extensible_attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
ADMGRP-JoeSmith String No Permissions
Admin
Group/Role
permission ADMGRP-JoeSmith is an example of an
admin permission of a specific admin
group. For information about data format
and examples, see Data Specific
Guidelines on page 8.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
NIOS 6.2 CSV Import Reference (Rev. A) 59
CSV Import Reference
Option Filter
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Method
Usage and Guidelines
Header-OptionFilter String Yes Example: OptionFilter
name String Yes Name name Example: Option Filter 1
_new_name String No Add this field to overwrite the name field
when you select the overwrite or merge
option.
comment String No Comment comment
boot_file String No Boot File boot_file Example: bootfile1
boot_server String No Boot Server boot_server Example: abc.corp100.com
lease_time Integer No Lease Time lease_time Example: 7200
pxe_lease_time Unsigned
integer
No PXE Lease Time pxe_lease_time Example: 1100
next_server String No Next Server next_server Example: blue.domain.com
option_space String No Option Space option_space Example: Infoblox_DHCP
OPTION-2 Integer No Custom DHCP
Options
option_list This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: 50
OPTION-1 String No Custom DHCP
Options
options_list This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ‘255.0.0.0’ name implies
vendor_class=’DHCP’ (default)
OPTION-XXXX-200 Option
information
Np Extensible
Attribute Site
options_list This is an example of a DHCP option. For
information, see Data Specific Guidelines
on page 8.Example: ’dfdfdfd’ name implies
vendor_class=’XXXX’, option
code/number 200
EA-Site String No Extensible
Attribute Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines on
page 8.
EA-Users String No Extensible
Attribute Users
extensible_attributes
EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see Data
Specific Guidelines on page 8.
60 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Examples
This section contains examples of how to create data files for option filters. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding an Option Filter
This example shows how to import an option filter with boot file, boot server, and lease time.
header-OptionFilter name*,comment,boot_file,boot_server,lease_time
OptionFilter,OptionFilter01,This is a comment.,bootfile01 1.2.3.4,12800
Overwriting Option Filter Data
This example shows how to overwrite an option filter name and boot file name.
header-OptionFilter,name*,_new_name,boot_file
OptionFilter,OptionFilter01,OptionFilter02,bootfile02
Merging Option Filter Data
This example shows how to merge to an option filter the PXE lease time and next server domain name.
header-OptionFilter,name*,pxe_lease_time,next_server
OptionFilter,OptionFilter02,12800,next.corp100.com
Option Filter Match Rule
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-OptionFileterMatchRule String Yes Example: OptionFilterMatchRule
parent Option filter Yes Option Filter
Name
filter The name of the parent option
filter. Example: Option filter 1
match_option String Yes Match Option num Example: OPTION-1 (option space
is DHCP)
match_value String Yes Match Value value Example: 255.0.0.0
_new_match_value String No Add this field to overwrite the
match_value field when you select
the overwrite or merge option.
comment String No Comment comment
is_substring Boolean No Value is a
substring
is_substring Example: FALSE
substring_offset Integer No Substring Offset substring_offset Example: 2
substring_length Unsigned
integer
No Substring Length substring_length Example: Doe
NIOS 6.2 CSV Import Reference (Rev. A) 61
CSV Import Reference
Examples
This section contains examples of how to create data files for option filter match rules. All examples use comma as
the separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an Option Filter Match Rule
This example shows how to import an option filter match rule.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,is_substring,substring_offset
OptionFilterMatchRule,OptionFilter01,OPTION-1,2.2.2.2,FALSE,0
Overwriting Option Filter Match Rule Data
This example shows how to overwrite an existing match option with OPTION-2 and add a new match value of 3.3.3.3.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,_new_match_value
OptionFilterMatchRule,OptionFilter01,OPTION-2,2.2.2.2,3.3.3.3
Merging Option Filter Match Rule Data
This example shows how to merge a substring length to an existing option filter match rule.
header-OptionFilterMatchRule,parent*,match_option*,match_value*,substring_length
OptionFilterMatchRule,OptionFilter02,OPTION-2,3.3.3.3,256
62 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Relay Agent Filter
Examples
This section contains examples of how to create data files for relay agent filters. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding a Relay Agent Filter
This example shows how to import a relay agent filter with a circuit ID and a remote ID.
header-RelayAgentFilter,name*,circuit_id_rule,circuit_id,remote_id_rule,remote_id
RelayAgentFilter,relayagent1,MATCHES_VALUE,123456,MATCHES_VALUE,abcd
Overwriting Relay Agent Filter Data
This example shows how to overwrite the circuit ID and remote ID of an existing relay agent filter.
header-RelayAgentFilter,name*,circuit_id_rule,circuit_id,remote_id_rule remote_id
RelayAgentFilter,relayagent1,MATCHES_VALUE,336699,MATCHES_VALUE,xyz
Merging Relay Agent Filter Data
This example shows how to merge a comment and extensible attribute Site to an existing relay agent filter.
header-RelayAgentFilter,name*,comment,EA-Site
RelayAgentFilter,relayagent1,This is a comment.,USA
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-RelayAgentFilter String Yes Example: RelayAgentFilter
name String Yes Name name Example: Relay Agent Filter 1
_new_name String No Add this field to overwrite the name
field when you select the overwrite or
merge option.
comment String No Comment comment
circuit_id_rule String No Circuit ID: Match
Value
is_circuit_id Example: MATCHES_VALUE
circuit_id String No Circuit ID circuit_id_name
remote_id_rule String No Remote ID: Match
Value
is_remote_id Example: MATCHES_VALUE
remote_id Integer No Remote ID remote_id_name Example: 50
EA-Site String No Extensible Attribute
Site
extensible_attributes
EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file.
For information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible Attribute
Users
extensible_attributes
EA-Users is an example of a user
defined attribute. You can add other
user defined attributes to the data file.
For information about data format and
examples, see Data Specific Guidelines
on page 8.
NIOS 6.2 CSV Import Reference (Rev. A) 63
CSV Import Reference
NAC Filter
Examples
This section contains examples of how to create data files for NAC filters. All examples use comma as the separator.
You can use other supported separators, such as semicolon, space, or tab.
Adding a NAC Filter
This example shows how to import a new NAC filter.
header-NacFilter,name*,comment,expression,EA-Site
NacFilter,nacfilter01,This is a comment.,option ServerError="true",USA
Overwriting NAC Filter Data
This example shows how to overwrite the name and comment of an existing NAC filter.
header-NacFilter,name*,_new_name,comment
NacFilter,nacfilter01,nacfilter02,This is a new comment.
Merging NAC Filter Data
This example shows how to merge the extensible attribute Users to an existing NAC filter.
header-NacFilter,name*,EA-Users
NacFilter,nacfilter02,John Smith
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-NACFilter String Yes Example: NACFilter
name String Yes Name name Example: NAC Filter
_new_name String No Add this field to overwrite the name field
when you select the overwrite or merge
option.
comment String No Comment comment
expression Option list No Match the following
rule
expression To include the option list in the Matching
the following rules table in Grid Manager,
you must enclose the expression in
brackets. Example:
(Sophos.ComplianceState="Compliant"
AND RADIUS.ServerError="TRUE")
EA-Site String No Extensible Attribute
Site
extensible_attributes EA-Site is an example of a predefined
extensible attribute. You can add other
predefined attributes to the data file. For
information about data format and
examples, see Data Specific Guidelines
on page 8.
EA-Users String No Extensible Attribute
Users
extensible_attributes EA-Users is an example of a user defined
attribute. You can add other user defined
attributes to the data file. For information
about data format and examples, see
Data Specific Guidelines on page 8.
64 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
IPv4 Option Space
Examples
This section contains examples of how to create data files for option spaces. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Option Space
This example shows how to import a new IPv4 option space.
header-OptionSpace,name*,space_type
OptionSpace,Optionspace01,VENDOR_SPACE
Overwriting IPv4 Option Space Data
This example shows how to overwrite the IPv4 option space name with Optionspace02.
header-OptionSpace,name*,_new_name
OptionSpace,Optionspace01,Optionspace02
Merging IPv4 Option Space Data
This example shows how to merge a comment to the IPv4 option space Optionspace02.
header-OptionSpace,name*,comment
OptionSpace,Optionspace02,This is a comment.
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-OptionSpace String Yes Example: OptionSpace
name String Yes Name name Example: ABC-co options
_new_name String No Add this field to overwrite the name
field when you select the overwrite or
merge option.
comment String No Comment comment
NIOS 6.2 CSV Import Reference (Rev. A) 65
CSV Import Reference
IPv6 Option Space
Note: This object is supported in CSV export only.
IPv4 Option Definition
Examples
This section contains examples of how to create data files for option definitions. All examples use comma as the
separator. You can use other supported separators, such as semicolon, space, or tab.
Adding an IPv4 Option Definition
This example shows how to import an option definition to the IPv4 option space Space01.
header-OptionDefinition,space*,name*,code*,type*
OptionDefinition,Space01,Option99,99,T_IP_ADDRESS
Field Name Data TypeRequired (Yes/No)
Associated GUI FieldAssociated PAPI Object
Usage and Guidelines
Header-IPv6OptionS
pace
String Yes Example: IPv6OptionSpace
name String Yes Name name Example: MySpace
_new_name String No Add this field to overwrite the name
field when you select the overwrite or
merge option.
comment String No Comment comment Example: Custom option space
ipv6_enterprise_number
String No Enterprise Number This is the vendor’s enterprise number
that is registered with IANA.Example: 7779
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-OptionDefinition String Yes Example: OptionDefinition
space String Yes Option Space space Example: ABC-co options
_new_space String No Add this field to overwrite the space field
when you select the overwrite or merge
option.
name String Yes Name name Example: Option one
_new_name String No Add this field to overwrite the name field
when you use the overwrite or merge
option.
code String Yes Options: Code code
type String Yes Options: Type type Use any of the following values: T_FLAG,
T_STRING, T_TEXT, T_IP_ADDRESS,
T_ARRAY_IP_ADDRESS, T_DOMAIN,
T_ARRAY_DOMAIN, T_UINT8,T_UINT16,
T_UINT32, T_INT8, T_INT16
Example: T_TEXT
66 CSV Import Reference (Rev. A) NIOS 6.2
Supported Object Types
Overwriting IPv4 Option Definition Data
This example shows how to overwrite the IPv4 option definition type from T_IP_ADDRESS to T_FLAG.
header-OptionDefinition,space*,name*,code*,type*
OptionDefinition,Space01,Option99,99,T_FLAG
Merging IPv4 Option Definition Data
This example shows how to merge a new space and a new name to an existing IPv4 option definition.
header-OptionDefinition,space*,_new_space,name*,_new_name
OptionDefinition,Space01,New_Space01,Option99,New_Option99
IPv6 Option Definition
Note: This object is supported in CSV export only.
Field Name Data TypeRequired (Yes/No)
Associated GUI Field
Associated PAPI Object
Usage and Guidelines
Header-IPv6OptionDefin
ition
String Yes Example: IPv6OptionDefinition
space String Yes Option Space space Example: MySpace
_new_space String No Add this field to overwrite the space field
when you select the overwrite or merge
option.
name String Yes Name name Example: MyOption1
_new_name String No Add this field to overwrite the name field
when you use the overwrite or merge
option.
code String Yes Options: Code code Example: 10
type String Yes Options: Type type Use any of the following values:
'T_ARRAY_DOMAIN', 'T_ARRAY_INT16',
'T_ARRAY_INT32', 'T_ARRAY_INT8',
'T_ARRAY_IP_ADDRESS','T_ARRAY_IP_AD
DRESS_PAIR','T_ARRAY_UINT16',
'T_ARRAY_UINT32', 'T_ARRAY_UINT8',
'T_DOMAIN', 'T_FLAG',
'T_FLAG_IP_ADDRESS', 'T_FLAG_TEXT',
'T_INT16', 'T_INT32', 'T_INT8',
'T_IP_ADDRESS', 'T_STRING', 'T_TEXT',
'T_UINT16', 'T_UINT32', 'T_UINT8',
'T_UINT8_1_2_4_8' Example: T_INT8
NIOS 6.2 CSV Import Reference (Rev. A) 67
CSV Import Reference
68 CSV Import Reference (Rev. A) NIOS 6.2