Arbi 7 Cm Patches


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Arbi 7 Cm Patches

  1. 1. Communication Manager Patches (on linux platforms) Arbi Arzouman ( GSS Backbone engineer (Tier III) – EMEA December 2008
  2. 2. Purpose of training <ul><li>Talk about Communication Manager patches </li></ul><ul><li>Introduce you to the world of CM patches </li></ul><ul><li>Commands for patches </li></ul>
  3. 3. Overview of patches
  4. 4. Overview of patches <ul><li>Quick Software Fixes for customer escalations </li></ul><ul><li>Patches are code (software) updates and / or fixes that we provide to customers after CM is installed </li></ul><ul><li>It means the fixes in the patches installed on top of the CM are NOT included in the current installed CM. Does it make sense?  </li></ul><ul><li>Avaya also provides period fixes to customers. These period fixes include defects and security problems detected after the release of CM was accepted as GA (General Availability) </li></ul>
  5. 5. More about patches <ul><li>Patches are built for each platform and release </li></ul><ul><ul><li>It means a patch for CM 3.1.2 can’t be installed on CM 3.1.3 or CM 5.x. It can only be installed on CM 3.1.2 </li></ul></ul><ul><li>There can be only ONE active patch for a system at a time </li></ul><ul><ul><li>Exceptions of course exist (e.g., DST patches) </li></ul></ul>
  6. 6. Why not just upgrade the customer? <ul><li>The fix may not be delivered to a GA load (generally-available) several weeks or even months, while a patch can be built and applied as soon as the fix is known </li></ul><ul><li>Patching doesn’t require a technician to be dispatched and spend several hours in transit and on site </li></ul><ul><li>Upgrading exposes the customer to new features or feature differences </li></ul><ul><li>Customers have gotten nervous about upgrading because upgrading sometimes introduces new problems!!! </li></ul>
  7. 7. So what does a patch look like? <ul><li>Ugly ;-) </li></ul><ul><li>It’s a compressed (gzip) file </li></ul><ul><li>It contains the fixes that will be installed on top of the currently installed CM </li></ul><ul><li>Patches are identified by 4 or 5 digit number </li></ul><ul><ul><li>00.0.825.4- 16249 </li></ul></ul><ul><ul><li>16249 is the patch number </li></ul></ul><ul><li>Let’s see an example! </li></ul>
  8. 8. So how do I see the installed patches? <ul><li>Use the command “ swversion ” on the linux CLI </li></ul><ul><li>You can also use the web interface </li></ul><ul><li>You can also use the CLI command “ update_show ” </li></ul>
  9. 9. So what does an installed patch look like? <ul><li>On different versions of CM, the result looks a bit different. But don’t worry, it’s easy to understand them </li></ul><ul><li>Next slide shows an example! </li></ul>
  10. 10. So what does an installed patch look like? <ul><li>init@budcm> swversion </li></ul><ul><li>Operating system: Linux 2.6.11-AV28 i686 i686 </li></ul><ul><li>Built: Apr 18 14:13 2008 </li></ul><ul><li>Contains: 01.0.414.3 </li></ul><ul><li>CM Reports as: R015x.01.0.414.3 </li></ul><ul><li>CM Release String: S8300-015-01.0.414.3 </li></ul><ul><li>UPDATES: </li></ul><ul><li>Update ID Status Type Update description </li></ul><ul><li>------------------------------- ------------ ------- --------------------------- </li></ul><ul><li>01.0.414.3-16492 unpacked cold Combo 16136 & 16491 </li></ul><ul><li>01.0.414.3-16662 activated cold combo of 15962 and 16625 </li></ul><ul><li>SES Update ID Status Type Update description </li></ul><ul><li>------------------------------- ------------ ------- --------------------------- </li></ul><ul><li>Platform/Security ID Status Type Update description </li></ul><ul><li>------------------------------- ------------ ------- --------------------------- </li></ul><ul><li>CM Translation Saved: 2008-12-02 22:00:16 </li></ul><ul><li>CM License Installed: 2008-09-30 14:58:30 </li></ul>
  11. 11. Type of the patches <ul><li>We have two types of patches: HOT and COLD </li></ul><ul><li>Hot patches are used in HOT countries and COLD patches are used in COLD countries  or maybe not! </li></ul><ul><li>Hot and Cold patches don’t look different on the file system (from the filename perspective) </li></ul>
  12. 12. Hot patches <ul><li>Hot patches when installed, by DESIGN are not service effecting </li></ul><ul><ul><li>This means that when we install a hot patch, we don’t need to: </li></ul></ul><ul><ul><ul><li>Interchange the servers (in case of duplex servers) </li></ul></ul></ul><ul><ul><ul><li>Stop and start the communication manager </li></ul></ul></ul><ul><ul><ul><li>Interrupt customer’s call control services </li></ul></ul></ul><ul><li>Hot patches replace individual functions </li></ul><ul><ul><li>Since existing instructions don’t move in a hot patch, it can be surprisingly small </li></ul></ul>
  13. 13. Cold patches <ul><li>Brrrrrr…. They are COLD </li></ul><ul><li>Installing a COLD patch is NOT service preserving!!!! </li></ul><ul><li>What this means: </li></ul><ul><ul><li>In case of duplicated servers, an interchange will be needed on live systems </li></ul></ul><ul><ul><li>In case of a single server, this will restart the CM </li></ul></ul><ul><ul><li>The Communication Manager will be stopped and started completely while patching the server </li></ul></ul><ul><ul><li>There will be short service interruption to customers call controller and services </li></ul></ul>
  14. 14. So why we have two types? <ul><li>We always want to minimize the impact we will have on customer’s call center and call controller when we want to deliver a patch </li></ul><ul><li>Cold patches don’t give us that option. However Hot patches do to some extend </li></ul><ul><li>Sometimes the fix is not possible to provide in the form of a hot patch, hence we need to provide the fix in the form of a cold patch!!! </li></ul>
  15. 15. How are fixes includes in the patches? <ul><li>Fixes are included in the patch as a single or collection of MRs. </li></ul><ul><li>MRs are referred to as: “ Modification Requests ”. </li></ul><ul><li>They contain additional files that are used by the patch. Let’s call them the x-files </li></ul>
  16. 16. Ok smartass, what’s an MR? <ul><li>When a software / hardware defect is detected and identified, the Tier4 / developers write an MR (modification request) </li></ul><ul><li>This MR documents the fault and additional details (depending on the author and the defect itself) </li></ul><ul><li>Developers then work on the MR and decide how to fix / if to fix and when to fix </li></ul><ul><li>The MR also includes additional info such as what is the fix, which files are effected and etc… </li></ul><ul><li>Let’s see an example of an MR !! </li></ul>
  17. 17. More patch types <ul><li>COLD and HOT patches are just one category of patch types. Let’s say they are the top of the pyramid. </li></ul><ul><li>We then have other types that derive from the COLD and HOT patches! They are: </li></ul><ul><li>Service pack patch </li></ul><ul><li>Incremental built patch </li></ul><ul><li>Combo patch </li></ul><ul><li>Seed patch </li></ul>
  18. 18. Seed patch <ul><li>Seed patches contain a single fix (Single MR) </li></ul><ul><li>When a fix is “developed”, a seed patch is created for that fix (MR) </li></ul>
  19. 19. Combo patches <ul><li>We rarely install seed patches on customer system </li></ul><ul><li>So what we do is we combine several seed patches and create a combo patch </li></ul><ul><li>Combo patches can be: </li></ul><ul><ul><li>Incremental built patches </li></ul></ul><ul><ul><li>Custom patches </li></ul></ul><ul><ul><li>Service packs </li></ul></ul>
  20. 20. Service packs <ul><li>Occasionally, we take our favorite fixes and bundle them into a giant patch known as a service pack </li></ul><ul><ul><li>Any server that is upgraded should immediately have the latest service pack applied </li></ul></ul><ul><ul><li>Service packs are available on the Avaya support web page ( </li></ul></ul><ul><ul><li>Often, a service pack is made available to coincide with the release of a new GA load to fix problems that have been discovered since the load was built </li></ul></ul><ul><ul><li>Subsequently, new service packs will be built as the number of known fixes warrants building a new one </li></ul></ul>
  21. 21. So what’s the schedule for service packs <ul><li>How do I know the schedule? </li></ul><ul><li>Visit the site: </li></ul><ul><ul><li> </li></ul></ul>
  22. 22. What to Include in a Service Pack? <ul><li>Since service packs are intended for distribution to large numbers of customers, we need to carefully choose what fixes are included </li></ul><ul><li>Fixes to problems that would affect many customers are candidates for inclusion in a service pack </li></ul><ul><li>Fixes that have undesirable side effects should not be included in a service pack </li></ul><ul><li>For example, a fix that stops restarts by breaking ISDN should not be included in a service packs </li></ul><ul><li>Each service pack includes all the fixes in the previous service pack </li></ul><ul><ul><li>...unless any of those fixes turned out to have undesirable side-effects! </li></ul></ul>
  23. 23. Where to find service packs! <ul><li>Open a browser and go to: </li></ul><ul><li>Click on “download” </li></ul><ul><li>Click on “Latest TN Circuit Pack, Server, and Media Gateway Firmware and Software Updates” </li></ul><ul><li>Scroll down to “Software Update table for Servers running Communication Manager” section </li></ul><ul><li>Let’s see a demo! </li></ul>
  24. 24. Incremental patches <ul><li>These are special combo patches </li></ul><ul><li>They are not service packs </li></ul><ul><li>But they are similar to service packs: </li></ul><ul><ul><li>They include several fixes </li></ul></ul><ul><ul><li>They are built periodically </li></ul></ul><ul><ul><li>Are public patches (can be installed on customer systems) </li></ul></ul><ul><li>Incremental built patches spent less time in TEST phase and hence are not always the best solution. </li></ul><ul><li>BPs and customers can’t download these patches themselves. Avaya backbone has to provide them </li></ul><ul><li>Not all the fixes in the incremental built patch make it to the next service pack </li></ul>
  25. 25. Where to find incremental patches <ul><li>Here: </li></ul><ul><li>This website is periodically updated </li></ul><ul><li>Find the correct patch number for your CM load </li></ul><ul><li>Then download the patch from: </li></ul><ul><ul><li> </li></ul></ul>
  26. 26. Custom patches <ul><li>These are combo patches </li></ul><ul><li>The secrete about these is that they are built for a specific reason or a specific customer or specific issue </li></ul><ul><li>Custom patches cannot and should not be provided to customers and BPs without the approval of Tier4 (CPE) </li></ul><ul><li>Customer patches are usually assigned as “ private ” </li></ul>
  27. 27. Public vs. Private patches <ul><li>Public </li></ul><ul><ul><li>Public patches can be provided to customers and BPs usually without the approval of Tier4 </li></ul></ul><ul><ul><li>Public patches are built for a large and general audience </li></ul></ul><ul><ul><li>Examples of public patches are the “service packs” </li></ul></ul><ul><li>Private </li></ul><ul><ul><li>Private patches are usually the “custom” patches </li></ul></ul><ul><ul><li>They are built for a specific reason, or a specific customer or to solve a specific issue </li></ul></ul>
  28. 28. What do patches look like on CM? <ul><li>UPDATES: </li></ul><ul><li>Update ID Status Type Update description </li></ul><ul><li>------------------------------- ------------ ------- --------------------------- </li></ul><ul><li>00.0.825.4-15759 unpacked cold patch 15759 for 00.0.825.4 </li></ul><ul><li>00.0.825.4-16249 activated cold Combo of 16015 and 16215 </li></ul><ul><li>Platform/Security ID Status Type Update description </li></ul><ul><li>------------------------------- ------------ ------- --------------------------- </li></ul><ul><li>PLAT-rhel4-1000 activated hot SSP 1-pcre security update </li></ul>
  29. 29. What are the Platform / Security patches <ul><li>Platform and/or security patches are not CM fixes </li></ul><ul><li>But rather the Linux OS fixes </li></ul><ul><li>Also include fixes for the applications that run under linux (such as http / ftp / etc…) </li></ul><ul><li>They also include security fixes </li></ul>
  30. 30. Where to find security patches <ul><li>Open a browser and go to: https:// / </li></ul><ul><li>Click on “download” </li></ul><ul><li>Click on “Latest TN Circuit Pack, Server, and Media Gateway Firmware and Software Updates” </li></ul><ul><li>Scroll down to “Software Update table for Servers running Communication Manager” section </li></ul><ul><li>Let’s see a demo! </li></ul>
  31. 31. What is the Security advisor <ul><li>Security advisor lists the discovered security problems </li></ul><ul><li>There are many discovered security problems for several products </li></ul><ul><li>The security patches contain fixes that are listed in the security advisory </li></ul><ul><li>Where to find them? Here  http:// = avaya.css.OpenPage& = SecurityAdvisory </li></ul>
  32. 32. WARNING! <ul><li>There is a product called “Multivantage express or MVE” or recently it has been renamed to “Communication Manager Express or CME” </li></ul><ul><li>These servers although they run CM, but the run them in a virtual environment (such as VMWare) and hence they need special patches that can be installed on their CM. </li></ul><ul><ul><li>Installing a normal CM patch will SCREW them up!!! </li></ul></ul>
  33. 33. How do I install patches? <ul><li>Installing the patches differ on CM loads. CM lower than CM 2.x use different command than CM higher or equal to 2.x </li></ul><ul><li>Let’s see the difference! </li></ul>
  34. 34. Install patches on CM 2.x and above <ul><li>You first need to have the patch downloaded to the server </li></ul><ul><li>The patch needs to be placed in /var/home/ftp/pub </li></ul><ul><li>Then issue the command: “update_unpack” </li></ul><ul><ul><li>This will unpack the patch </li></ul></ul><ul><li>You then need to un-install (deactivate) a patch if there is one already one installed (activated) </li></ul><ul><ul><li>Use the command: “update_deactivate <patchid>” </li></ul></ul><ul><li>Then install the patch using the command: “update_activate <patch id>” </li></ul>
  35. 35. Install patches on CM 2.x and above <ul><li>update_activate </li></ul><ul><ul><li>To activate a patch. The patch has to have already been unpacked </li></ul></ul><ul><li>update_info </li></ul><ul><ul><li>Shows information about a patch on the system </li></ul></ul><ul><li>update_show </li></ul><ul><ul><li>Lists the patches that are either activated / unpacked / packed </li></ul></ul><ul><li>update_deactivate </li></ul><ul><ul><li>To deactivate / uninstall the patch. This changes the status of the patch to “unpacked” </li></ul></ul><ul><ul><li>Does not completely remove the patch from the system </li></ul></ul><ul><li>update_remove </li></ul><ul><ul><li>Removes the patch and the files from the system </li></ul></ul><ul><li>update_unpack </li></ul><ul><ul><li>Unpacks the patch and copies the files to a proper directory. Before activating a patch, we need to unpack it first </li></ul></ul>
  36. 36. Install patches on CM lower than 2.x <ul><li>patch_show </li></ul><ul><li>patch_remove </li></ul><ul><li>patch_install </li></ul><ul><li>patch_apply </li></ul>
  37. 37. Additional info <ul><li> </li></ul><ul><li> </li></ul>
  38. 38. Thank you for listening to my crap  <ul><li>Thank you </li></ul>
  39. 39. © 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA