Product Support Notice

Transcription

1 PSN # PSN020381u Product Support Notice 2018 Avaya Inc. All Rights Reserved. Avaya Proprietary Use pursuant to the terms of your signed agreement or company policy. Original publication date: 10-Dec-18. This is Issue #03, published date: 11-Mar-19. Severity/risk level Medium Urgency When convenient Name of problem PSN020381u- Avaya Aura Application Enablement (AE) Services 8.0.x Super Patches Products affected Avaya Aura Application Enablement (AE) Services, Releases 8.0.x (all offer types) Problem description Avaya Aura Application Enablement (AE) Services Super Patch 2 ( ) is available. (aesvcs superpatch.bin; PLDS ID: AES ) AE Services ( Super Patch 2) includes the following fixes: Issue AES AES AES AES AES AES AES AES AES AES AES AES AES Customer Visible Symptom setselinux utility could not properly set the SELinux mode. DMCC SDK or could not receive channeltype in DeliveredEvent. SMS would get timed out intermittently. AES could not relinquish control of a call after a snapshot on the station is performed. Log Entry in /var/log/httpd/mod_jk.log. init_jk::mod_jk.c (3591): mod_jk/ initialized The potentially vulnerable HTTP DELETE and OPTIONS method requests could be sent AES didn't send "Conenction Clear" event to CTI application for service observer dropping off the call to observed party for the 2nd time. Huge amount of kernel martian logs were generated in alarm.log file The avayadefaultsal SNMP trap receiver could not be deleted after database restore Listed log files (sssd_ldap_domain.log, sssd.log, sssd_nss.log, maillog, cron) do not have a correct logrotation configuration from the third party RPMs, hence the file sizes may grow to a very large size. Alarm Viewer could not be seen on OAM due to conflict in hostname in /etc/hosts and /etc/hostname files. Running 'mvap.sh info' will show unexpected exceptions output. Snmpwalk on AES did not show information for TsapiLicense Order of Application: AES can be installed over AES AES can be installed over AES Historical Information for AE Services Super Patch 1 ( ) Avaya Aura Application Enablement (AE) Services Super Patch 1 ( ) is available. (aesvcs superpatch.bin; PLDS ID: AES ) AE Services ( Super Patch 1) includes the following fixes: Issue AES Predictive Call followed by Single Step Transfer fails. Customer Visible Symptom

2 Critical Note: The order of application is important. For an existing AES 8.0 upgrade to AES AES 8.0 OVA 2. AES pre-upgrade patch 3. AES Feature Pack Installer 4. AES Super Patch 1 For a new install starting with AES AES OVA 2. AES Super Patch 1 Software Only 1. AES ISO 2. AES Super Patch 1 Reference PCN 2083S for additional information on Resolution Install the latest Super Patch. Workaround or alternative remediation Remarks Issue 1 Dec 10, 2018: Avaya Aura Application Enablement (AE) Services Super Patch 1 ( ) Issue 2 Jan 24, 2019: Updated swversion output in verification section (changed from to 1) Issue 3 Mar 11, 2019: Avaya Aura Application Enablement (AE) Services Super Patch 2 ( ) Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Backup AE Services server data before applying the Super Patch: 1. Log into the AE Services Management Console using a browser. 2. From the main menu, select Maintenance > Server Data > Backup. AE Services backs up the database, and displays The backup file can be downloaded from Here on the Database Backup screen, 3. Click the "Here" link. A file download dialog box is displayed, from where you can open or save the backup file servername_softwareversion_aesvcsdbddmmyyyy.tar.gz. Where, ddmmyyyy is the date stamp). 4. Click Save, and download the backup file to a location from where you can gain access after the system upgrade. For example, save the file to your local computer or another computer used for storing backups. Download These instructions are applicable for any Super Patch binary. To download the AE Services Super Patch: A. Download from the Ayava support site: 1. Go to Avaya Support ( 2. Click Support by Products > Downloads: i. In Enter Product Name type Avaya Aura Application Enablement Services ii. In Choose Release select 8.0.x from the drop-down menu. iii. In the list of Downloads locate and select the patch you are looking for, in this example : 2018 Avaya Inc. All Rights Reserved. Page 2

3 Avaya Aura AE Services Super Patch, (paging might be necessary to find the entry). iv. Select the appropriate Super Patch download link. B. Download from PLDS 1. Go to the link Select View Downloads. 3. Use the search engine to locate the available downloads for Application Enablement Services using version 8.0 to narrow the search. 4. Locate the appropriate entry for the patch you are looking for (paging might be necessary to find the entry): Avaya Aura AE Services Super Patch 1 Alternatively, you can search directly for Download ID AES Note: All AE Services Software Downloads are available in PLDS, while the Release Note documents are available on the Support Site. Cross references between the corresponding download entries for patches are provided PLDS ID File Name MD5 Checksum Compatible with AES aesvcs superpatch.bin ab0dfad714874a31e911fa592c0d75cd AE Services (all offer types) PLDS ID File Name MD5 Checksum Compatible with AES aesvcs superpatch.bin c5c913d93e b380263fee2fa14 AE Services (all offer types) Note: Before you start with the installation of the patch, check the md5 checksum of the file. If the MD5 checksum does not match the stated value, do not proceed with installation. Download the patch again and verify the MD5 checksum matches. Patch install instructions Note: The AE Services server is out of service for 20 to 30 minutes while the patch is being applied and a reboot is required. Service-interrupting? Yes Check the detailed AE Services version. For the VMware and Software Only offer, use the AE Services Linux console to determine whether the patch has already been applied: 1. Start a Linux console session on the AE Services server (locally, via the services port, or by connecting remotely). 2. As the root user, execute the swversion command on the Command Line Interface (CLI). 3. If the Super Patch is not listed proceed with Patch installation. Installing the Patch on the AE Services server These instructions are applicable for any Super Patch binary. The example below is for Avaya Inc. All Rights Reserved. Page 3

4 For the VMware or Software Only offers use the following steps to install the patch: 1. Login to the AE Services server using the local Linux console, the service port or SSH. 2. Secure copy the patch file to the /tmp directory on the AE Services server. 3. As root user execute the following commands from the Command Line Interface (CLI). cd /tmp chmod 750 aesvcs superpatch.bin./aesvcs superpatch.bin 4. Follow the instructions provided. 5. After finished applying the Super Patch reboot the server: a. As root user execute the following command from the Command Line Interface (CLI): shutdown r now Verification These instructions are applicable for any Super Patch binary. The example below is for Use the following steps to verify successful patch installation: 1. Locally through the service port or remotely by using putty or SSH, start a Linux console session on the AE Services server. 2. Log in as sroot or root. 3. Run the following command to verify the installation of the Super Patch: swversion The swversion command displays a message similar to the following if the Super Patch is installed: ************* Patch Numbers Installed in this system are ************* 1 *********************************************************************** 4. Log into the AE Services Management console using a web browser. 5. From the main menu, click Status. 6. On the Status page, verify that all previously licensed services are running. 7. Validate the server configuration data, as follows: On the main menu click Networking Under AE Service IP (Local IP), verify that the settings are correct. Under Network Configure, verify that the displayed settings are correct. Under Ports, verify that the settings displayed are correct. 8. Check all of the remaining Management Console pages listed under AE Services and Communication Manager Interface. Verify that the information is complete and correct. This completes the installation of the Super Patch. AE Services server configurations for data changes Note: Follow this procedure, only if the AE Services server configuration data has changed. Follow this procedure to restore the AE Services server data: 1. From the main menu of the AE Services Management Console, select Maintenance > Server Data > Restore. The Management Console displays the Restore Database Configuration screen. The initial state of the Restore Database page provides you with two basic functions: Text box with the Browse button, which provides the means to select a backup file to use for the Restore process. Alternatively, you can type a fully qualified name (FQDN) of the backup file in the text box. Restore button that starts the Restore process Avaya Inc. All Rights Reserved. Page 4

5 2. Click Browse and locate the AE Services database backup file that you intend to use 3. Click Restore. The Management Console redisplays the Restore Database Configuration page, with the following message: "A database restore is pending. You must restart the Database Service and the AE Server for the restore to take effect. To restart these services now, click the Restart Services button below." 3. Click Restart Services. AE Services restarts the Database Service and the AE Services, thereby completing the Restore process. Failure Contact Technical Support. Patch uninstall instructions These instructions are applicable for any Super Patch binary. The example below is for For the VMware or Software Only offers use the following steps to uninstall the patch: 1. Login to the AE Services server using the local Linux console, the service port or SSH. 2. As root user execute the following command from the Command Line Interface (CLI): update e Follow the instructions provided. 4. Restore server data using the steps provided in the AE Services server configurations for data changes section. 5. After the patch is uninstalled reboot the server: a. As root user execute the following command from the Command Line Interface (CLI): shutdown r now Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks Avaya Security Vulnerability Classification Not Susceptible Mitigation If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED AS IS. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS AVAYA ), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners Avaya Inc. All Rights Reserved. Page 5