MDS Upgrade to R81.10

[Sanjay_S]

Hi All,

I am planning to upgrade our MDS which is installed in VM ESX version 7.0.1. Upgrade wizard doesn't give me option to select 7.x at all and i can see the options till 6.x only. R81 is already working on the same ESX version without any issues. So just wanted to re-confirm if we are good to go ahead with R81.10 version with the ESX version 7.0.1?

Also getting the below warning when i verify the image. So does it mean i should only install Take 14 and not any latest JHF take?

A Jumbo Hotfix Accumulator (HFA) is installed on this server.
To align with this Jumbo HFA after the upgrade, install R81.10 jumbo take 14.

Also i got a warning to take Backup of user.def and table.def files and replace it once upgraded. Anything else that i need to be taking manual backup of and replace it once done?

The upgrade process will deploy new files, which are suitable to version R81.10.
If you wish to apply these modifications again, backup the modified inspect files now, and add the changes post upgrade.

Please suggest on this as i need to upgrade the MDS this weekend.

Thanks in advance.

Regards,

Sanjay S

[PhoneBoy]

Vmware ESX 7 is supported per the HCL.
What the error means is you should install at least JHF Take 14.
If you made modifications in Expert mode to any other file, you should back that up too.
The ones mentioned were noticed by the migration tool.

[Sanjay_S]

Thank you PhoneBoy for the information.

I am not confident on what all changes has been done in the Expert mode except updating the User.def files for some VPN encryption issues. Is there any way i can check what changes has been done so that i can back all those file.

Regards,

Sanjay S

[PhoneBoy]

The migration tools should notice anything that affects the Security Policy (i.e. modified .def files).
There are other files in the Gaia OS that you might manually modify (e.g. sshd_config) that will need to be modified differently in newer versions, so simply making a backup and restoring it isn't enough, changes may have to be applied manually.
There are also specific files on gateways (e.g. fwkern.conf) you should make sure you document any changes to and review if they are necessary in the target version. 

[Sanjay_S]

Thank you PhoneBoy for more detailed info.

Is there any document which suggests what are the files because there are many firewalls which are there even before i came into this project. So it is bit difficult to know which files to manually change if there is no document suggesting that 😞 

Sorry for being a pain but if there are any such document please suggest.

[PhoneBoy · Accepted solution]

On management, it's mostly the .def files (which the migration tool notices) and maybe /etc/ssh/sshd_config.
I'm less familiar with what might be MDS specific that may have been edited.
Gateways have a LOT more possibilities for edited files (e.g. for MAB portal customization or similar). 

[Sanjay_S]

Hi All,

The below Job Scheduler was working fine until i upgrade it to R81.10 from R81. Not really sure why it is not working after upgrade. I also changed the CPmds-R81.10 from CPmds-R81 still not working. As per the schedule every week i can see the pgiz, gtar and mds_restore files getting created. Any inputs on this please.

. /etc/profile.d/CP.sh; /opt/CPmds-R81.10/scripts/mds_backup -l -b -s -d /var/log/mdsbackups/ 2>/dev/null; sleep 120;

Regards,

Sanjay S