Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to determine a server's patch history?
- Thread starter adminman3
- Start date
phoneguy55
Programmer
not really sure, but I always leave the old patches in /var/home/ftp/pub
AvayaTier3
Technical User
update_show from linux will show unpacked patches staged on the server. History in the newer servers is in the /var/log/ecs/commandhistory files. Unfortunately, this only stores around 6 weeks of activity for each server.
when patches are unpacked, the patch files are unzipped to /opt/updates directory. There is not any stored information that would indicate all patches ever unpacked, activated, deactivated, or removed.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
when patches are unpacked, the patch files are unzipped to /opt/updates directory. There is not any stored information that would indicate all patches ever unpacked, activated, deactivated, or removed.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
- Thread starter
- #4
Great info! We had a recent situation when Avaya was dispatched to replace a faulty S8510, but when the tech tried to access load information based on the sold-to, he found that the Avaya site was down for maintenance. We had to resort to looking at a neighboring server to determine which patches to apply to the box load.
If we plan to keep track of applied patches, it sounds like we can do so only going forward, not historically, or at least not beyond about 2 months.
Thank you!
If we plan to keep track of applied patches, it sounds like we can do so only going forward, not historically, or at least not beyond about 2 months.
Thank you!
AvayaTier3
Technical User
In older cm versions it was kept in /var/log/ecs/update.log
This is no longer the case.
You should keep the tar.gz files for all patches that you ever unpack and a calendar of events for details on unpack, deactivate, active, remove.
There are many types of patches.
hot
cold
security
rpm
put it in, take it out (like DST and security patches)
IA770
aes
ses
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
This is no longer the case.
You should keep the tar.gz files for all patches that you ever unpack and a calendar of events for details on unpack, deactivate, active, remove.
There are many types of patches.
hot
cold
security
rpm
put it in, take it out (like DST and security patches)
IA770
aes
ses
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
- Thread starter
- #6
not to mention there are now "KERNEL" patches as well (for CM 5.2.1 for example), that update the linux kernel as well. these do a total reboot of the server when applied, and then must be "sudo update_commit [patch name]" to make them permanent.
Mitch
AVAYA Certified Expert
Mitch
AVAYA Certified Expert
AvayaTier3
Technical User
How to remove the patch
if malfunction of
your system occurs:
After the kernel service pack installation is complete (the update
is committed) you can deactivate it using the following method.
Note that a full Linux reboot will be required to completely
deactivate the changes after which the server will be running on
the original Linux kernel installed with Communication Manager
5.2.1 or SIP Enablement Services 5.2.1:
Run the following bash command on the Server:
> update_deactivate KERNEL-2.6.18-128.AV7c
The system will display a warning that a server reboot is required
to deactivate the update. Enter “y” to continue.
After the reboot is complete run the following bash command on
the Server:
> update_show
This should show the status of kernel service pack (Update ID)
“KERNEL-2.6.18-128.AV7c” as “pending_deactivate”.
Run the following bash command to commit the deactivation:
> update_commit KERNEL-2.6.18-128.AV7c
*Note - If you do not run the update_commit command within ten
minutes of the server reboot, a minor platform alarm is
generated.
>update_show
This should show the status of kernel service pack (Update ID)
“KERNEL-2.6.18-128.AV7c” as “unpacked”.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
AvayaTier3
Technical User
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
- Status
Similar threads
- Locked
- Question
