Technical References

If there is an [export-addresses] section in the configuration file,
the export command uses the clusters that the section specifies
instead of the default cluster. If you omit a configuration file, the
export addresses command looks for a default .nrconfig file. This is
the same configuration file that the report command uses.
Network Registrar looks for the file first in your current directory,
then in your home directory, and finally in the install-path/conf
directory. It uses the first file it encounters. Each line of the
configuration file must begin with the character # (comment), a
section header enclosed in square brackets, or a parameter=value
pair or its continuation. For example:
[export addresses]
clusters=machine1 username password, machine2 username password [...]
Network Registrar strips leading white space from each line and ignores
blank lines.
dhcp-only
This keyword causes the command to output only DHCP information and
not DNS information.
Database tables
The table keyword specifies the database table to which the command
exports address information. If you omit this keyword,
Network Registrar writes to the default table name ip_addresses.
If the table already exists in the specified database when you run the
export command, Network Registrar clears (and resets the columns)
before writing the new data. Network Registrar does not provide a
warning or confirmation if it clears an existing table.
Date and time
The optional time-ascii and time-numeric keywords specify how to
output date/time fields to a CSV text file and when the target
database does not support the timestamp data type. The default
is time-ascii.
If no vpn is specified, the current-vpn of the session is used.
is used.
When specifying a <vpn-name> to any export command which supports
it, the name "global" (with or without the quotes) will specify
the global (i.e., unnamed or default) vpn. The name "all" (also
with or without the quotes) will specify that all vpn (including
the global one) should be exported.
You can use the export command to export the TSIG keys that are
configured on a cluster with the export keys command. You can
also specify to export a single key with the export key <keyname>
command. These commands will generate key definitions in BIND
syntax so they may be either imported into other clusters or copyied
into BIND configurations.
The export option-set command writes out a text file that may be
loaded into a running server with the option-set import command.