dockerd wrote:
Code:
P patches don't need node restarts and can we installed one after the other okay, some have dependencies so the order installed can matter and some require running commands at the CLI after to finish and check they completed (the release notes will say so if required).
Ok.
Do patch update need any pre-requisite except patch dependencies such cpu and memory utilization less than 50% , stop all task , stop all activity and disconnect any ssmc sessions ???
Code:
Version changes (e.g. 3.2.2 -> 3.3.1) or MU installs (e.g. 3.3.1MU1 -> 3.3.1MU2) do require node reboots. One node at a time and recommended to use the pause option so you have time to check hosts have reconnected to the rebooted node okay before doing the next in an online live environment.
Ok.
What you mean by pause options ???
Thank you so much
Typically you don't need to worry about array activity/state when doing just Patches, it will do a health check first so as long as nothing broken can proceed. You may experience SSH/SSMC sessions dropping out if those services are restarted by the patch, normally SSMC will recover automatically. It's worth letting any admins know about patching so they don't think something broke.
All the things you mention are more relevant to MU and version upgrades because of the node reboots.
The pause options are for during node reboots, without selecting the pause option the 2nd node will start updating/rebooting as soon as the 1st node rejoins the cluster (after its reboot). With the pause option you have time to check the paths are restored okay on the hosts and do manual rescans on any hosts that failed to notice the 1st node return. Depends how critical the hosts are, we've tried to keep all hosts updated and configured within the 3PAR recommendations and other then one small VMware cluster have never had an issue during updates in the last 10 years or so.