Attention: Change in behaviour - Address Manager v9.5.4Address
Manager v9.5.0 introduced a different migration engine that was set as the
default engine for the migration service. In Address Manager v9.5.4, the legacy
engine has been returned as the default engine for the Address Manager migration
service. The migration engine introduced in v9.5.0 can still be accessed in
v9.5.4 by uploading the migration file with a manifest file, for more
information refer to Selecting the migration engine.
Use one or more XML files to migrate data into Address Manager.
After structuring the data in the XML file, you import the files to Address Manager and queue them for migration. You can use the migration
function to migrate data from another system into Address Manager, or to add
large amounts of new data.
To migrate configuration data from other types of servers, contact BlueCat Professional Services for assistance. For more information,
visit https://care.bluecatnetworks.com.
The Document Type Definition (DTD) file that defines the structure of the XML file
used for migration is available on your
Address Manager appliance or VM.
Launch a web browser and navigate to the
protocol://addressmanager-host/dtd/migration-legacy.dtd file, where
protocol is http or https, and
addressmanager-host is the IP
address or host name for your
Address Manager appliance or VM. Use this
address to view and download the DTD file. You can also add this address to the
header of your migration XML file to validate the file before you perform the
migration.
Note: Most browsers can display
the DTD file. Microsoft Internet Explorer can't display the DTD
file in the browser window, but you can download and save the
file from Internet Explorer. To save the file from Internet
Explorer, navigate to the DTD file address. After the error page
appears, click the File menu and then
select Save As. Save the file to your workstation as
migration.dtd.
Note: The DTD file for the v9.5.0 engine is accessible at
protocol://addressmanager-host/dtd/migration.dtd.
On the Migration service page, you can upload XML files and
queue them for migration. On the System logs page, you can
download migration logs to your workstation and delete logs from the server.
Note: Address Manager
doesn't create parent blocks, nor does
Address Manager try to search for the
best-suited parent block for the networks.
When importing networks without a defined
parent block in the migration XML,
Address Manager will perform the
following:
- If a suitable parent block exists in Address Manager, the network
will be added to that block.
- If no parent block exists, Address Manager won't create the network
and will instead log an error and skip the element.