Identity Awarness upgrade (cross platform)

[melcu]

Hi team,
Me again 🙂

I'm working on a project to upgrade one layer from an IA platform. Right now across the board there is R81.10 but my client wants to replace some gateways and new ones only support R81.20 (Some 6600 with 9400).

Current architecture is:

- Fist layer: PDP Identity Broker

- Second layer: PDP Identity Broker

- Third layer: PDP Indentity Broker

- 4th layer: PEPs

As I've mentioned, everything is R81.10 Take ..something.

I am looking to replace only the 6600 from the 3rd layer and I was wondering if just migrating the identity_broker.C file from the original gateway to the new one (just as in a RMA process) and clearing all the PEPs will still work. I know back in the day with R77 and R80.40 there was chaos with cross platform versions. Different database structures and it's a mess.

Nowadays is still the same ? 
We have in plan to upgrade to R81.20 across the board but third layer is the most important at this point.

Little help is always appreciated as I don't want to "test in prod"

[the_rock]

I had customer do this before and while they did have backups etc, thry never had to copy over any files.

[Lesley · Accepted solution]

spin up lab, install version you want. import customer config Compare https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_IdentityAwareness_AdminGuide...

with 

https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_IdentityAwareness_AdminGuide...

And check if the filters from R81.10 are still there with R81.20

But tbh I never did this. There is no need to do this, unless you made custom changes to this file and you will perform clean install. 

Consider r82 r81.20 is eol next year nov 

[the_rock]

All valid points!

[melcu]

Agree with everything but it's outside my power to recommend R82 ;( They want R81.20 and it is what it is.

[the_rock]

100% fair!