Avaya CFA 7.1 Patch 1 (X01) Release Notes October 13, 2014

Transcription

1 Avaya CFA 7.1 Patch 1 (X01) October 13, 2014

2 Contents 1. PURPOSE PATCH PREREQUISITES AND CONSIDERATIONS PATCH PREREQUISITES CHECK THE HEALTH SYSTEM PERFORM BACKUP ENSURE A CORRECT VERSION IS INSTALLED PATCH CONSIDERATIONS DOWNLOAD INSTRUCTIONS PATCH INSTALLATION INSTRUCTIONS GENERAL RECOMMENDATIONS INSTALLING THE PATCH VERIFYING THE PATCH INSTALLATION PATCH BACK-OUT INSTRUCTIONS BACK-OUT TIME RECOMMENDATIONS BACK-OUT PATCH POST BACK-OUT INSTRUCTIONS FALLBACK PROCESS ISSUES RESOLVED ISSUES RESOLVED IN PATCH APPENDIX A: VERIFYING SYSTEM HEALTH... 8 APPENDIX B: PRE-CHECKS... 9 October 29,

3 1. Purpose This document provides information about the Patches released for Avaya CFA 7.1 software. The following table describes the release details: Product Avaya CFA 7.1 software Patch1 Version _14682_14738_CFA_X01.bin 2. Patch Prerequisites and Considerations 2.1 Patch Prerequisites This section describes prerequisites that you must perform or items you must consider before applying the Patch Check the health system Please refer to Appendix A: Verifying System Health Perform backup The following data must be backed up before installing the Patch. Avaya AAPC application data Avaya AAPC database data Current backups are highly recommended. In the event of a catastrophic failure while installing the Patch, restoring to the backup version may be necessary. Recent backups will help to minimize data loss. For detailed backup procedures, see Maintaining and Troubleshooting Avaya AAPC guide available at Ensure a Correct Version is installed This Patch can be installed on the following versions. The Patch installer will verify the version compatibility and will display an error message if the version currently installed is not compatible with this Patch. Product Version Required Patches Avaya AAPC 7.1 software _6000 None October 29,

4 2.2 Patch Considerations Patch deployment is a service affecting procedure. Deployment of the Patch will take approximately 30 minutes. The time will vary according to the size of the database. During this procedure reports will not be available. The CMS ECH handlers will continue to write ECH files into the Linux file system. The ETL will process them once Tomcat and the Quartz Scheduler are back up. If patches are normally applied off-peak hours then the backlog should not be large. There will be latency alarms until caught up. Patch deployment should be scheduled at a time that causes minimal disruption. Also, it should not be scheduled during daily maintenance window. You may wish to communicate the plan to your end users in advance. 3. Download Instructions To download the Patch: 1. The patch should be downloaded to the server being patched. 2. If the $CCR_HOME/patches directory does not exist on the server, create it with following command: mkdir $CCR_HOME/patches 3. Request your Avaya Customer Support Representative to provide the Login, Password and a Sold-To number, which will be used to download the patch from the Avaya product download site. 4. Bring up the Avaya Product Download site in your browser 5. Select the link - Download My Software. 6. Enter the login and password provided by your Avaya Customer Support Representative. You will also be prompted for your Sold-To Number, to access the files you have been authorized to download. 1. Download the _14682_14738_CFA_X01.bin file from the Avaya support site in $CCR_HOME/patches directory. 2. Open the $CCR_HOME/patches directory and verify that the patch.bin file is downloaded properly and run the following command: October 29,

5 md5sum _14682_14738_CFA_X01.bin 7. Verify that the md5sum displays the following: 259b4e52489f00fce908ce34852ef2ba _14682_14738_CFA_X01.bin 4. Patch Installation Instructions 4.1 General Recommendations In general, do not break out of any command or kill a command while it is being executed. This will cause unpredictable results and could potentially make your system unusable. Consult your Avaya Customer Support representative if you have trouble while applying the Patch. 4.2 Installing the Patch To install the Patch: 1. Log in to the AAPC host as root or root pseudo user 2. Change the current directory by executing following command: cd $CCR_HOME/patches 3. Execute the following command to launch the Patch Install: sh _14682_14738_CFA_X01.bin apply The following is displayed: 4. Enter 1 Select a host to apply the Patch (1) (System FQDN) App:Database (IP Address) Choose 1.. or q to quit: The following is displayed: [Timestamp] Dependency check successful. A full backup must be run on this host prior to running this tool. Has a recent full backup been completed? (yes or no): October 29,

6 5. Enter yes The pre-checks are run and the following is displayed: Verifying system health... PASS Verifying that required files exist... PASS Verifying that required text files terminate with a newline... PASS Verifying the network setup... PASS Verifying that all minimum disk free space requirements are met... PASS Verifying that the current.conf file contains the correct RootHostIP... PASS Verifying miscellaneous prerequisites...pass Do you want to continue? (yes or no): To review pre-check errors please refer to Appendix B: Pre-checks. 6. Enter yes The patch will begin to install. 7. After successful completion, the following message will appear: [Timestamp] Patch installation FINISHED SUCCESSFULLY. 8. Review the logging information in $CCR_HOME/patches/runPatch.log. 4.3 Verifying the Patch installation After installing the Patch, the first line of file $CCR_HOME/patch_CFA.txt should contain the following string on each of the hosts _14682_14738_CFA_X01 For verifying the health of the system, please refer to Appendix A: Verifying System Health 5. Patch Back-out Instructions This section lists the steps required to back-out the Patch. Please consult your Avaya Customer Support Representative before deciding to back-out the Patch. 5.1 Back-out Time Recommendations Note that backing out the Patch is a service affecting procedure. Completion of the back-out procedure will take approximately 30 minutes. The time will vary according to the size of the database. During this procedure, you will not be able to run reports on the system. October 29,

7 Schedule the Patch back-out at a time that causes minimal disruption and communicate the plan to your end users in advance. 5.2 Back-out Patch To back out the Patch: 1. Log in to the AAPC host as root or root pseudo user 2. Change the current directory by executing following command: cd $CCR_HOME/patches 3. Execute the following command to launch the Patch back-out: sh _14682_14738_CFA_X01.bin backout The following is displayed: Select a host to apply the Patch (1) (System FQDN) App:Database (IP Address) Choose 1.. or q to quit: 1. Enter 1 The patch back-out process begins. After successful completion, the following message will appear on the application host: [Timestamp] Patch backout FINISHED SUCCESSFULLY. 4. Review the logging information in $CCR_HOME/patches/runPatch.log. 5.3 Post Back-out instructions After backing-out the Patch, the following string of file $CCR_HOME/patch_CFA.txt will be removed _14682_14738_CFA_X01 For verifying the health of the system, please refer to Appendix A: Verifying System Health October 29,

8 6. Fallback process If the patch apply process is not successful, use these steps to revert operation to the previous version and patch level. Please consult your Avaya Customer Support Representative before deciding to back-out the Patch. 1. Follow the patch back-out process described in this document. 2. If the patch back-out process is not successful, follow the system backup/restore process to revert back to 7.1. Apply patches to return to previous patch level. 7. Issues Resolved 7.1 Issues Resolved In Patch 1 Work item CFA-3639 CFA-3413 CFA-3640 CFA-3641 CFA-3642 CFA-332 CFA-3654 Issue resolved Fixed the issue of gauges not displaying and browser Hanging (Agent Performance Inbound call summary) Fixed the issue of monthly inbound calls summary report not displaying gauges, just legends Localized the new report created to fix Inbound Calls Summary Changed the display name of Calculations(hhh:mm:ss) for Contact Analyzer CMS to Calculations(hh:mm:ss) Fixed the issues of CPU reaching 100% utilization after 3 concurrent OBI monthly reports took 10 mins to run Localized some untranslated strings Fixed the issue of taking long time for the OBIEE landing page Appendix A: Verifying System Health This appendix provides information on verifying the system health prior to installing the Patch, after backing out the Patch, and after a successful deployment of the Patch. 1. Verify Containers and Process Elements status: Verify that all Containers and Processing Elements are in the STARTED state. If there are Containers and Processing Elements displayed in a state other than STARTED, they must be corrected. To verify the Container and Processing Element states prior and post applying the update, you can use either the AAPC Administration User Interface (UI) or Linux command line. Verification through Administration UI; October 29,

9 Select: Enterprise Select: Sites Select: HostName Verify that the hosts configured for this system have all processes started. -or- Verification through Linux command line, enter: $CSBASE/lifecycle/bin/lc ls 2. Verify reports and scheduled jobs are running properly: Open a supported web browser. Log on to the reporting interface using the following URL: Run Job History reports. Run some CFA reports. Appendix B: Pre-checks This appendix provides information on the pre-checks that are run automatically when the patch is applied prior to its installation. If there are failures or warnings, the pre-check log file can be checked to review the detail. The log file for the pre-checks is located at: $CCR_HOME/patches/<Patch version>/scripts/prechecks/logs/prechecks.sh.log 1. Verifying system health. This check verifies the containers and process element are all in the STARTED state. Refer to Appendix A. 2. Verifying that required files exist. This check verifies that the following list of files exist: $CCR_HOME/version.txt $CCR_HOME/current.conf /avaya/cmp/conf/hostinfo /avaya/cmp/conf/modstatus $CCR_HOME/modules/moduleInstallationStatus $CCR_HOME/modules/installed_modules /avaya/control/iqci_inputs /avaya/control/hosts_installed /avaya/control/oracle_installed 3. Verifying that required text files terminate with a newline. October 29,

10 This check is done to insure that the required text files end with a newline so that it can be processed correctly. If the file does not end with a newline it edits the file to insert the newline. 4. Verifying the network setup. This check validates the following network configuration items: Validates the /etc/sysconfig/network or /etc/sysconfig/network-scripts file contains the GATEWAY= entry Validates the Linux version is compatible with version listed in the $CCR_HOME/patches/<Patch Version>/patch.spec file. Validates the Oracle version is compatible with version listed in the $CCR_HOME/patches/<Patch Version>/patch.spec file. Validates hostname command displays the FQDN of the host. Validates that the DNS configuration is setup correctly. Validates network time synchronization is running using ntpstat. Validates the LDAP is running by checking if the service slapd is running. Validates loopback port is setup in /etc/hosts. Validates that each host listed in /etc/hosts can be reached. 5. Verifying that all minimum disk free space requirements are met Checks the free disk space is sufficient for patch. Minimum values are set in the $CCR_HOME/patches/<Patch Version>/scripts/prechecks/apc_info file in the section under FREESPACE BEGIN The minimum free disk space requirements may vary by patch. 6. Verifying that the current.conf file contains the correct RootHostIP Checks the current.conf root host setting and compares to the host IP the patch is running on. 7. Verifying miscellaneous prerequisites Verifies the umask setting is set to Validates the hwclock matches the system date. Verifies ntpd, slapd, and iptables are set to proper run levels. Validates the ulimit n and u settings are set to the system install values. October 29,