MARS upgrade path

[brianbono]

hi guys,

i need your advice on how to go about upgrading the following MARS boxes below to the latest 4.2.8 version.

do I need to do this upgrade:

product version: 4.2.6 (2458) -> 4.2.7 -> 4.2.8

product version: 4.2.4 (2428) -> 4.2.5 -> 4.2.6 -> 4.2.7 -> 4.2.8

product version: 4.2.1 (2249) -> 4.2.2 -> 4.2.3 -> 4.2.4 -> 4.2.5 -> 4.26 -> 4.2.7 -> 4.2.8 (i understand to upgrade a 4.2.2 -> 4.2.3 will take about 1.6Gb)

Do I have to do this? Is there any other way to straight away upgrade those version to 4.2.8?

Lastly, I am planning to update the boxes remotely since I'm not geographically within reach of MARS boxes. I'm planning configure a internal upgrade server of this setting.

Would you suggest this type of setup? Is this really effective? Or do I need an on-site engineer to do the updates?

Please advise...

[mhellman]

Yes, and no there is no way to go directly to 4.2.8 without starting pretty much from scratch.

you can do the updates remotely (using the CLI) and then pray that nothing bad happens. Having gone through many upgrades myself, I would recommend having someone at least marginally competent available locally.

[pmccubbin]

My opinion exactly.

If you haven't done the upgrades before then by all means have someone on site to monitor the process via the CLI.