Skip to main content

Hello, 

I don't understand the process to import maps with the old format (.xml) into the new Centreon MAP.

 

Step 1: Installation Central 22.10.2: OK (with the image inside)

Step 2: Installation MAP Engine 22.10.1: OK

Step 3: Monitoring → MAP in Central : OK

Step 4: Import .xml in the desktop client.: OK

 

But when i click on “migrate” in the Central, i can see :

Error: Authentification on the Centreon MAP legacy server. Migration step failed, check the logs on the NG server

 

Are we required to install MAP Legacy first before MAP Engine ?

Thank you.

Hello,

 

Not really sure to understand. Are you using MAP “legacy” (the one with the desktop client)?

The goal of the migration is to take the maps you have designed on legacy, convert them to the new format and import them in the new server. All this automatically by clicking on the “migrate” button of the new map home page, provided that your MAP legacy and MAP are configured properly in the “Admin → Extension → (map) options” form, and that you’ve switched the “ Map Engine server” option to yes.

If you do not have any map you want to migrate from the legacy this is not necessary.

 

Nils

Hello,

 

OK, in “Admin → Extension → (map) options”, i have only configured “Map engine server address”, because on my MAP serveur, only package centreon-map-engine is installed.

 

Do i also need to install map legacy on this same server ? And after migration, uninstall legacy to keep engine only ?

Hello,

You don’t need to install map legacy on the same server. Question is do you have maps that you have created with legacy server? If yes, and if your configuration is fine (map servers addresses set properly), if migration failed, please raise a ticket to support with information about your environments and logs when errors occures. If you don’t have maps you want to migrate then migration is not needed and you can start using MAP.

Best regards,

Nils

Yes, i have map created with legacy.

Ok, i will create ticket for support, thank you.

Reply


Terms & ConditionsCookie settings