Best Practice for DIFF config before/after upgrade

[saitoh]

Hi all,

I am having hard time in confirming if there is no unexpected change in configuration after conducting upgrade.

Is there any recommended way to perform this task, maybe more simple or quicker?

I did Open Server R80.10 to R80.40 with CPUSE, eventually to R81.20 tomorrow.

Saitoh

[G_W_Albrecht]

What are you speaking of ? Usually, old config still works, but new blades/parameters are set to default. Manual config changes in e.g. .def files have to be included in change log.

[saitoh]

Dear @G_W_Albrecht ,

Thanks for your comment.

A customer always makes us clearly confirm there is no avoidable config change in order to eliminate worse user experience, and make less impact on their business after replacement of the appliance.

On account of that, it is common sight for us engineers to compare the settings of pre/post-upgrade, I guess?

This is what I am working on.

Do I make myself clear?  Apologies if not...

Saitoh 

[AkosBakos]

Hi @saitoh 

If we talk about GW configuration: export the configuration into a file and compare them using Notepad++ compare tool. That higlights the differences.

The management is harder. 

Firtst: I usually make a new rule before the upgrade, and check it after the upgrade. If exists we are ok.

Second: tell to the customer, we trust in the product.

Third: do before and after tests. Write a check-list which contains the relevant services, and thest them one-by-one.

I hope it helps,

Akos