traps 4.1.x on premise to 6 in cloud

[Alex_Samad]

Hi

So I am thinking of doing the traps on premise to in cloud move and at the same time upgrading versions.

So is it doable ?

Whats the main gotchas to look out for

[BPry · Accepted solution]

@Alex_Samad ,

The configuration doesn't match, so you'll need to re-create your policy in TMS and can only utilize the EMS configuration as a baseline to what you need to make for TMS. Youll then want to ensure that your agents have been upgraded to the latest release to ensure that the migration goes smoothly.

When you generate the package on TMS you'll actually deploy that package through EMS, just be sure you've disabled service protection for the agents you're upgrading.

You can find the guide within the TMS admin guide as far as how you would perform the upgrade step by step. 

[BPry]

@Alex_Samad,

You sure can, and without any issues. When you have your TMS instance setup you'll actually be able to generate an agent installation specifically for upgrading from an existing EMS managed agent. There really aren't any gotchas with it as long as you verify that any agent that was on EMS is actually shwoing up in your TMS instance and is showing as active. 

[Alex_Samad]

Hi

Thanks, so I have create TMS and set it up, I believe - I can log into it.

So i think the next steps is to migrate any polices or stuff from my  on premise traps install - seems like I can export and import stuff.

Then you are suggesting I can download something from my TMS to install on my machines that will automatically repoint them to the new location 

Cool.

I used to send my logs to my panorama box is there any way to do that from TMS back into my panorama on premise

[Alex_Samad]

@BPry  Do you know of any document that outlines the best practise setup for TMS. I am having issues exporting the current config from my EMS, so I am thinking I might redo the polices - wouldn't mind basing it upon what PA consider best practise

Go an upgrade package - how can I install the uninstall password so that the upgrade can happen without user intervention 

[BPry · Accepted solution]

@Alex_Samad ,

The configuration doesn't match, so you'll need to re-create your policy in TMS and can only utilize the EMS configuration as a baseline to what you need to make for TMS. Youll then want to ensure that your agents have been upgraded to the latest release to ensure that the migration goes smoothly.

When you generate the package on TMS you'll actually deploy that package through EMS, just be sure you've disabled service protection for the agents you're upgrading.

You can find the guide within the TMS admin guide as far as how you would perform the upgrade step by step.