Hello, welcome to this video demonstration to accompany KB ‘ECS Solution to Address
CVE 2022-31231 Security Vulnerabilities’.
There are four parts to this video.
Number one, checking and upgrading xdoctor version.
Number two, pre-checks for patch application.
Number three, application of patch.
Number four, post-checks.
We start by verifying the version of xdoctor on the system.
Here we have version 83.
In this case we need to upgrade to version 84 or later.
So now you should proceed to the KB, click on the link to download the latest version
of xdoctor and upload it to the master node on the VDC.
You then upgrade the version of xdoctor using this command.
Note all the commands are taken from the KB.
Successful upgrade of xdoctor will look like this.
Here as we said we've upgraded the version 84.
We can double check this if I run the ‘--version’ command.
Please note in this example there is one rack in the VDC.
You may have two or more racks in your VDC, in that case you need to repeat this procedure
for each rack master node.
For more details on that consult the KB.
We now move to the pre-checks.
The first check is to verify that all DT's have ready status.
So for this, for this example here we have zero unready DT's.
The second check is to run a ‘svc_patch’ with the value ‘status’.
This verifies the patch bundle consistency.
It also checks all nodes can be reached on the VDC.
It's important that all these values are set to ‘done’.
So as the pre-check completes it tells you the patch that's going to be installed, the
two files that are going to be installed, and the ‘dataheadsvc’ service, which is
the service that's going to be restarted on each node.
We now proceed to the install phase, based on the successful completion of the previous
two pre-checks.
So we open a screen session, I've called it ‘patchinstall’, you can call it what you
want.
Screen session has now been opened, you can see the blue line here at the bottom.
You ‘unset’ the timeout.
To start to install you run the ‘svc_patch’ with the ‘install’ value.
So again, it does what we've previously done in the pre-checks, it values validates the
bundle consistency, checks all nodes are online, and checks installed patches and dependencies.
It then pauses with a prompt for you to continue.
It lists the patch that's going to be installed like it did in the pre-checks, the files are
going to be installed, and the data head service that will be restarted.
It identifies, in this case, that your five nodes on the system, and the number of seconds
between the restart of the ‘dataheadsvc’ service is 60 seconds.
You will remember if you had done previous svc_patch installs that it took seven and
a half minutes because we're restarting all services.
In this case it's just the ‘dataheadsvc’ service, so we'll only be waiting 60 seconds
between the restart on each node.
So answer yes to the prompt, it will now begin the distribution of these files to each of
the five nodes in the VDC.
So now you see it's completed the distribution to each of the five nodes, it's now at the
restart dataheadsvc service.
So as I said it waits 60 seconds between each node.
Patches are now, patches now completed and each of the five nodes say patching complete.
So at this stage we actually exit the screen session and we proceed to run the check again.
So again like in the pre-check phase it does the same verifications.
So it tells us the patch is now installed, no files need to be installed, no services
need to be restarted.
For more information around this customer-led patch install please consult the KB.
It gives information about who runs the procedure, impact to procedure, time taken for the activity
and some Frequently Asked Questions.
Thanks for taking the time to view this, and if there are any issues identified during
the pre-checks, install, or post checks then engage ECS remote support.