> The CLI Guy 

Please contact your system administrator...

Avaya Communication Manager Version Number

22 Sep 2019  ·  Comments:  ·  Tags: Avaya, CommunicationManager, PowerShell, Regex

Summary

Avaya Communication Manager is a communication product which provides user and system management, call routing, application integration/extensibility, etc. It is normally accompanied by other Avaya products/components to form a complete communication platform.

The purpose of this post is to demonstrate how to obtain the Communication Manager version number from the output of the swversion command in the format that’s used in Avaya documentation.

The swversion Command

The swversion command is used to display details relating to the installed version of Communication Manager on a server.

To execute the command, connect to the server on which Communication Manager resides (using SSH for example) and run swversion.

Versions 3.0.0 - 6.0.1

The Avaya documentation uses the version number format n.n.n. There are two candidate fields in the output of swversion which are translatable to the n.n.n format:

(Older versions of CM do not use the CM prefix, I don’t know exactly which version this was first introduced)

  1. Reports as / CM Reports as
  2. Release string / CM Release String

Using the example output below, the version number in n.n.n format is 3.1.5:

    Operating system:  Linux 2.6.11-128.AV18h i686 i686
                Built:  Aug 7 17:01 2008
    
             Contains:  01.5.642.3
           Reports as:  R013x.01.5.642.3
       Release String:  S8700-013-01.5.642.3
UPDATES
01.5.642.3-17196        unpacked        cold         patch 17196 for 01.5.642.3
01.5.642.3-17944        activated       cold         patch 17944 for 01.5.642.3

 Translation saved:     2012-02-27 22:00:22
 
 License Installed:     2011-08-08 12:27:41

This is how to perform the translation:

Reports as: R013x.01.5.642.3
               |   | |
               | +-+ |
               | |   |
               | | +-+
               | | |
               V V V
               3.1.5
Release string: S8700-013-01.5.642.3
                        |  | |
                      +-+  | |
                      | +--+ |
                      | | +--+
                      | | |
                      V V V
                      3.1.5

Once you know how, it’s not difficult to do the translation by eye but it can also be done using a regular expression, an example of which is below using PowerShell:

PS C:\> "R013x.01.5.642.3" -replace 'R[0-9]{2}([0-9])[ix]\.[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
3.1.5

PS C:\> "S8700-013-01.5.642.3" -replace '[0-9a-z]+-[0-9]{2}([0-9])-[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
3.1.5

In order to make sure this translation technique was reliable I needed several Communication Manager versions to work from. The examples I used came from a YouTube video, How to Remotely Identify the Server Type of an Avaya Aura Communication Manager.

The example above for 3.1.5 is the first of three demonstrations from the video, the other two are shown below.

5.2.1 - https://youtu.be/_hKbxTZcA6c?t=167

swversion output:

      Operating system:  Linux 2.6.18-128.AV07PAE i686 i686
                 Built:  Aug 19 04:58 2009
                 
              Contains:  02.1.016.4
         CM Reports as:  R015x.02.1.016.4
     CM Release String:  S8500-015-02.1.016.4
     
UPDATES:
Update ID                       Status       Type    Update description
------------------------------- ------------ ------- ---------------------------
02.1.016.4-18942                activated    cold    patch 18942 for 02.1.016.4

Platform/Security ID            Status       Type    Update description
------------------------------- ------------ ------- ---------------------------


 CM Translation Saved:    2012-03-06 22:00:17
 
 CM License Installed:    2011-10-17 10:55:42
 
     CM Memory Config:    Standard

How to perform the translation:

CM Reports as: R015x.02.1.016.4
                  |   | |
                  | +-+ |
                  | |   |
                  | | +-+
                  | | |
                  V V V
                  5.2.1
CM Release String: S8500-015-02.1.016.4
                           |  | |
                         +-+  | |
                         | +--+ |
                         | | +--+
                         | | |
                         V V V
                         5.2.1

Regex:

PS C:\> "R015x.02.1.016.4" -replace 'R[0-9]{2}([0-9])[ix]\.[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
5.2.1

PS C:\> "S8500-015-02.1.016.4" -replace '[0-9a-z]+-[0-9]{2}([0-9])-[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
5.2.1

6.0.0 - https://youtu.be/_hKbxTZcA6c?t=224

swversion output:

              Contains:  00.0.345.0
         CM Reports as:  R016x.00.0.345.0
     CM Release String:  vcm-016-00.0.345.0
     
UPDATES:
Update ID                       Status       Type    Update description
------------------------------- ------------ ------- ---------------------------
00.0.345.0-18444                activated    cold    patch 18444 for 00.0.345.0

Platform/Security ID            Status       Type    Update description
------------------------------- ------------ ------- ---------------------------


 CM Translation Saved:    2012-02-27 22:00:12
 
 CM License Installed:    2011-12-31 16:49:13
 
         Messaging:       --N6.0-26.0----------------------
         
     CM Memory Config:    Large

How to perform the translation:

CM Reports as: R016x.00.0.345.0
                  |   | |
                  | +-+ |
                  | |   |
                  | | +-+
                  | | |
                  V V V
                  6.0.0
CM release string: vcm-016-00.0.345.0
                         |  | |
                       +-+  | |
                       | +--+ |
                       | | +--+
                       | | |
                       V V V
                       6.0.0

Regex:

PS C:\> "R016x.00.0.345.0" -replace 'R[0-9]{2}([0-9])[ix]\.[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
6.0.0

PS C:\> "vcm-016-00.0.345.0" -replace '[0-9a-z]+-[0-9]{2}([0-9])-[0-9]([0-9])\.([0-9]).*', '$1.$2.$3'
6.0.0

NB: In 2009, Avaya Communication Manager was renamed to Avaya Aura Communication Manager, making version 5.2 the first release to receive this new branding.

Version 6.2

(There is no version 6.1, the version numbering jumps from 6.0.x to 6.2)

There were a number of releases under version 6.2 but unlike previous versions each release did not increment the version number, instead releases were named as follows: 6.2 SP1, 6.2 SP2, etc.

Here’s an example of the swversion output for 6.2 SP8:

     Operating system:  Linux 2.6.18-238.AV02xen i686 i686
                Built:  Aug 26 09:25 2011

             Contains:  02.0.823.0
        CM Reports as:  R016x.02.0.823.0
    CM Release String:  vcm-016-02.0.823.0
     Publication Date:  27 December 2011

UPDATES:
Update ID                       Status       Type    Update description
------------------------------- ------------ ------- ---------------------------
02.0.823.0-20763                unpacked     cold    patch 20763 for 02.0.823.0
02.0.823.0-21388                activated    cold    patch 21388 for 02.0.823.0



Platform/Security ID            Status       Type    Update description
------------------------------- ------------ ------- ---------------------------

Messaging ID                    Status       Type    Update description
------------------------------- ------------ ------- ---------------------------


 CM Translation Saved:   2016-05-29 22:00:15

 CM License Installed:   2015-08-04 13:57:08

            Messaging:   --N6.2-22.0----------------------

     CM Memory Config:   Medium

(The example above was obtained from this Avaya Support article)

The version number (6.2) can be obtained with a minor tweak to the regex used for versions 3.0.0 - 6.0.1:

PS C:\> "R016x.02.0.823.0" -replace 'R[0-9]{2}([0-9])[ix]\.[0-9]([0-9]).*', '$1.$2'
6.2

PS C:\> "vcm-016-02.0.823.0" -replace '[0-9a-z]+-[0-9]{2}([0-9])-[0-9]([0-9]).*', '$1.$2'
6.2

Unfortunately there’s no way to obtain the service pack number directly from the output. The only option is to lookup up the latest patch number present on a system with a status of activated against the Avaya website, which in this example is 02.0.823.0-21388. See excerpt from the Avaya website below:

Avaya Aura® Communication Manager 6.2 Service Pack 8

File name - 02.0.823.0-21388.tar
File size - 29.0 MB (29,710 KB)
MD5 Sum - 42E5B8E5C730B7533333855C9F8B91D1

Version 6.3

Each release under 6.3 incremented the version number. The version numbering format used in documentation for 6.3 releases consists of a mixture of n.n, n.n.n and n.n.n.n, the reason for this appears to be explained in the Release Notes for Avaya Aura® Communication Manager Release 7.0 and Release 7.0 SP1, see Versions 7.0 - 8.1.

Using swversion, the version number can be obtained from the Update description field of the latest service pack to be present on a system with a status of activated. In the example below, the version is 6.3.16.0:

       Operating system:  Linux 2.6.18-417.AV1xen i686 i686
                  Built:  Feb 7 18:49 2017
  
               Contains:  03.0.124.0
          CM Reports as:  R016x.03.0.124.0
      CM Release String:  vcm-016-03.0.124.0
       Publication Date:  04 October 2012
  
  UPDATES:
  Update ID                       Status       Type    Update description
  ------------------------------- ------------ ------- ---------------------------
  03.0.124.0-21904                activated    cold    fix shellshock bug
  03.0.124.0-23675                activated    cold    6.3.16.0-SP16
  
  
  KERNEL-2.6.18-417.AV1           activated    cold    kernel patch KERNEL-2.6.18-
  
  Platform/Security ID            Status       Type    Update description
  ------------------------------- ------------ ------- ---------------------------
  PLAT-rhel5.3-3021               activated    cold    RHEL5.3-SSP308
  
  Messaging ID                    Status       Type    Update description
  ------------------------------- ------------ ------- ---------------------------
  
  
   CM Translation Saved:   2017-09-13 23:34:14
  
   CM License Installed:   2017-09-14 00:32:15
  
       CM Memory Config:   Large Survivable

(The example above was obtained from this Avaya Support article)

Versions 7.0 - 8.1

Each release increments the version number. The Release Notes for Avaya Aura® Communication Manager Release 7.0 and Release 7.0 SP1 clearly state how the version number convention works for 7.0 and later, see excerpts below:

Communication Manager Release 7.0 and later uses the following service pack naming 
convention. This is a five digit number format as described in the following example:

Communication Manager 7.1.0.0.0, where

    A - major release field (Communication Manager Release 7)
    B - minor release field (Communication Manager Release 7.1)
    C - feature pack field (Communication Manager Release 7.0.1)
    D - service pack field (Communication Manager Release 7.0 Service Pack 4)
    E - special release field, typically used for a re-issue of an existing service pack (Communication Manager 7.0 Service Pack 4.1)
...To avoid confusion, unused fields to the right might not be shown. For example, 
Communication Manager 7.0 will be used in documentation related to the minor release 
instead of Communication Manager 7.0.0.0.

This passage says the naming convention does not apply to 6.2 and earlier, so does that mean it does apply to 6.3? I suspect it does because 6.3 documentation includes a mixture of n.n, n.n.n and n.n.n.n:

...This naming change does not apply to service packs for Communication Manager Release 
6.2 and earlier which will follow existing naming formats.

The version number can be obtained from the output of swversion using a new field called RTS Version, see two examples below.

7.1.2:

       Operating system:  Linux 3.10.0-693.el7.AV1.x86_64 x86_64 x86_64
                  Built:
  
               Contains:  01.0.532.0
          CM Reports as:  R017x.01.0.532.0
      CM Release String:  vcm-017-01.0.532.0
            RTS Version:  CM 7.1.2.0.0.532.24184
       Publication Date:  25 June 2015
    VMwaretools version:  9.10.2.48224 (build-2822639)
  
  UPDATES:
  Update ID                         Status       Type  Update description
  --------------------------------- ------------ ----- ---------------------------
  01.0.532.0-24184                  activated    cold  7.1.2.0.0-FP2
  
  KERNEL-3.10.0-693.el7.AV1         activated    cold  kernel patch KERNEL-3.10.0-
  
  Platform/Security ID              Status       Type  Update description
  --------------------------------- ------------ ----- ---------------------------
  PLAT-rhel7.2-0010                 activated    cold  RHEL7.2-SSP001
  
  
   CM Translation Saved:   2018-11-01 22:00:07
  
   CM License Installed:   2018-08-27 07:02:24
  
       CM Memory Config:   Medium

(The example above was obtained from this Tek-Tips.com FAQ)

8.0.1.1:

     Operating system:  Linux 3.10.0-693.21.1.el7.x86_64 x86_64 x86_64
                Built:  Feb 23 18:54 2018
 
             Contains:  00.0.822.0
        CM Reports as:  R018x.00.0.822.0
    CM Release String:  vcm-018-00.0.822.0
          RTS Version:  CM 8.0.1.1.0.822.25183
     Publication Date:  09 May 2018
  VMwaretools version:  10.1.5.59732 (build-5055683)
       App Deployment:  Virtual Machine
       VM Environment:  VMware
 
UPDATES:
Update ID                         Status       Type  Update description
--------------------------------- ------------ ----- ---------------------------
00.0.822.0-25183                  activated    cold  8.0.1.1.0-FP1SP1
 
 
Platform/Security ID              Status       Type  Update description
--------------------------------- ------------ ----- ---------------------------
 
 
 CM Translation Saved:   2018-06-14 03:21:25
 
 CM License Installed:   2019-04-05 08:57:19
 
     CM Memory Config:   Large

(The example above was obtained from this Avaya Support article)

Comments

Leaving comments has been disabled for this post.

Copyright © 2018 - 2022 thecliguy.co.uk
For details, see Licences and Copyright