Product Support Notice

Transcription

1 PSN # PSN004766u Product Support Notice Original publication date: 05-Jul-16. This is Issue #01, published date: 05-Jul-16. Name of problem Solaris Critical Patch Update R41 - April 2016 Products affected Media Processing Server (MPS) 500/1000 Reference: ESPL - MPS Technical-Bulletin-121 Problem description Solaris Patchset level: 2016_04 Severity/ risk level Medium Urgency 2016 Avaya Inc. All Rights Reserved. Immediately Avaya R&D Instruction: The R41 Solaris patchset has been released. It includes the Solaris 10 CPU (Critical Patch Update) patchset from April 2016 with additional patches required for MPS. See the patch_order file for a complete list of patches. File Name - sunpatch10r41.iso MD5 Sum - f b0db46df054dd0527 SHA256 Sum - 2fa40c143fed39fcfda48820d482e5b4577dd767f82605c2017abc c Resolution See patch install instructions Workaround or alternative remediation - Customers with an active maintenance contract with Avaya may contact support to have patches installed o Use R41 as needed Remarks Notes: 1. Read this Technical Bulletin in its entirety before installing R41 on any platform. 2. Included in R41 are Java versions; but only Java 6 and Java 7 are supported in MPS4.1: a _85 b _115 c _101 d _91 3. R41 has been verified against 4.1* only. This patchset is not compatible with MPS 3.5 or older MPS platforms. This is due to some Solaris library changes. *MPS 4.1 requires an additional patches see Known Issues section. 4. R41 includes a post patchset script. It allows the user to configure the default Java version as either Java 6 or Java In order to install the R41 patchset, users will continue to execute the sunpatch10 script. a. See README files - included on the R41 DVD or.iso image. 6. The Avaya sunpatch10 script kicks off Oracle s installpatchset program to actually install the patches. This has been the case since the R25a release. sunpatch10 completes some required work related to MPS and then it kicks off installpatchset. 7. The Solaris patchset level can be determined via the uname v command

2 a. R25a - OS version: Generic_ b. R27 - OS version: Generic_ c. R29 - OS version: Generic_ d. R31 - OS version: Generic_ (note: -03 was the base kernel. -04 was added by Avaya) e. R32 - OS version: Generic_ f. R33 - OS version: Generic_ g. R34 - OS version: Generic_ (note: -13 was the base kernel. -14 was added by Avaya) h. R35 - OS version: Generic_ i. R36 - OS version: Generic_ j. R37 - OS version: Generic_ k. R38 - OS version: Generic_ l. R39 - OS version: Generic_ m. R40 - OS version: Generic_ n. R41 - OS version: Generic_ This Patchset was verified against MPS 4.1 only. Backup before applying the patch N/A Download N/A Patch install instructions Enhancements: 1. Java 7 - MPS platforms are moving to support Java 7 so the R41 patchset installs Java 7 on any system that does not already have it installed. a. Java 6 does, however, remain as the default active version of Java once the R41 patchset is installed. b. Important: A post patchset install script java_select can optionally reconfigure the software links so Java 7 or Java 6 will be the default active version of Java. i. MPS4.1 Execute the java_select script and make Java 7 active. 1. Java 7 A known bug associated with /opt/vps/packages/ws4.1.0/etc/perirc.csh This is resolved in Avaya patch ws Java 6 and Java 7 - A known issue with latest versions of Java that disables TLS causes MPSManager to stop working in MPS4.1. This is resolved in Avaya patches pdp and view c. See README files - included on the R41 DVD or.iso image. 2. R41 now displays the recommended minimum and actual free space for the /, /var, and /usr partitions. 3. R41 now displays the recommended minimum and actual OBP (OpenBoot Prom) firmware level for the target system. It is highly recommended that OBPs are upgraded prior to the Solaris patchset installation when found to be older than the recommended versions. In laboratory test environments, we have experienced some patchset install failures (including system hang problems) due to old OBP levels. a. Current OBP firmware upgrade SW is included on the R41 DVD for all SPARC servers used in the MPS product line. b. See OBP Firmware Upgrade section. 4. R41 allows for the option to install the Solaris patchset with or without backouts. a. sunpatch10 installs the Solaris patches with the backouts / saves deleted by default as with older versions. b. FEs must continue to utilize the default installation method as standard procedure, conserving disk space. c. There is now an option to keep the backouts, consuming additional disk space. FEs should only utilize this feature when debugging and instructed to do so by Avaya Technical Support personnel. 5. The sunpatch10 script prompts and asks a series of questions to assist the installer with these enhancements Avaya Inc. All Rights Reserved. Page 2

3 OBP Firmware Upgrade: 1. OBP info: Minimum OBP level recommendation for V120/N120: OBP Minimum OBP level recommendation for V210/V240/N240: OBP a Minimum OBP level recommendation for V215/V245: OBP Minimum OBP level recommendation for Blade100/150 WS: OBP Minimum OBP level recommendation for Ultra45 WS: OBP Minimum OBP level recommendation for T2000: OBP e Minimum OBP level recommendation for Netra T2000: OBP e Minimum OBP level recommendation for T5120/T5220/N5220: OBP f Minimum OBP level recommendation for Netra T4-1: OBP Simply mount the DVD in single user mode and cd to /(mntiso)/patches_10/packages. 3. Type: cat README_FIRMWARE SPARC PLATFORM INSTALL OBP VERSION V120/N zip OBP /10/06 V210/V240/N210/V zip OBP a V215/V zip OBP Blade100/ zip OBP /04/11 Ultra45 WS zip OBP T zip OBP e 2013/09/23 Netra T zip OBP e 2013/09/23 T5120/T zip OBP g 2016/03/11 *Netra T zip OBP /02/20 *New this Patchset 4. Copy the appropriate *.zip to a location with sufficient free hard disk space (example /mmf). a. Unzip the file and install the new firmware as per the Oracle provided Install.info and README.* instructions contained in the zip. 5. Reboot the server after the OBP firmware upgrades and make certain all is functional before moving on to the Solaris patchset installation. Restrictions: 1. The R41 patchset requires the same hard disk partitioning first introduced with the R25a patchset. For systems that are older and have not successfully installed the R25a or newer patchset please refer to Appendix A for partitioning updates and additional information. Known Issues: 1. Hard Disk Repartitioning only as required: a. Systems that have already successfully installed R25a or greater do not require repartitioning because it was already completed. i. These systems will be at a minimum OS version of: Generic_ (uname v) b. Refer to the partition tables in Appendix A. 2. Java 6 Packages: Pre R41 patchset install: It has been discovered that there are some Sol10 5/08 based MPS platforms at customer sites that do not have the appropriate Java 6 packages installed and can cause: a. An early termination of the Solaris patchset installation. b. The latest Java 6 patches not to be installed Avaya Inc. All Rights Reserved. Page 3

4 These Java packages need to be in place in order to complete the installation of the Java patches. Refer to Appendix B (Pre R41 patchset install) i. Complete the Appendix B instructions prior to the R41 patchset installation. 3. Java links: Post R41 patchset install: In a few instances the patchset installer may in the end not configure the appropriate symbolic link for Java. The patchset may link (make active) an earlier version and not the current version of The corrective action is provided here. a. Patchset installers (Field Engineers) need to check the active version of Java after the R41 patchset installation is complete i. ver _115 is current ii. Type: java version java version "1.6.0_115" iii. If not correct you can fix it manually Appendix C b. See Appendix C (Post R41 patchset install) for some further description and workaround on this known issue. 4. MPS4.1 MPSManager fails to start: a. There are changes in Java security that disables TLS in the latest Java versions. b. The solution is to install Avaya patches pdp and view Webconsole: a. Previous patchsets failed to install some patches I.E. ( ) due to the webconsole service not being in maintenance mode. To avoid this the sunpatch10 script now forces webconsole service into maintenance mode prior to patch install. On reboot the service will go back to normal. 6. Sendmail: a. Some customer sites may have modified the sendmail program, this causes the failure to install some patches I.E. ( ). Any site modification to the sendmail configuration files needs to be restored prior to patching to allow the patchset to be fully installed. /etc/mail/submit.cf /etc/mail/sendmail.cf 7. Apache fails to start in MPS4.1: a. There is a known issue with Oracle Solaris PatchSet R40 and newer with MPS4.1 that the S90apachectl Apache service fails to start because the /usr/lib is added before $MPSHOME/lib in the LD_LIBRARY_PATH b. The solution is to either install Avaya MPS patch globl or install MPS 4.1 Patch Bundle 03 and higher. Appendix A - Hard Disk Repartitioning (Pre R41 patchset install) Solaris Server - Recommended Repartitioning Table (Single Disk Systems Includes /mmf) Primary OS HDD slice Partition V210 36GB V210 V240 Netra Avaya Inc. All Rights Reserved. Page 4 V215 V245 T2000 T GB Netra T GB S0 (/) 3GB 3GB 3GB 3GB 3GB 3GB 3GB 5GB 5GB S1 swap 4GB 4GB 4GB 4GB 4GB 4GB 4GB 18GB 35GB S2 backup 34GB 68GB 68GB 68GB 68GB 68GB 68GB 137GB 279GB S3 **unassigned 100MB 104MB 104MB 104MB 104MB 104MB 104MB 3GB 5GB S4 (/)var 6GB 6GB 6GB 6GB 6GB 6GB 6GB 20GB 40GB

5 S5 (/)opt 5GB 10GB 10GB 10GB 10GB 10GB 10GB ***40GB ***73GB S6 (/usr) 5GB 5GB 5GB 5GB 5GB 5GB 5GB 10GB 30GB S7 (/)mmf 10GB 39GB 39GB 39GB 39GB 39GB 39GB 40GB 90GB Totals 33GB 67GB 67GB 67GB 67GB 67GB 67GB 136GB 278GB **Approximate *** Extra space should be allotted to /opt Solaris Server - Recommended Repartitioning Table (Dual Disk Systems - when /mmf is on secondary drive) Primary OS HDD slice Partition V210 36GB V210 V240 Netra 240 V215 V245 T2000 T GB Netra T GB S0 (/) 3GB 3GB 3GB 3GB 3GB 3GB 3GB 5GB 5GB S1 swap 4GB 4GB 4GB 4GB 4GB 4GB 4GB 18GB 35GB S2 backup 34GB 68GB 68GB 68GB 68GB 68GB 68GB 137GB 279GB S3 **unassigned 100MB 104MB 104MB 104MB 104MB 104MB 104MB 3GB 5GB S4 (/)var 6GB 6GB 6GB 6GB 6GB 6GB 6GB 20GB 40GB S5 (/)opt ***15G ***49G ***49GB ***49GB ***49GB ***49GB ***49GB ***80GB ***163GB S6 (/usr) 5GB 5GB 5GB 5GB 5GB 5GB 5GB 10GB 30GB Totals 33GB 67GB 67GB 67GB 67GB 67GB 67GB 136GB 278GB **Approximate *** Extra space should be allotted to /opt Appendix B Java 6 Packages (Pre R41 patchset install) Step 1: Verify if system has Java 6 packages installed or not. Run pkginfo grep SUNWj6 command to find out if system has Java 6 packages installed or not. Output should have 8 packages as listed below. Ignore the java version number in the parentheses below. pkginfo grep SUNWj6 system SUNWj6cfg JDK 6.0 Host Config. (1.6.0_26) system SUNWj6dev JDK 6.0 Dev. Tools (1.6.0_26) system SUNWj6dmo JDK 6.0 Demo Programs (1.6.0_26) system SUNWj6dmx JDK bit Demo Programs (1.6.0_26) system SUNWj6dvx JDK bit Dev. Tools (1.6.0_26) system SUNWj6jmp JDK 6.0 Man Pages: Japan (1.6.0_26) This package is optional - not needed system SUNWj6man JDK 6.0 Man Pages (1.6.0_26) system SUNWj6rt JDK 6.0 Runtime Env. (1.6.0_26) system SUNWj6rtx JDK bit Runtime Env. (1.6.0_26) Important: Proceed to the next step only if no output is generated by the pkginfo grep SUNWj6 pipeline. Step 2: Download jdk1_6_0_31_pkgs.tar.z compressed tar file from ESPL search: MPS-TECHNICAL-BULLETIN-107 OR look in the Patches_10/packages directory on the R41 DVD Place.tar.Z file in /mmf (can be other dir with available space) 2016 Avaya Inc. All Rights Reserved. Page 5

6 Step 3: Uncompress/untar the jdk1_6_0_31_pkgs.tar.z cd /mmf uncompress jdk1_6_0_31_pkgs.tar.z /usr/sfw/bin/gtar xvf jdk1_6_0_31_pkgs.tar Step 4: Install Java 6 packages using pkgadd command and follow the prompts. cd jdk1_6_0_31_pkgs pkgadd -d. SUNWj6rt SUNWj6dev SUNWj6cfg SUNWj6man SUNWj6dmo SUNWj6jmp SUNWj6rtx SUNWj6dvx SUNWj6dmx Step 5: Verify Java 6 packages installed pkginfo grep SUNWj6 system SUNWj6cfg JDK 6.0 Host Config. (1.6.0_31) system SUNWj6dev JDK 6.0 Dev. Tools (1.6.0_31) system SUNWj6dmo JDK 6.0 Demo Programs (1.6.0_31) system SUNWj6dmx JDK bit Demo Programs (1.6.0_31) system SUNWj6dvx JDK bit Dev. Tools (1.6.0_31) system SUNWj6jmp JDK 6.0 Man Pages: Japan (1.6.0_31) This package is optional - not needed system SUNWj6man JDK 6.0 Man Pages (1.6.0_31) system SUNWj6rt JDK 6.0 Runtime Env. (1.6.0_31) system SUNWj6rtx JDK bit Runtime Env. (1.6.0_31) Step 6: Run the R41 sunpatch10 script to patch Java after a packages install. Appendix C Java Links (java_select) (Post R41 patchset install) Java Summary: (Java 1.6 or 1.7) The patchset installer (FE) needs to verify the version of Java running after the patchset is completed. It should be version "1.6.0_115" after R41 is installed. For Java version other than 1.6.0_115: if the version returns at something older than this version follow the instruction in the WORKAROUND section of this document. WORKAROUND: PROBLEM: root@mpsap1-a {6} java -version java version "1.5.0_xx" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_XX) Java HotSpot(TM) Server VM (build 1.5.0_XX, mixed mode) root@mpsap1-a {7} which java //bin/java root@mpsap1-a {34} ls -l /usr grep java 2 lrwxrwxrwx 1 root other 15 Sep 24 16:17 java -> jdk/jdk1.5.0_34/ //here is the problem this link is set to the wrong java path. 2 lrwxrwxrwx 1 root other 15 Mar java_savedby1.6.0_13 -> jdk/jdk1.5.0_34 FIX: (Java 7) 2016 Avaya Inc. All Rights Reserved. Page 6

7 (Note: the java_select script is located in the Patches_10 directory of the Patchset DVD) #./java_select java version "1.6.0_115" Java(TM) SE Runtime Environment (build 1.6.0_XXX) Java HotSpot(TM) Server VM (build 20.XXX, mixed mode) MPS primarily supports Java7 and JAVA6. Do you wish to configure the systems with Oracle's latest JAVA7? (Default is N for JAVA6), (Q for no change) [y,n,?,q] y JAVA 7 is being configured lrwxrwxrwx 1 root root 15 Nov 25 16:24 java -> /usr/jdk/latest java version "1.7.0_101" Java(TM) SE Runtime Environment (build 1.7.0_XXX) Java HotSpot(TM) Server VM (build 24.XXX, mixed mode) Or FIX: (Java 6) MPS primarily supports Java7 and JAVA6. Do you wish to configure the systems with Oracle's latest JAVA7? (Default is N for JAVA6), (Q for no change) [y,n,?,q] n JAVA 6 is being configured lrwxrwxrwx 1 root root 20 May 29 12:03 java -> /usr/jdk/jdk1.6.0_115 java version "1.6.0_115" Java(TM) SE Runtime Environment (build 1.6.0_XXX) Java HotSpot(TM) Server VM (build , mixed mode) Collect data: a series of commands can be executed to collect data and report back to Avaya s Technical Support group if Java version problems are not resolved with the workaround. 1. date 2.hostname 3.uname -a 4.java -version 5.which java 6. ls -l /usr/ 7. ls -l /usr/jdk 8. ls -l /var/sadm/patch/12513* Collect log files: (examples) /var/sadm/install_data/s10s_rec_patchset_short_ _ log /var/sadm/install_data/s10s_rec_patchset_verbose_ _ log /var/sadm/prep_log Verification Failure Patch uninstall instructions 2016 Avaya Inc. All Rights Reserved. Page 7

8 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. Business Partner Notes Additional information for BusinessPartners Avaya Notes Additional information for Tier 3, Tier 4, and development 2016 Avaya Inc. All Rights Reserved. Page 8