Integrated Management 6.0 Performance and Administration Release Notes - Service Pack 8

Transcription

1 Integrated Management 6.0 Performance and Administration Release Notes - Service Pack 8 Release 6.0 SP8 Issue 1 December 2012

2 2012 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Websites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Website: Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by the said Avaya reseller and not by Avaya. Licenses The software license terms available on the Avaya Website, are applicable to anyone who downloads, uses and/or installs Avaya software, purchased from Avaya Inc., any Avaya affiliate, or an authorized Avaya reseller (as applicable) under a commercial agreement with Avaya or an authorized Avaya reseller. Unless otherwise agreed to by Avaya in writing, Avaya does not extend this license if the software was obtained from anyone other than Avaya, an Avaya affiliate or an Avaya authorized reseller, and Avaya reserves the right to take legal action against you and anyone else using or selling the software without a license. By installing, downloading or using the software, or authorizing others to do so, you, on behalf of yourself and the entity for whom you are installing, downloading or using the software (hereinafter referred to interchangeably as you and end user ), agree to these terms and conditions and create a binding contract between you and Avaya Inc. Or the applicable Avaya affiliate ( Avaya ). Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License types Designated System(s) License (DS): End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU): End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Named User License (NU): End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (for example, webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR): Customer may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). (See Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law.ll Third Party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Website: Preventing toll fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Website: Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to:securityalerts@avaya.com. Trademarks Avaya and Avaya Aura are trademarks of Avaya Inc. The trademarks, logos and service marks ( Marks ) displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. All non-avaya trademarks are the property of their respective owners. Linux is a registered trademark of Linus Torvalds. Downloading documents For the most current versions of documentation, see the Avaya Support Website: Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Website:

3 Contents Performance and Administration Release 6.0 SP PSN Enhancements delivered in Performance and Administration 6.0 SP Fixes delivered in Performance and Administration 6.0 SP Upgrading Red Hat Enterprise Linux 5.x to Red Hat Enterprise Linux Supported Upgrade Paths for P & A Service Pack 8 on RHEL YUM support for Red Hat Linux platforms Installation of Performance and Administration 6.0 SP Integrated Management software line-up for Release 6.0 SP Requirements/Enhancements delivered in Performance and Administration 6.0 SP Fixes delivered in Performance & Administration 6.0 SP Enhancements delivered in Performance and Administration 6.0 SP Fixes delivered in Performance and Administration 6.0 SP Known issues in Performance and Administration 6.0 SP Installation of Performance and Administration 6.0 SP Integrated Management Software Line-up for 6.0 SP Fixes delivered in Performance and Administration 6.0 SP Known issues in Performance and Administration 6.0 SP Enhancements delivered in Performance and Administration 6.0 SP Fixes delivered in Performance and Administration 6.0 SP Known issues in Performance and Administration 6.0 SP User guidelines for JRE 1.6.0_19 and later versions Enhancements delivered in Performance and Administration 6.0 SP Fixes delivered in Performance and Administration 6.0 SP Known issues in Performance and Administration 6.0 SP Key notes for SSL enabled users for 6.0 SP Enhancements delivered to Performance and Administration 6.0 SP Fixes in Fault and Performance Manager 6.0 SP Fixes in MultiSite Administration 6.0 SP Enhancements in Performance and Administration 6.0 SP Fixes in Performance and Administration 6.0 SP Known issues in Performance and Administration 6.0 SP P&A Release Notes 6.0 SP8 December

4 Contents 2 P&A Release Notes 6.0 SP8 December 2012

5 Performance and Administration Release 6.0 SP 8 Integrated Management service packs are cumulative. Integrated Management - Performance and Administration (P & A) Release 6.0 Service Pack 8 includes modifications and enhancements specific to this service pack and from earlier service packs, if any. Modifications are grouped by applications as listed in the tables in this document. This Service Pack includes: Enhancements delivered in Performance and Administration 6.0 SP 8 Fixes delivered in Performance and Administration 6.0 SP8 To learn about the installation of Performance and Administration 6.0 SP7, read the following topic: Installation of Performance and Administration 6.0 SP 8 For the list of software line up that the various Integrated Management applications for Release 6.0 SP7 support, read the following topic: Integrated Management software line-up for Release 6.0 SP 8 PSN Some problems are also documented as Product Support Notices (PSN). The PSN number defines the related document and appears in the Problem column in the tables. To read the PSN description online: 1. Go to the Avaya Support site at 2. Click Products. The Web page displays a pop-up window. Enter the name of the product in the window, in this case Avaya Aura TM System Manager You can even select the product from the A-Z list in the bottom right corner of the pop-up window. 3. On the Products page, click Product Notices > Product Support Notices. The Product Support Notices page lists the pdf document with the PSN number in the table under Titlle. 4. Click the PSN title link to open the PSN: P&A Release Notes 6.0 SP8 December

6 Enhancements delivered in Performance and Administration 6.0 SP 8 The work item numbers are only for internal reference, to be used by Avaya engineers and do not in any way impact the end users of this document. Table 1: Enhancements delivered in MultiSite Administration 6.0 SP 8 Work item Enhancement wi wi wi MultiSite Administration now supports the Enhanced Callr-Info display for 1-line phones field on the Station object. MultiSite Administration now supports the Block Exclusion Notification field on COR Object. MultiSite Administration now supports the Mute in Shared Control field for 96x1 and H.323 set types. Table 2: Enhancements delivered in Fault and Performance Manager 6.0 SP 8 Work item Enhancement wi If you modify the Xmx parameter in the ENV file and mfpmconfig, then keep the Java heap size as it is after Service Pack 8 installation.. Fixes delivered in Performance and Administration 6.0 SP8 The work item numbers are only for internal reference, to be used by Avaya engineers and do not in any way impact the end users of this document. Table 3: Fixes in Performance and Administration 6.0 SP 8 Work item Problem Solution 2 P&A Release Notes 6.0 SP8 December 2012

7 Fixes delivered in Performance and Administration 6.0 SP8 wi wi The jar signer certificate expried for NCM jars. The installer did not give a warning message when the / tmp/avaya directory was not there and the installation failed. This issue is resolved in the current The installer displays a warning message if the /tmp/avaya directort is not present. Table 4: Fixes delivered in Integrated Management Database 6.0 SP 8 Work item Problem Solution wi When Integrated Management Database disabled a user due to inactivity, admin was unable to re-enable the user. Admin can now enable a user disabled due to inactivity. Table 5: Fixes in Fault and Performance Manager 6.0 SP 8 Work item Problem Solution wi wi wi The NCM jars were signed using new certificate keystore files. After you modified and saved a filter setting, the NMS box is not checked. NMC exceptions are logged when you launched Fault and Performance Manager applet. This issue is resolved in the current The NMS box is now checked after you modify and save a filter setting. This issue is resolved in the current Table 6: Fixes in MultiSite Administration 6.0 SP 8 Work item Problem Solution wi The system did not display the Change Password screen when you clicked the Change Password link in the MultiSite Administration login screen. The system now displays the Change Password screen. P&A Release Notes 6.0 SP8 December

8 wi wi wi When a user logged into MultiSite Administration. the user login time was not updated in the user_last_login table causing the user to be disabled due to inactivity. The jar signer certificate expired in MultiSite Administration. CISCO ASA server did not forward s received from MultiSite Administration. This issue is resolved in the current This issue is resolved in the current CISCO ASA server now forwards s received from MultiSite Administration. Upgrading Red Hat Enterprise Linux 5.x to Red Hat Enterprise Linux 5.8 To upgrade Red Hat Enterprise Linux 5.x to Red Hat Enterprise Linux 5.8, perform the following steps: 1. Insert the Red Hat Enterprise Linux 5.8 CD into the CD-ROM drive, restart the server and start the Red Hat Enterprise Linux System Installer in graphical mode. Follow the prompts until the system displays the Red Hat Enterprise Linux 5, installation guide page. 2. Click Next. The system displays the Language Selection page. 3. Select the appropriate language, and then click Next. System displays the keyboard configuration page. 4. Select the appropriate keyboard and click Next. The system displays the Installation Number dialog box. 5. Enter your Red Hat installation number, and then click OK. OR You can choose skip entering installation number, click OK. The system displays the Install or Upgrade page. 6. Click Upgrade an existing installation, and click Next. The system displays the GRUB Boot Loader page. 4 P&A Release Notes 6.0 SP8 December 2012

9 Supported Upgrade Paths for P & A Service Pack 8 on RHEL Click the appropriate option button, and then click Next. The system displays the Begin Upgrade page. 8. Click Next. The system displays the Required Install Media dialog box. 9. Click Continue. The system displays the installation status bar. 10. Proceed with the upgrade. When the upgrade is complete, remove the CD, and click Reboot. Supported Upgrade Paths for P & A Service Pack 8 on RHEL 5.8 Performance and Administration Service Pack 7 and above support Red Hat Enterprise Linux 5.8 (32 bitand 64 bit). The following are the upgrade paths for installing SP8 on Red Hat Enterprise Linux For a Fresh OS RHEL 5.8 Install: a. Install Red Hat Enterprise Linux 5.8 (with Web server support). b. Install 6.0 GA, and apply the SP8 binary. 2. For OS Upgrade from RHEL 5.x to RHEL 5.8 : a. Take a backup of the existing data (You can use the IMbackup <filename> command or the Avaya > Integrated Management Data Backup and Restore Utility). b. Upgrade the OS to RHEL 5.8. c. Run the Up2Date Config (Application > Avaya > Up2Date Config) utility d. Reboot the system. e. Run the PA6.0_SP8_02.bin binary. f. Reboot the system. g. Restore the backed up data. (You can use the IMrestore <filename> command or the Avaya > Integrated Management Data Backup and Restore Utility). 3. After installing SP8, to upgrade the OS from RHEL 5.x to RHEL 5.8: a. Upgrade the OS to RHEL 5.8. b. Run the Up2Date Config (Application > Avaya > Up2Date Config) utility. c. Reboot the system. P&A Release Notes 6.0 SP8 December

10 YUM support for Red Hat Linux platforms Yellow dog Updater, Modified (YUM) is a program for updating Red Hat Linux packages. Use YUM to download and install new software, and to upgrade the operating system. Performance and Administration 6.0 SP8 supports YUM update. When you update the Red Hat Linux version, the configuration file changes. This change modifies the configuration settings for tomcat, apache, and other third party RPMs, and causes application failure. To resolve this issue, perform the following steps: 1. On the main menu, click Avaya > Up2Date Config. Wait for the terminal window to close. 2. Restart the system to start Avaya services. Installation of Performance and Administration 6.0 SP 8 Read the instructions provided in this section before you install the common binary for Multisite Administration, Fault and Performance Manager, and Integrated Management Database. During the installation, the script checks the product versions that are currently installed. The script prompts you to apply the software update. Installing the common binary, PA6.0_SP8_02.bin: 1. Save the PA R6.0 update file to your computer. Follow the directions to save the update file to a directory. Make a note of the location. 2. Optional: If you saved the update file on your Windows computer, then FTP or SCP the update file (in the binary mode) to the Linux server where the product resides. 3. Log in as root on the Linux server. 4. Open a terminal window. Enter the cd command to go to the directory where you saved the update file. 5. At the command prompt, start the install script. Type sh PA6.0_SP8_02.bin, and press Enter. Answer the questions prompted to install the software update. Reboot your system after installation. 6. To install in the console mode, type sh PA6.0_SP8_02.bin -- -console, and press Enter. Then answer the questions prompted to install the software update. Reboot your system after installation. The installer does not run mfpmconfig in the console mode. You must manually run this after applying and uninstalling the service pack in the console. 6 P&A Release Notes 6.0 SP8 December 2012

11 Installation of Performance and Administration 6.0 SP 8 Integrated Management now supports: RHEL 5.8 for SP7 and above, RHEL 5.5 for earlier releases Red Hat AS/ES 4.8 and earlier versions. Internet Explorer 8 running on a Microsoft Windows 7 Professional (x86 and x64) machine as client to access the Performance and Administration applications. P&A Release Notes 6.0 SP8 December

12 Integrated Management software line-up for Release 6.0 SP 8 The following tables list the software line up which includes the various operating systems, third-party packages, and the virtual machines that the various Integarted Management applications support for Release 6.0 SP 8: Site Administration 6.0 SP 8 Table 7: Site Administration 6.0 SP 8 Operating systems Windows 7 Professional SP1 (32-bit and 64-bit) Windows XP Professional with SP 3 Windows Vista (32-bit and 64-bit) Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 R2 server Third party applications and packages Virtual machine support VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 VMware ESXi 5.0 Additional notes 8 P&A Release Notes 6.0 SP8 December 2012

13 Integrated Management software line-up for Release 6.0 SP 8 Network Management 6.0 SP 8 Table 8: Network Management 6.0 SP 8 server Operating systems Third party applications and packages Virtual machine support Additional notes Windows 7 Professional SP1 (32-bit and 64-bit) Windows XP Professional with SP 3 Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 Server R2 with SP1(Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; without Hyper-V; 32-bit and 64-bit) Windows 7 SP1 JRE Version _24 Apache Server Version PostgreSQL Version VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 VMware ESXi 5.0 NM Serveron Windows 2008 Server R2 (Standard and Enterprise) & Windows 7 Professional 64-bit is only supported on Intel 64-bit processors. AMD 64-bit processors are not supported for these OperatingSyste ms P&A Release Notes 6.0 SP8 December

14 Table 9: Network Management 6.0 SP 8 client Operating systems Third party applications and packages Virtual machine support Additional notes Windows 7 Professional SP1 (32-bit and 64-bit) Windows XP Professional with SP3 Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 Server R2 with SP1(Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; without Hyper-V; 32-bit and 64-bit) Windows 7 SP1 JRE Version _24 Browsers - IE6, IE7, IE8, IE9, Firefox 3.5, Firefox 3.6 (higher versions of FF will also work, but have not been tested extensively) VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 VMware ESXi 5.0 There is only support for IE8 on Windows professional Ensure that the JRE minor version is equal to or greater than the minor version of the server It is recommended that the JRE minor version be equal to or greater than the servers minor version 10 P&A Release Notes 6.0 SP8 December 2012

15 Integrated Management software line-up for Release 6.0 SP 8 Performance and Administration 6.0 SP 8 Table 10: Performance & Administration 6.0 SP8 P&A server Operating systems Third party applications and packages Virtual machine support Additional notes RHEL 5.8, RHEL 5.5 and earlier versions (x86 and x64) JRE Version _32 Apache ServerVersion Tomcat Version PostgreSQL Version ) VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 VMware ESXi 5.0 P&A Release Notes 6.0 SP8 December

16 Table 11: Performance & Administration 6.0 SP8 P&A client Operating systems Third party applications and packages Virtual machine support Additional notes Windows 7 Professional (32-bit and 64-bit) Windows XP Professional with SP 3 Windows Vista (32-bit and 64-bit) Windows 2003 Serverwith SP2 (Standard and Enterprise) Windows 2008 Server R2 with SP1 (Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; withouthyper-v ; 32-bit and 64-bit) JRE Version _32 Browsers - IE6, IE7, IE8, FF 3.5, FF 3.6 (later versions of FF will also work, but have not been tested extensively) VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 VMware ESXi 5.0 Only IE8 is supported on Windows 7 Professional It is recommended that the JRE minor version be equal to or greater than the minor version of the server 12 P&A Release Notes 6.0 SP8 December 2012

17 Requirements/Enhancements delivered in Performance and Administration 6.0 SP 7 Requirements/Enhancements delivered in Performance and Administration 6.0 SP 7 The work item numbers are for internal reference, only to be used by Avaya engineers and do not in anyway impact the end users of this document. Table 12: Requirements/Enhancements delivered in IMD 6.0 SP7 wi wi wi wi wi wi Performance and Administration 6.0 SP7 supports JRE version 1.6.0_32 on client side as well as on the server side. Performance and Administration 6.0 SP7 now supports Tomcat Integrated Management Database 6.0 SP7 now consists of a combo box version for messaging systems. Integrated Management Database 6.0 SP7 now supports Automatic Re-Index task. Integrated Management Database 6.0 SP7 now supports Automatic Vaccum task. Performance and Administration 6.0 SP7 now supports Red hat Enterprise Linux 5.8 along with RHEL 5.5 and earlier versions. Table 13: Requirements/Enhancements delivered in Fault & Performance Manager 6.0 SP7 wi wi Fault and Performance Management (FPM) 6.0 SP7 supports Automatic Re-Indexing of FPM postgres database. Fault and Performance Management (FPM) 6.0 SP7 supports Automatic Vaccuming of FPM postgres database. P&A Release Notes 6.0 SP8 December

18 Table 14: Requirements/Enhancements delivered in MultiSite Administration 6.0 SP7T wi Multisite Administration 6.0 SP7 supports VDN Override for ISDN Trunk ASAI Messages option in VDN administration. wi wi wi wi Multisite Administration 6.0 SP7 supports Time Zone field for both Avaya Aura Messaging 6.1 and 6.2. Multisite Administration 6.0 SP7 supports TUI Message Order for Modular Messaging (MM) 5.2 and Modular Messaging (MM) 5.1. Multisite Administration 6.0 SP7 supports a repair tool for EcsUser Database Files and back up task for EcsUser Database Files. Multisite Administration 6.0 SP7 supports Add ListCmdTimeOut parameter as a configirable option in the switch.ini file. Fixes delivered in Performance & Administration 6.0 SP7 The work item numbers are for internal reference, only to be used by Avaya engineers and do not in anyway impact the end users of this document Table 15: Fixes delivered in Integrated Management Database 6.0 SP7 Work item Problem Solution wi wi Install script displayed the message installation successful even after rpm installation failed. On IMD element page, "Allowed Users" cannot be selected if a string of a username is longer than 13 characters. This issue has been resolved in the 6.0 SP7. You can now select "Allowed Users", even if the username string has 13 or more charcters. Table 16: Fixes delivered in MultiSite Administration 6.0 SP7 Work item Problem Solution wi wi Extended tenant partition range (SA8993) was not available for Agent Login ID and Terminal Extension group objects. User was unable to delete NPA value on route pattern form. This issue has been resolved in the 6.0 SP7. You can now, delete the NPA value on route pattern form. 14 P&A Release Notes 6.0 SP8 December 2012

19 Enhancements delivered in Performance and Administration 6.0 SP 6 Table 16: Fixes delivered in MultiSite Administration 6.0 SP7 wi wi wi wi wi wi CMM/Messaging with SSL failed to run on a 64-bit operating system. Ping alarms of voice systems and adjuncts were not visible in UI After applying Service Pack 6 the collection tasks were not scheduled. Collections tasks in Fault and Perfomance Management were stuck as the application encountered Too many open files exception. Applet tampering messages were displayed intermittently in the Fault and Performance Manager. During collection Out Of Memory exceptions were thrown in Fault and Performance Manager CMM/Messaging with SSL now runs on a 64-bit operating system. This issue has been resolved in the 6.0 SP7. This issue has been resolved in the 6.0 SP7. This issue has been resolved in the 6.0 SP7. This issue has been resolved in the 6.0 SP7. This issue has been resolved in the 6.0 SP7. Enhancements delivered in Performance and Administration 6.0 SP 6 The work item numbers are for internal reference, only to be used by Avaya engineers and do not in anyway impact the end users of this document. Table 17: Enhancements delivered in Integrated Management Database 6.0 SP 6 Table 18: 1.wi If you enter more than 300 elements in the Integrated Management database, the system displays a popup warning window. P&A Release Notes 6.0 SP8 December

20 Table 18: 2.wi When you use the import function to import the elements from a file, you cannot add more than 300 elements. The import script now checks the maximum number of elements you can import. 3. Integrated Management Database now supports Communication Manager 6.2, Communication Manager Messaging 6.2. Table 19: Enhancements delivered in Fault and Performance Manager 6.0 SP 6 Table 20: 1. wi The system displays the correct icon in the Fault and Performance Manager user interface which indicates whether the Enterprise Survivable Server switch is active or inactive. 2. wi You can incorporate a status tool in Fault and Performance Manager to check the daily scheduled tasks. 3. Fault and Performance Management now supports Communication Manager 6.2, Communication Manager Messaging 6.2. Table 21: Enhancements delivered in Multisite Administration 6.0 SP 6 Table 22: 1. wi MultiSite Administration now supports Communication Manager Messaging 6.2 with Base DN "ou=people, dc=avaya". 2. wi MultiSite Administration now supports the Time of Day Lock field. 3. wi MultiSite Administration now supports the following new set types: 9608, 9611, 9621, 9641, 9404, and wi MultiSite Administration now supports Communication Manager P&A Release Notes 6.0 SP8 December 2012

21 Fixes delivered in Performance and Administration 6.0 SP 6 Fixes delivered in Performance and Administration 6.0 SP 6 The work item numbers are for internal reference, only to be used by Avaya engineers and do not in anyway impact the end users of this document. Table 23: Fixes delivered in Integrated Management Database 6.0 SP 6 Table 24: Integrated Management Database Work item Problem Solution 1. wi Lightweight Directory Access Protocol support issues such as: 1. Integrated Management database allowed the addition of Lightweight Directory Access Protocol group with group no.0 2. wi Integrated Management Database exported all the SNMP configuration details and import failed, using this file. 3. wi Integrated Management Database was unable to lauch Multi Vantage Fault and Performance Manager(MPFM) when FQDN was not registered in the corporate DNS Integrated Management Database now, does not allow to add light weight directory access protocol with group 0 with fix of this issue. This issue has been fixed in this The issue has been fixed in this P&A Release Notes 6.0 SP8 December

22 Table 24: 4. wi Integrated Management Database handling of the LDAP account configuration was case-sensitive. 5. wi FPM Server Status Utility in Integrated Management database had the following issues: 1. When the Status Button was selected Permission Denied exceptions were thrown. 2. When the LvlUtil Button was selected Permission Denied exceptions were thrown. 3. Integrated Management Database page froze when command line arguments were specified in the Command Options box. Even after the page froze, the corresponding process was running in the background. 4. The CollShed button was removed from the Fault and Performance Manager server status page. Configuration of LDAP accounts is no longer case sensitive. All these issues have been fixed in this Table 25: Fixes delivered in Multisite Administration 6.0 SP 6 Table 26: Multisite Administration Work item Problem Solution 1. wi Help for New Station template showed an Http 404 error. 2. wi You could not add a station with the set type 9408 DCP. 3. wi While configuring a station, the COR field is required. An error occured when you added a station with the set type wi You could not duplicate 8 digit XMobile extension. 6. wi The EC500 State field was missing in the 96xx templates The system no longer displays this error. You can now add a station using the set type 9408 DCP. The issue is now fixed in this Now, you can duplicate the 8 digit XMobile extension The 96xx templates have been updated with the EC500 State field. 18 P&A Release Notes 6.0 SP8 December 2012

23 Fixes delivered in Performance and Administration 6.0 SP 6 Table 26: 7.wi MultiSite Administration did not show the correct status of the Xmobile option when you selected DECT. 8. wi HTTP Status /mcm/mcmhelp/ MCM_Screens_Sta_Mgr/ Station_Administration_screen_.htm appeared while adding a station from system manager 9. wi Only reason code 0-9 was available for AuxWork station button instead of wi Find Extension in report manager did not show the extensions when you selected multiple stations. MultiSite Administration now shows the correct status of the XMobile option if you select DECT. The issue in now fixed in this The issue in now fixed in this Find Extension option shows extensions even when you select multiple stations. Table 27: Fixes delivered in Fault and Performance Manager 6.0 SP 6 Table 28: Fault and Performance Manager Work item Problem Solution 1. wi Applying restored defaults did not apply filters on Communication Manager. 2. wi The report scheduler stopped working. 3. wi Changing the severity of an alarm on Alarms/Filter form did not reflect in the Fault & Performance Management exception output. 4. wi AVP resulted into an exception in Fault & Performance Management 5.2 SP7. 5. wi When Voice System/Adjunct generates and sends an alarm or trap and the primary server was incorrectly configured, the secondary server did not work with Fault and Performance Manager to deliver the . Restoring defaults now applies filters on Communication Manager. The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The secondary server now works with Fault and Performance Manager to deliver the . P&A Release Notes 6.0 SP8 December

24 Table 28: 6. wi After the primary service failed, an exception did not get logged. 7. wi Login traps did not appear in the Exception output. 8. wi When you set the severity to All or None, the filters were set incorrectly. 9. wi The system did not generate a trap when you set a filter on Communication Manager instead of both Communication Management and Fault and Performance Management. 10. wi The system did not save the filters properly for the 5.2 voice systems. 11. wi SNMP V2c trap in Fault and Performance Manager showed incorrect timetick. 12. wi The port configuration process stopped working and the status window froze. 13. wi notification stopped working, even after CM detected an alarm. 14. wi When you add a voice system, after deletion of that system,dbcpserver table showed incorrect data. 15. wi The system did not process traps for voice systems. The system logs an exception when the primary service fails. Login traps now appear in the Exception output. The issue has been fixed in this The system now generates a trap after a filter is set on Communication Manager instead of both Communication Management and Fault and Performance Management. The issue has been fixed in this SNMP V2c trap in Fault and Performance Manager now shows the correct timetick. The port configuration gets processed and status window does not hang. notification now functions smoothly. This issue now has been fixed in this The system now processes traps for voice systems. 16. wi ESS clusters view was not enabled. You can now see the ESS clusters view menu. 17. wi Configuration for ESS server showed incorrect data type error. 18. wi Voice adjuncts were unable to process SNMP V1 traps. The issue has been fixed in this Voice adjuncts now process SNMP V1 traps. 20 P&A Release Notes 6.0 SP8 December 2012

25 Known issues in Performance and Administration 6.0 SP 6 Known issues in Performance and Administration 6.0 SP 6 The work items are for reference by Avaya engineers only, and in no way impact the end users of this document. Table 29: Known issues in Performance and Administration 6.0 SP 6 Table 30: Work item Known issue Workarounds 1. wi When a voice system is added after deletion dbcpserver table shows incorrect data 2. wi When MFPM.ignoreSSGInadsTrap is to false in PMProp file, then Inads trap is triggered explicitly. 3. wi Applet tempering messages were observed intermittently and when you click on the popup the window does not get launched. 4. wi When you run the IMautoremotebackup tool manually, the backup files are transferred smoothly. However there are some cipher exceptions. 5. wi Communication Manager Messaging and Messaging do not run on a 64-bit operating system. 6. wi Unable to login the MultiSite Administration application using the LDAP active directory credentials. 7.wi Save As feature in Report Management of FPM application is not working. Run fix counts and then run collection on all CMs to solve the issue. Set this value to true which stops all the inad traps. Reopen the web interface. P&A Release Notes 6.0 SP8 December

26 Installation of Performance and Administration 6.0 SP 6 Integrated Management now supports: RHEL 5.5 and earlier releases. Red Hat AS/ES 4 version 8 and earlier versions. Internet Explorer 8 running on a Microsoft Windows 7 Professional (x86 and x64) machine as client to access Performance and Administration applications. Read the instructions provided in this section before you install the common binary for Multisite Administration, Fault and Performance Manager, and Integrated Management Database. During the installation, the script checks the product versions that are currently installed. The script prompts you to apply the software update. Installing the common binary, PA6.0_SP6_04.bin: 1. Save the PA R6.0 update file to your computer. Follow the directions to save the update file to a directory. Make a note of the location. 2. Optional: If you saved the update file on your Windows computer, then FTP or SCP the update file (in the binary mode) to the Linux server where the product resides. 3. Log in as root on the Linux server. 4. Open a terminal window. Enter the cd command to go to the directory where you saved the update file. 5. At the command prompt, start the install script. Type sh PA6.0_SP6_04.bin and press Enter. Then answer the questions prompted to install the software update. 6. To install in the console mode, type sh PA6.0_SP6_04.bin -- -console and press Enter. Then answer the questions prompted to install the software update. The installer does not run mfpmconfig in the console mode. You must manually run this after applying and uninstalling the service pack in the console. 22 P&A Release Notes 6.0 SP8 December 2012

27 Integrated Management Software Line-up for 6.0 SP 6 Integrated Management Software Line-up for 6.0 SP 6 The following tables give the Operating Systems, Third-party packages and Virtual Machines that the various Integrated Management applications.support. Site Administration 6.0 SP 6 Table 31: Site Administration 6.0 SP 6 Table 32: Operating Systems Third-party Applications & Packages Virtual Machine Support Additional Notes Windows 7 Professional SP1 (32-bit and 64-bit) Windows XP Professional with SP 3 Windows Vista (32-bit and 64-bit) Windows 2003 Server with SP2 (Standard and Enterprise) NA VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX P&A Release Notes 6.0 SP8 December

28 Network Management 6.0 SP 6 Table 33: Network Management 6.0 SP 6- Network Management Server Table 34: Operating Systems Third-party Applications & Packages Virtual Machine Support Additional Notes Windows 7 Professional (32-bit and 64-bit) Windows XP Professional with SP 3 Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 Server R2 and SP1(Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; without Hyper-V; 32-bit and 64-bit) Windows 7 SP1 JRE Version _24 Apache Server Version PostgreSQL Version VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 NM Server on Windows 2008 Server R2 (Standard and Enterprise) & Windows 7 Professional 64-bit is only supported on Intel 64-bit processors. AMD 64-bit processors are not supported for these Operating Systems. Table 35: Network Management 6.0 SP 6- Client 24 P&A Release Notes 6.0 SP8 December 2012

29 Integrated Management Software Line-up for 6.0 SP 6 Table 36: Operating Systems Third-party Applications & Packages Virtual Machine Support Additional Notes Windows 7 Professional (32-bit and 64-bit) Windows XP Professional with SP 3 Windows Vista SP2(32-Bit and 64-Bit) Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 Server R2 with SP1(Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; without Hyper-V; 32-bit and 64-bit) Windows 7 SP1 JRE Version _24 Browsers - IE6, IE7, IE8 Firefox 3.5, Firefox 3.6 VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 Only IE8 is supported on Windows 7 Professional. It is recommende d that the JRE minor version be equal to or greater than the servers minor version P&A Release Notes 6.0 SP8 December

30 Performance and Administration 6.0 SP 6 Table 37: Performance and Administration 6.0 SP6- Performance & Administration Server Table 38: Operating Systems Third-party Applications & Packages Virtual Machine Support Additional Notes RHEL Linux 5.5 and earlier versions (x86 and x64) JRE Version _23 Apache Version Tomcat Version PostgreSQL Version VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX Table 39: Performance and Administration 6.0 SP6- Performance & Administration Client Table 40: Operating Systems Third-party Applications & Packages Virtual Machine Support Additional Notes Windows 7 Professional (32-bit and 64-bit) Windows XP Professional with SP 3 Windows Vista (32-bit and 64-bit) Windows 2003 Server with SP2 (Standard and Enterprise) Windows 2008 Server R2 with SP1 (Standard and Enterprise) Windows 2008 Server with SP2 (Business and Enterprise; without Hyper-V; 32-bit and 64-bit) JRE Version _23 Browsers - IE6, IE7, IE8, FF 3.5, FF 3.6 VMWare ESX 3.0 VMWare ESX 3.5 VMWare ESX 4.0 VMWare ESX 4.1 Only IE8 is supported on Windows 7 Professional It is recommended that the JRE minor version be equal to or greater than the servers minor version Please read the Appendix for using JRE and above 26 P&A Release Notes 6.0 SP8 December 2012

31 Integrated Management Software Line-up for 6.0 SP 6 Enhancements delivered in Performance and Administration 6.0 SP 5 The work items are for reference by Avaya engineers only, and do not in anyway impact the end users of this document. Table 41: Enhancements delivered in Integrated Management Database 6.0 SP 5 Table 42: 1. wi A new capability named ViewReports has been added which you can use for FPMRole creation. 2.wi Integrated Management Database now supports Voice Portal. Table 43: Enhancements delivered in Fault and Performance Manager 6.0 SP 5 Table 44: 1. wi SP 5 supports Voice Portal traps. 2. wi The new default ReadOnly mode in Fault and Performance Manager has Report Manager disabled. Table 45: Enhancements delivered in Multisite Administration 6.0 SP 5 Table 46: 1. wi Based on the SA8993 green feature, SP 5 supports the expanded range (1-250) of Tenant Partition. P&A Release Notes 6.0 SP8 December

32 Fixes delivered in Performance and Administration 6.0 SP 5 The work items are for reference by Avaya engineers only, and do not in anyway impact the end users of this document. Table 47: Fixes delivered in Integrated Management Database 6.0 SP 5 Table 48: Integrated Management Database Work item Problem Solution 1. wi The IMautoremote script did not work correctly. 2. wi The BaseDN was not getting populated properly in Integrated Database Management. The issue has been fixed in this The issue has been fixed in this Table 49: Fixes delivered in Multisite Administration 6.0 SP 5 Table 50: Multisite Administration Work item Problem Solution 1. wi With a partition restriction defined in it's group, the system was unable to clear off-pbx-sta entry for the Multisite Administration non super user. 2. wi Even after you closed the Multisite Administration application, the Multisite Administration browser session remained open. The issue has been fixed in this The issue has been fixed in this Table 51: Fixes delivered in Fault and Performance Manager 6.0 SP 5 Table 52: Fault and Performance Manager Work item Problem Solution 28 P&A Release Notes 6.0 SP8 December 2012

33 Fixes delivered in Performance and Administration 6.0 SP 5 Table 52: 1. wi While processing the best match, the system did not process Traps when you defined multiple filters. 2. wi Fault and Performance Manager application did not receive Modular Messaging traps. 3. wi The system was unable to forward Modular Messaging traps. 4. wi In the previous version, the system did not launch Site Administration and Multisite Administration with the selected voice system. 5. wi The Service shutdown command in the PM Monitor of Fault and Performance Manager UI made the server unreachable. 6. wi Site Administration did not launch from the DCS trunk and the IP trunk tabs. 7. wi The system displayed an inappropriate message when the system tried to open more than 1000 exceptions. 8. wi The change password option in Fault and Performance manager did not work from the Linux server UI. 9. wi The mfpmconfig script did not detect the Primary server location if Integrated Management Database was not co-resident with the Fault and Performance server. The output showed Integrated Management Database server as the primary Fault and Performance server. 10. wi Fault and Performance Manager was unable to create reports in the ASCII format. 11. wi NMSIService displayed an IllegalArgument exception error. 12. wi The IP DSP Resources GW report on a 64 bit Linux system did not populate GW type and GW No fields. The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The Service shutdown button has been removed from the PM Monitor UI. The issue has been fixed in this The system now displays a modified message or instruction while it opens more 1000 exceptions. The button has been removed from the Linux server UI. The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this P&A Release Notes 6.0 SP8 December

34 Table 52: 13. wi From Alarms/Errors filters, you could not add the MO location entry for only the Trunk group without specifying the trunk member. 14. wi In the previous releases, MO Location Column appeared wrongly in the Restart Alarm Filter row. 15. wi In the previous release, the port configuration and the status view did not launch for the mediiagateway ports. 16. wi The system detects some Avaya Aura Communication Manager traps incorrectly. 17. wi The system wrongly displayed an applet tampering message when you launched the mfpm applet. 18. wi RMI SSL did not support High strength ciphers. The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this 30 P&A Release Notes 6.0 SP8 December 2012

35 Known issues in Performance and Administration 6.0 SP 5 Known issues in Performance and Administration 6.0 SP 5 The work items are for reference by Avaya engineers only, and do not in anyway impact the end users of this document. Table 53: Known issues in Multisite Administration Release 6.0 SP 5 Table 54: Work item Known issue 1. wi Avaya Aura Communication Manager Messaging and Modular Messaging with SSL do not work on 64-bit operating system. Table 55: Known issues in Fault and Performance Manager 6.0 SP 5 Table 56: Work item Known issue Workarounds 1. wi The system does not save the Filters properly for 5.2 voice systems. For 5.2 voice systems, when number of lines in mvmgt.conf increases beyond 250, then whenever you try to save any new filter, the system does not save the filter. Also, when you modify any filter, the system does not save the modifications. 2. wi Restore defaults does not apply default filters on Avaya Aura Communication Manager. 3. wi When you set a filter on Avaya Aura Communication Manager instead of both (Avaya Aura Communication Manager/Fault and Performance Manager), trap is not generated. Clear the filter using the following commands: snmpset -c private -v 2c i i 1 snmpset -c private -v 2c i i 2 Modify or click modify for any filters and then save the filters. Set the filter on BOTH. P&A Release Notes 6.0 SP8 December

36 Enhancements delivered in Performance and Administration 6.0 SP 4 Table 57: Enhancement delivered in Integrated Management Database 6.0 SP 4 Table 58: 1. Unsupported Platform Types have been removed from the Integrated Management Database user interface. 2. Inactivity timeout functionality has been implemented in Integrated Management Database. Integrated Management Database provides a checkbox in security settings to set the inactivity interval. 3. Due to vulnerability issues, CollStatus and ShowConfig buttons have been removed on the Fault and Performance Manager server status screen. Table 59: Enhancements delivered in Fault and Performance Manager 6.0 SP 4 Table 60: 1. FixCounts script in Fault and Performance Manager has been improved to run REINDEX after VACUUM FULL. 2. When Fault and Performance Manager receives an alarm or a trap, for subsequent actions, best match of the alarm filter on the basis of MO location is provided. 3. Best match of the alarm filter on the basis of Mo Location is provided 5. You can launch Details view for trunk members of H.323 and SIP trunks. 6 For CMM/Adjunts trap received directly (those not received through SAL), columns in the exception list get populated. Table 61: Enhancements delivered in Multi Site Administration 6.0 SP 4 Table 62: 1.. There is support for 4612CL set type. 2. There is now support for inactivity lock out. 32 P&A Release Notes 6.0 SP8 December 2012

37 Enhancements delivered in Performance and Administration 6.0 SP 4 Enhancement in Fault and Performance Manager alarms / errors filter The alarms and error filter of Fault and Performance Manager release 6.0 SP 4 has been enhanced as follows: MO-Location gets disabled if you select a Category and/or MO-Type Filters now have a new Category as None, so that you can filter on location by selecting MO-Location like Media Gateway, Board, Trunk (grp/member), Port, Error Code, Cabinet and Extension. You can populate location in the Location field that you want to filter. a. Example : Category= None, MO-location= Media Gateway, Location=001. b. Example: Category= None -> MO-location= Cabinet, Location=01. Category Filter All allows you to select MO-Types from the drop down list. This list is editable and so, you can key-in any MO that you want to filter. User interface validations similar to Avaya Aura Communication Manager web maintenance GUI are part of the filter administration. For example, for a wrong entry of Media Gateway in the Location field a popup displays as given below. Similar validations (as given in the last point) for Mo-Location fields Board, Trunk (grp/member), Port, Error Code, Cabinet, and Extension have been incorporated. NIC bonding Network Interface Card (NIC) bonding enables two Ethernet interfaces on the IM PA Server to act as one, providing redundancy. The NIC bonding driver is configured to use active-backup mode in which two Ethernet interfaces can be added as slaves to the NIC bonding driver interface. Only one slave in the bond is active and the other slave becomes active if, and only if, the active slave fails. For more information on this, refer to the P & A Install and Upgrade guide 6.0 SP4 on the Support site. The System Adminstrator or the Network Admistrator of the Integrated Management server must take the responsibilty to configure NIC bonding according to the operating system. P&A Release Notes 6.0 SP8 December

38 Fixes delivered in Performance and Administration 6.0 SP 4 Table 63: Fixes in Performance and Administration 6.0 SP 4 offer Table 64: Performance and Administration Problem From Performance & Administration installer, Fault and Performance Manager launch failed for Firefox (and in some IE cases) for some JRE versions. Solution. The issue has been fixed in this Integrated Management Database Problems Base DN was not polulated correctly for CMM/IA Audix elements. IMDDeleteElm script failed to delete element associated with LDAP group. Solutions The issue has been fixed in this The issue has been fixed in this Fault & Performance Mananger Problem PING_FAILED alarrms were not being generated. PSQL exception error was thrown up during the collection. Alarm collection was failing intermittently on Fault and Performance Manager. When you ran on-demand performance collection, Fault and Performance Manager user interface stopped functioning and recovered only after restarting FPM services. Also, it was not possible to see the on-demand performance report. Fault and Performance Manager was not working successfully after changing FQDN/IP address of the server. With the new (JRE 1.6.0_23) in 6.0 SP3, most of the times login screen text was blank. Solution The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this release 34 P&A Release Notes 6.0 SP8 December 2012

39 Fixes delivered in Performance and Administration 6.0 SP 4 Table 64: Filter settings were not changed from default to Custom or vice versa after you restored snapshot. The system threw up ClassCast exception error during IP Server Interface report collection. Fault and Performance Manager did not process Avaya Aura Messaging traps forwarded by SAL. Trap severity got changed for traps recevied through SAL. Restoring 6.0 SP2 filter snapshot on the 6.0 SP3 system was not working properly. LDAPS authentication was failing in Fault and Performance Manager. If you changed to Integrated Management Database elements, they were not reflected in the Fault and Performance Manager screen. The filter entries of multiple Fault and Performance Manager servers were not populated correctly on a single Avaya Aura Communication Manager serves. The system was not saving the Fault and Performance Manager filters properly. They were disappearing randomnly. In Fault and Performance Manager, the system was not purging the ping data at all. After you restored the snapshot, the particular Avaya Aura Communication Manager had custom filters set as earlier, but the GUI did not refresh after restore. Fault and Performance Manager alarm/filter table was not blocking addition of invalid entries. LaunchApps menu on the Admin UI has been updated. The GUI stopped functioning for Traps for Adjunct. The issue has been fixed in this release The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this P&A Release Notes 6.0 SP8 December

40 Table 64: When Fault and Performance Manager received trap on a single media gateway it cleared configuration on all media gateways and re-collected configuration only for that single media gateway. Trap service of Fault and Performance Manager was restarting automatically when UI was launched. There was database access failure when you were saving Trunk Group List for a Voice System. The issue has been fixed in this The issue has been fixed in this The issue has been fixed in this Multi Site Administration (MSA) Problem You failed to add an off-pbx-telephone station-mapping entry in the Multi Site Administration application. Next Page button was grey on Agent_loginID form. So you could not list the additional agent-loginids. Solution The issue has been fixed in this The issue has been fixed in this Known issues in Performance and Administration 6.0 SP 4 Table 65: Known issues in Fault & Performance Manager 6.0 SP 4 Table 66: 1. Fault and Performance Manager java related logs are only logged on java console they are not seen in msglog_* 2. When you use Fault and Performance Manager for a long time, you see java exceptions like ClassCast, or NullPointer exceptions in the Java console. These exceptions go away when you reopen user interface. Along with the exceptions you may see issues in opening sub windows of FPM. 36 P&A Release Notes 6.0 SP8 December 2012

41 User guidelines for JRE 1.6.0_19 and later versions User guidelines for JRE 1.6.0_19 and later versions Overview As in the Java SE 6 Update 19 release or later, when a program contains both signed and unsigned components, a warning dialog box appears. The application contains both signed and unsigned codes by design. You must allow the applet or the application to run. Click No when the system displays the warning, Java has discovered application components that could indicate a security concern. The follwing topics and sub-topics explain this. Mixing signed and unsigned code - ensuring Application security Signed Java Web Start application overview Signed Java Web Start applications and applets that contain signed and unsigned components could be potentially unsafe unless you intend to use the mixed code. The following figure is an example of the warning dialog box that you may see, when you are using Java SE 6 Update 19 release (or later), and the program contains both signed and unsigned components. Click More Information and the new dialog box (figure below) appears: P&A Release Notes 6.0 SP8 December

42 Click No to enable the application to continue to run with some added protections. If you click Yes, the application does not start. By default, the system issues a warning, but you have various protection options available to handle this situation. For more information, see the topic Mixed code protection options for users. Mixed code protection options for users There are options available to manage mixed code programs. The relevant one is explained here for your benefit. Java Control Panel: You can manage mixed code programs through the Java Control Panel. The following screen shot shows the four levels of control available. See the Mixed code heading towards the bottom of the panel. 38 P&A Release Notes 6.0 SP8 December 2012

43 User guidelines for JRE 1.6.0_19 and later versions Accessing the Java Control Panel varies for each platform and for different releases of a platform. On Microsoft Windows Vista and XP, to access the panel, go to Start menu > Control Panel > Java Control Panel. Validate usage. The first three options enable software protection, but exhibit different features. Enable - show warning if needed This is the default setting. When you encounter a potential security risk, a warning dialog box appears. If you click Yes to block potentially unsafe components from running, the program does not start. If you click No, the application or applet continues execution with some added protections. Packages or resources that you later encounter with the same names but with different trust levels, that is, sign versus unsigned, are not loaded. P&A Release Notes 6.0 SP8 December