Scribd
Upload
15 views1 page

CM

Uploaded by

manogara05
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
15 views1 page

CM

Uploaded by

manogara05
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

In DLM landscape We will have manual patching activity twice a year to update to

latest kernel & glibc on all DLM servers.expected set of such servers different
platform
around 1000+ which may get failed while booting up due to some unknown booting
issue. Since ,we perform the activity in bulk, this issue would have caused trouble
for us on the patching day.
Hence,to avoid such scenario , before patching date as a part of prechecks, Prior
to that we will be having pre-patching activity on the servers.
We will be performing the checks including FS,hardware, patchme script enable etc.
on all the servers to avoid any issue in getting patched.
To make this task to be done in more simplified way, implemented an automated
process to handle the pre-patching task as well as the patching task.
We could recognize different type of issues with less manual effort on more no of
serevrs,which is helpful to resolve the issue before patching.
Also, before automation pre-patching was done for 10 servers among 100 servers but
after implementing the script, we can schedule nearly 40-50 servers as a pre-
patching activity.
As a better and improved way, this automation process is efficiently done through
shell-scripting.

We would have required additional time for troubleshooting to bring up the servers
back thus leading to extension of approved downtime which therefore would have
impacted the client directly i.e. loss of business.
Hence, implementing such automation process helped us in executing the pre/post
patching activity more efficiently by reducing more manual
work and contributing higher success rate.

The aim was to avoid such scenario and boot-up all the servers without getting
stuck and complete the activity within given down time.

CM analyzed and implemented implemented an automated process to handle the pre-


patching activity in more number of server to recognize different type of issues
with less manual effort, which is helpful to resolve the issue before patching and
will share the issues and findings with COE incase of common any trend.
Further on recieving the workaround from COE and on implementing the same on
remaining servers thereby mitigating the risk of failure on patching day.
Customers were happy for making this activity successful within the downtime.

You might also like