Product Support Notice

Transcription

1 PSN # PSN004084u Product Support Notice 2014 Avaya Inc. All Rights Reserved. Original publication date: 06-Nov-13. This is Issue #03, published date: 10-Oct-14. Severity/risk level Medium Urgency When convenient Name of problem Avaya Aura Application Enablement (AE) Services Super Patch 4 Release Notes Products affected Avaya Aura Application Enablement Services Release: (all offer types) Note: This patch is being reissued to resolve an installation issue with the AE Services VMware offer. Problem description What is fixed in this Patch? This patch contains the following updates to the DMCC Service: Issue AES : LampUpdateEvents corresponding to buttons in the call-coverage expansion module of a DMCC registered station were being mapped to the wrong buttonids. This patch ensures that the LampUpdateEvents are mapped to the correct call-coverage module buttonids. Issue AES : When a user logs into a Lync 2010 client, Lync sends multiple INVITEs and will sometimes send a CANCEL request to cancel the extra INVITE requests. DMCC would not always respond to the CANCEL requests. This caused the transaction queue to gradually grow and eventually messages would randomly be dropped (i.e. not processed) causing unpredictable behavior in the Lync client. Issue AES : When the Main Communication Manager (CM) failed-over to a Local Survivable Processor (LSP), it was possible for a DMCC station to be incorrectly re-registered against a CLAN which was associated with an ESS (that was also part of the switch survivability hierarchy). This fix ensures that, on CM failover, the DMCC stations are correctly re-registered to the Processor Ethernet (PE) of the LSP, instead of to a CLAN. Issue AES : When the DMCC sample applications from the AE Services 6.1.x Java SDK were run against an AE Services 6.2 server, the sample applications sometimes received a WARNING message indicating that the "ServiceLinkStatusEvent" could not be unmarshalled. This fix ensures that the "ServiceLinkStatusEvent" is handled correctly. Issue AES : When DMCC is running, it checks the IP addresses listed in the "H.323 Gatekeepers List" for each Switch Connection. Each check included the establishment of a TCP socket from AE Services to the specified H.323 gatekeeper, and caused the Communication Manager (CM) to log an error for that socket. This fix changes the H.323 gatekeeper check to ping the gatekeeper's IP address, instead of establishing a TCP socket, thereby eliminating the error in the CM logs. This patch contains the following updates to the TSAPI Service: Issue AES : Prior to AE Services 6.2 Super Patch 4, if a malicious or misconfigured application opened a TCP socket to the AE Services server using the port number assigned to a secure Tlink, the TSAPI Service would stop processing acsopenstream() and acsenumservernames() requests. Issue AES : The TSAPI Service has been updated for AE Services 6.2 Super Patch 4 to improve compatibility with future releases of Avaya Aura Communication Manager (CM). Specifically, this patch ensures that the attv10querystationstatus() escape service will continue to work with the next major release of CM. Issue AES :

2 Prior to AE Services 6.2 Super Patch 4, if a TSAPI application issued a cstaanswercall() request for a monitored station extension when four ASAI station domain controls already existed for that extension, the cstaanswercall() request was successful, but the TSAPI Service did not provide any private data with the corresponding CSTA Established event(s). This patch contains the following updates to the AE Services Management Console: Issue AES : The SMS Property screen has been updated to accept Communication Manager (CM) hostname, IP address or FQDN for the field labeled Default CM Host Address. Issue AES : The load speed of the Management Console screens has been improved by eliminating an unnecessary function called by the menu navigation tree. This patch contains the following updates to the AE Services on System Platform (SP) offer: Issue AES : The script responsible for applying patches has been modified to not exit with a return code of 1 for a successful patch install or removal. Issue AES : It has been noticed that once in a while the spsanity script hangs, and therefore CDOM (on System Platform) does not receive any sanity messages from the AE Services server. CDOM in response reboots the AE Services VM in attempt to recover it. With this patch, watchdog on the AE Services server keeps a watch on the spsanity script. If the spsanity scripts hangs for any reason, watchdog will restart the spsanity script. This patch contains the following updates to the Watchdog Process: Issue AES : The retry and service wait time values which are used by the watchdog process to determine how long to wait for a service to start and how long to wait before aborting the startup process of a managed service was not properly configured for the database service. This patch will resolve this possible issue. This patch contains the following updates to the AE Services Server: Issue AES and AES : This modification updates the AE Services server configuration to meet Joint Interoperability Test Command (JITC) certification. Note: The JITC modifications will not be applied to the SW Only or VMware offer types during the install process of this patch. For the VMware offer type, a list of manual instructions are specified in the Patch install instruction section of this PSN. Issue AES : Update the tzdata RPM to tzdata-2013c-2 to support the latest DST changes for Morocco and Israel. Morocco does not observe DST during Ramadan. Therefore, Morocco is expected to switch to Western European Time (WET) on July 7 and resume again to Western European Summer Time (WEST) on August 10. The period of DST in Israel has been extended until the last Sunday in October from the year 2013 onwards. Note: The patch information related to the tzdata DST issue is available in PSN Avaya Inc. All Rights Reserved. Page 2

3 Resolution Install Super Patch 4 for AE Services Workaround or alternative remediation n/a Remarks 1. What AE Services rpm/s is updated by AE Services Super Patch 4? tzdata-2013c-2.el5.i386.rpm tomcat av1.i386.rpm aesvcs-linux-config noarch.rpm aesvcs-tomcat-config noarch.rpm aesvcs-platform noarch.rpm aesvcs-userservice-config noarch.rpm aesvcs-sms noarch.rpm aesvcs-callcontrol i386.rpm aesvcs-snmp noarch.rpm aesvcs-watchdog-config noarch.rpm 2. Are there new features or enhancements included in AE Services Super Patch 4? No. 3. What must application suppliers do to be compatible with AE Services Super Patch 4? (recompile, re-link, etc.) This Super Patch is fully compatible with AE Services 6.2.x Clients and SDKs. 4. Is applying AE Services Super Patch 4 service affecting? The AE Services server will be out of service for 20 to 30 minutes while the patch is being applied. 5. With which Application Enablement Services release(s) is AE Services Super Patch 4 compatible? This patch is compatible with all AE Services offer types. 6. Is the AE Services Super Patch 4 cumulative? Yes, this patch includes the AE Services Super Patch 3 modifications. 7. Is the AE Services Super Patch 4 compatible with Application Enablement Services 5.x and 6.1.x servers? No. The AE Services Super Patch is only supported with AE Services Is the AE Services Super Patch 4 available for all Offer Types? Yes. Please use the appropriate procedure for the upgrade based on the patch install instructions specified in this PSN. Note, unlike previous installs, this patch must be installed directly on the AE Services server using a different set of installation steps. 9. What are the CM requirements for the Application Enablement Services Super Patch 4? AE Services supports CM 4.x and later. Note: Certain functionality on AE Services requires CM versions later than CM 5.x Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Please take a backup of the AE Services server data before applying the AE Services Super Patch Avaya Inc. All Rights Reserved. Page 3

4 Follow these steps to back up the AE Services server data: 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 Database Backup screen, that displays the following message: The backup file can be downloaded from Here. 3. Click the "Here" link. A file download dialog box is displayed, that allows you to either open or save the backup file (named as: servername_rsoftwareversion_mvapdbddmmyyyy.tar.gz, where ddmmyyyy is a date stamp). 4. Click Save, and download the backup file to a safe location that the upgrade will not affect. For example, save the file to your local computer or another computer used for storing backups. Download To download the AE Services patch, go to: A. Avaya Support ( On the Downloads and Documents screen, in the textbox labeled Enter Your Product Here, enter Avaya Aura Application Enablement Services and the release option 6.2.x. If the option Select a content type is displayed select the Download radio button and click the button labeled Enter. If the Documents table is displayed, select the link, View downloads, on the right-hand side of the screen above the Documents table. In the Downloads table locate and select the entry, Avaya Aura Application Enablement Services Super Patch 4 (new entries appear at the top of the list). B. PLDS ( Select View Downloads. Use the search engine to locate the available downloads for Application Enablement Services using version 6.2 to narrow the search. Locate the entry, Avaya Aura Application Enablement Services Super Patch 4 (new entries appear at the end of the list). Alternatively, you can search for the Download ID, which is AES Note: All AE Services Software Downloads are now in PLDS, while the Release Notes documents are provided on the Support Site. There will be cross references between the corresponding download entries for patches. File Name File Size MD5 Sum 620_SuperPatch_4-1zip.zip MB (120,634,880 Bytes) 8c77544f1755b8c2887d2ba a Before you start with the installation of the Patch, check the md5 checksum of the file. Run the following from the command line: md5sum 620_SuperPatch_4-1zip.zip Note: If the MD5 checksum does not match what is stated above, do not proceed with the installation of the patch. Download the patch again and check the MD5 checksum again. Patch install instructions How to check the detailed AE Services version Service-interrupting? Yes A. For the AE Services on System Platform offer, use the System Platform Management Console (and hence see whether the patch has been applied already): 1. Log into the System Platform Management Console using a browser. 2. Go to Virtual Machine Management Manage (that is the page which should come up after connecting to the web console) 3. Verify that your AE Services VM has AE Services running (the GA version shows ) 4. Click on the version information to get the detailed version information in a popup window Avaya Inc. All Rights Reserved. Page 4

5 5. If the patch is not listed, continue to the next section, How to install the Super Patch to the AE Services server. Note: When multiple patches for the AE Services server is installed, the System Platform Management Console may show each of the installed patches as Active instead of only showing the latest installed patch as Active and the previous installed patches as Installed. While other VM s may use a patch status consisting of Active, Installed and Uninstalled, AE Services currently only use the patch status Active and Uninstalled. B. For the Bundled, Software Only and VMware offer, use the AE Services Linux console (and hence see whether the patch has been applied already): 1. Start a Linux console session on the AE Services server (locally, via service port, or remotely using e.g. putty or SSH) 2. As the root user, execute the following command: swversion 3. If the patch is not listed, continue to the next section, How to install the Super Patch to the AE Services server. How to install the Super Patch to the AE Services server. Patch Installation Instructions for all AE Services offer types: 1. Start a Linux console session on the AE Services server (locally, via service port, or remotely using e.g. putty or SSH) 2. Secure copy 620_SuperPatch_4-1zip.zip to the /tmp directory on the AE Services server. 3. As the root user, execute the following from the command line: cd /tmp unzip 620_SuperPatch_4-1zip.zip./patchProcess install 4. Follow the on-screen instructions. 5. If the AE Services server is the VMware offer type and you want to apply the JITC security changes, continue to the next section, How to install the JITC changes on the AE Services VMware offer type. Otherwise proceed to the section called After applying the Super Patch, reboot the AE Services server. How to install the JITC changes on the AE Services VMware offer type: 1. Start a Linux console session on the AE Services server (locally, via service port, or remotely using e.g. putty or SSH) 2. As the root user, execute the following command: /opt/mvap/bin/configurejitc 3. After the script completes, execute the following command: chmod +x /usr/bin/ldd 4. Reboot the AE Services server After applying the Super Patch, reboot the AE Services server. A. For the AE Services on System Platform offer 1. On the System Platform Management Console, click on Virtual Machine Management Manage. 2. On the Manage Virtual Machines page, click on Application Enablement Services 3. On the Application Enablement Services page, click on Reboot B. For the Bundled, Software Only or VMware offer As the root user execute the following command from the command line: shutdown r now Post Patch Installation Verification: 2014 Avaya Inc. All Rights Reserved. Page 5

6 1. Start a Linux console session on the AE Services server (locally, via service port, or remotely, using e.g. putty) 2. Login as sroot or root 3. Run the following command to verify the installation of Super Patch 4: swversion The swversion command should return something similar to the following if Super Patch 1, 2, 3 and 4 are installed: ************* Patch Numbers Installed in this system are ************* In case you used swversion -a, the RPMs will be listed as well below the patch number this is the output: ************* Patch Numbers Installed in this system are ************* 1 aesvcs-callcontrol i386.rpm aesvcs-platform noarch.rpm aesvcs-userservice-config noarch.rpm aesvcs-watchdog-config noarch.rpm 2 tzdata-2011h-2.el5.i386.rpm aesvcs-callcontrol i386.rpm aesvcs-platform noarch.rpm aesvcs-userservice-config noarch.rpm aesvcs-watchdog-config noarch.rpm 3 tzdata-2011h-2.el5.i386.rpm aesvcs-callcontrol i386.rpm aesvcs-platform noarch.rpm aesvcs-userservice-config noarch.rpm aesvcs-watchdog-config noarch.rpm 4 tzdata-2013c-2.el5.i386.rpm tomcat av1.i386.rpm aesvcs-linux-config noarch.rpm aesvcs-tomcat-config noarch.rpm aesvcs-platform noarch.rpm aesvcs-userservice-config noarch.rpm aesvcs-sms noarch.rpm aesvcs-callcontrol i386.rpm aesvcs-snmp noarch.rpm aesvcs-watchdog-config noarch.rpm Note: Instead of the steps 1-3 as listed above, you can use the same procedure as described at the beginning of this section for AE Services on System Platform (which does not require a console login) Avaya Inc. All Rights Reserved. Page 6

7 4. Login to the AE Services Management Console using a 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: From the main menu, click Networking. Under AE Service IP (Local IP), verify that the settings are correct. Under Network Configure, verify that the settings are correct. Under Ports, verify that the settings 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. Verification See the Post Patch Installation Verification section above. Failure n/a Patch uninstall instructions Follow the Patch Uninstall Instructions: Patch Uninstall Instructions for all the AE Services offer types: 1. Start a Linux console session on the AE Services server (locally, via service port, or remotely using e.g. putty or SSH). As the root user, execute the following from the command line: cd /tmp./ patchprocess uninstall 2. Follow the on-screen instructions. Follow this procedure to restore the AE Services server data using the backup data saved during the patch install process: 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 of the backup file in the text box. Restore button, that starts the Restore process 2. Click Browse and locate the AE Services database backup file that you intend to use (For example: servername_r _mvapdb tar.gz). 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." After removing Super Patch 4 and scheduling the restore, reboot the AE Services server. A. For AE Services on System Platform 1. On the System Platform Management Console, click on Virtual Machine Management Manage. 2. On the Manage Virtual Machines page, click on Application Enablement Services 3. On the Application Enablement Services page, click on Reboot B. For the Bundled, Software Only or VMware offer As the root user, execute the following command from the command line: shutdown r now 2014 Avaya Inc. All Rights Reserved. Page 7

8 Do I have to perform any additional steps if I am uninstalling the Super Patch? No. Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks n/a Avaya Security Vulnerability Classification Not Susceptible Mitigation n/a 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 8