The cnr_exim data
import and export tool now supports the following for a user not constrained to
a specific tenant:
- Exporting all the data
- Exporting the data specific
to a tenant either with or without the core data
- Exporting and importing
license related data
- Importing all of the data
- Importing the data specific
to a tenant and optionally mapping it to a new tenant either with or without
the core data. This allows you to build a base configuration for new tenants.
When specifying tenant tags, the imported data is used to find the old tenant
id and the current configuration is used to find the new tenant id.
Some of the
advantages that come with the use of multi-tenant architecture are that you can
move configurations for a tenant from one cluster to another to export a tenant
template data and them import that data as another tenant.
Note |
A user constrained
to a specific tenant can only export or import data for that tenant.
|
The cnr_exim tool
also serves to export unprotected resource record information. However,
cnr_exim simply overwrites existing data and does not try to resolve conflicts.
Note |
You cannot use
cnr_exim tool for import or export of data from one version of Cisco Prime
Network Registrar to another. It can be used only for import or export of data
from or to the same versions of Cisco Prime Network Registrar.
|
Before using the
cnr_exim tool, exit from the CLI, then find the tool on:
- Windows —...\bin\cnr_exim.exe
- Solaris
and
Linux —.../usrbin/cnr_exim
You must reload the
server for the imported data to become active.
Note that text
exports are for reading purposes only. You cannot reimport them.
The text export
prompts for the username and password (the cluster defaults to the local
cluster). The syntax is:
> cnr_exim –e exportfile [–N username –P password –C cluster]
To export
(importable) raw data, use the
–x option:
> cnr_exim –e exportfile –x
To export DNS server
and zone components as binary data in raw format, use the
–x and
–c options:
> cnr_exim –e exportfile –x –c "dnsserver,zone"
The data import
syntax is (the import file must be in raw format):
> cnr_exim –i importfile [–N username –P password –C cluster]
You can also
overwrite existing data with the
–o option:
> cnr_exim –i importfile –o
The following table
describes all the qualifying options for the cnr_exim tool.
Table 2. cnr_exim Options
Option
|
Description
|
–a
value
|
Allows
exporting and importing of protected or unprotected RRs. Valid
values
are:
protectedRR unprotectedRR
On export or
import, all RRs are exported by default, so you must use a value to export or
import just the protected or unprotected RRs.
|
–c
" components"
|
Imports or
exports Cisco Prime Network Registrar components, as a quoted, comma-delimited
string. Use
–c
help to view the supported components. User are
not exported by default; you must explicitly export them using this option, and
they are always grouped with their defined groups and roles. Secrets are never
exported.
Note
|
After you
import administrator names, you must set new passwords for them. If you export
groups and roles separately from usernames (which are not exported by default),
their relationship to usernames is lost.
|
|
–C
cluster
|
Imports
from or exports to the specified cluster. Preset to
localhost .
|
–e
exportfile
|
Exports the
configuration to the specified file.
|
–h
|
Displays
help text for the supported options.
|
–i
importfile
|
Imports the
configuration to the specified file. The import file must be in raw format.
|
–N
username
|
Imports or
exports using the specified username.
|
–o
|
When used
with the
–i (import)
option, overwrites existing data.
|
–p
port
|
Port used
to connect to the SCP server.
|
–P
password
|
Imports or
exports using the specified password.
|
–t
exportfile
|
Specifies a
file name to export to, exports data in s-expression format.
|
–v
|
Displays
version information
|
–x
|
When used
with the
–e (export)
option, exports binary data in (importable) raw format.
|
-d
|
Specifies
the directory path of cnr_exim log file.
|
-f
tag
|id
|
Specifies
the source tenant. Valid for export and import.
|
-g
tag
|id
|
Specifies
the destination tenant. Valid for import only. The tenant-id can not be changed
when exporting data, only when the data is imported.)
|
-b
|
Specifies
that the core (base) objects are to be included in the import/export. This
includes all objects either with an explicit tenant-id of 0 and those that have
no tenant-id attribute
|
-w
|
Specifies
the view tag to export. This option allows the user to export zone and RRs data
which has the same view tag as mentioned in “w” option. All other objects will
not take this option into consideration and will be exported as earlier if it
is used.
|