Avaya CM Software updates

How to optimize Aura Communications Manager

Avaya_CM_Software_Updates_img

Avaya CM Software updates

How to optimize Aura Communications Manager

In this post “Avaya CM Software updates” see how you can optimize the Avaya Aura Communications Manager server avoiding future software incompatibilities, or data failures by keeping the kernel running smooth when applying the necessary patches, routine backups, and service packs.  

As a service technician I have the privilege of preparing the equipment in the lab before going out to the customer’s site to deploy it. In the staging process I login to the customer’s system to apply any service packs or updates necessary.

These are the three elements to follow when implementing new system software=

  • 1.- Overview of Service Packs and Patches
  • 2.- Software Updates
  • 3.- Routine Backups

1.- Overview of Service Packs and Patches 

What is a software patch?

When Avaya releases a new version of Avaya Aura Communications Manager some customers might experience issues with their VoIP systems. This normally happens when Avaya develops the new Software and tested with a particular set of conditions, and like any other software developer every customer runs it differently with other features and adjuncts, therefore a patch is released to accommodated missing or broken features.

Service packs – After a couple of patches reiteration Avaya combines them into one piece of software and calls it Service pack. In theory a service pack is nothing more than a bunch of patches compiled into one.

Software Updates

Before you go jumping on downloading and upgrading your system(s) you have to take into consideration a couple of the following factors=

  • Licensing – Verify that any existing licenses residing in your system are compatible with the dowloaded software, and remember to re-generate a new license reflecting the new software version if necessary.
  • Hardware – Most of the software that is released by Avaya is backwards compatible making it convenient to keep legacy equipment around until end-of-life (EOD). If the release is not compatible with the hardware there is no other choice than to replace the necessary components. Always check the compatibility matrix
  • Upgrade procedure – When planning the upgrade always read the release’s notes and thoroughly understand the steps and procedures needed to successfully update the system. Follow these steps for a successful upgrade=
  • 1.- Test the environment – By recording and eliminating existing issues will help you understand if these are related to any updates done to your servers after applying the new patch(es).
  • 2.- Prepare the server(s) – Check the server memory, hard-drive space, fans, filters (if available), fiber connectors, IPSIS (if available), DHCP Configuration for IP Media Processors, etc. Go through the Maintenance/Configure Server / Individual Services pages and record all the IP Addresses, and identity names. It is very important if you are running duplicate servers, to collect that information as well.
  • 3.- Network Switches – Gather network switch configuration, as well as VLAN IDs, Network Maps, duplex and speed settings, among other settings.
  • 4.- Server Media – In order to deliver the files to the sever, you have to decide if you are using internal media such as CD/DVD-ROM, or external media such as DVD-ROM, Flashcard readers, or HTTP/FTP servers.
  • 5.- Backup – Conduct a backup and freeze date. A freeze date is implemented to avoid any changes there after.
  • 6.- Start the installation – For a clean install boot-up the server with a DVD media that you have created. An installation wizard will appear, fill out the appropriate fields the information already gathered.
  • 7.- Install service packs and patches – After the installation is completed, install the licenses, update the dadmin account, root passwords, load the Authentication/Password file, then load the service pack and patches. These can be uploaded and activated through the Maintenance/software update.

Routine Backups

Scheduled and Manual Backups

Using the SMI Console Avaya Communications Manager allows you to schedule a job to run based on time and date to a local media storage or shared network drive; the Manual Backup runs immediately after completing selecting the options.

There are three files backed up are the XLN, OS and Security. If you are using an Integrated Voicemail CMM then you also want to select the messages, announcements, and names.

Resources

Avaya Communication Manager Patches Program

Please note: I reserve the right to delete comments that are offensive or off-topic.

  • Sprith Shrivastava

    Hello, nice article. It would be grateful if you’d give more information regarding OS, XLN and security files.. What is their purpose ?

    • Sprith, the OS File contains Operating System files based on your configuration
      XLN – Communications Manager configurations (stations, ars, etc)
      Security – Has all the existing CM Accounts.

      By the way sorry for the delay on your response. It’s been a crazy two weeks

      • Sprith Shrivastava

        Thank you so much for the reply !
        Your articles are really helpful 🙂