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

Integrated Management 6.0 Performance and Administration Release Notes-Service Pack 2 Service Pack 2 Issue 1 November 2010

2010 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: http://www.avaya.com/support. 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, http://support.avaya.com/licenseinfo/ 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 e-mail 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 e-mail 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: http://support.avaya.com/copyright. 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Website: http://www.support.avaya.com/. 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: http://www.avaya.com/support. 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 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Website: http://www.avaya.com/support.

Contents Problems fixed in Integrated Management Performance and Administration 6.0 SP2 1 Integrated Management Performance and Administration 6.0 SP2........ 1 Product Support Notices............................... 2 Requirements delivered to Integrated Management Performance and Administration 6.0 SP22 Fixes in Integrated Management - Fault and Performance Manager 6.0 SP2... 3 Fixes in Integrated Management - Multi Site Administration 6.0 SP 2....... 4 Enhancements in Integrated Management Performance and Administration 6.0 SP1 6 Fixes in Integrated Management Performance and Administration 6.0 SP1.... 7 Known issues in Performance and Administration 6.0 SP1............ 9 Performance and Administration 6.0 SP1 supported packages and OS...... 9 Integrated Management Performance and Administration Release 6.0 Service Pack 2 November 2010 1

Contents 2 Integrated Management Performance and Administration Release 6.0 Service Pack 2 November 2010

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 Integrated Management Performance and Administration 6.0 SP2 Integrated Management service packs are cumulative. Service Pack 2 (SP2) includes modifications and enhancements specific to this service pack and from earlier service packs. Modifications are grouped by applications as listed in the tables in this document. This Service Pack includes: Table 1: Requirements delivered to Fault and Performance Manager 6.0 SP2 on page 2. Table 2: Requirements delivered to Multi Site Administration 6.0 SP2 on page 2. Table 3: Requirements delivered to P & A 6.0 SP2 on page 3. Table 4: Changes delivered to Fault and Performance Manager 6.0 SP2 on page 3. Table 5: Changes delivered to Multi Site Administration 6.0 SP 2 on page 4. Table 6: Enhancements delivered to Performance and Administration Release 6.0 SP1 on page 6. Table 7: Enhancement to Fault and Performance Manager Release 6.0 SP1 on page 6. Table 8: Changes delivered to Fault and Performance Manager Release 6.0 SP1 on page 7. Table 9: Table 4: Changes delivered to Multi Site Administration Release 6.0 SP1 on page 8. Table 10: Changes delivered to PA Installer Release 6.0 SP1 on page 9. Table 11: Known issue in Performance and Administration for Multi Site Administration Release 6.0 SP1 on page 9. Table 12: Performance and Administration supported OS on page 9. Table 13: Performance and Administration supported third party packages. on page 9. 1 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 Product Support Notices 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 http://support.avaya.com. 2. Click Products. The web page displays a popup 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 Title 4. Click the PSN title link to open the PSN. Requirements delivered to Integrated Management Performance and Administration 6.0 SP2 Table 1: Requirements delivered to Fault and Performance Manager 6.0 SP2 1. Support for HP DL360g7 Server. 2. Support for Standalone Avaya Aura Messaging 6.1. 3. Migration from ireasoning SNMP stack to open source SNMP4j stack. 4. Ajunct alarming by SAL and SSG.. 5. Support for CM 6.0.1 running as part of new templates. Table 2: Requirements delivered to Multi Site Administration 6.0 SP2 1. Support for CM 6.0.1 running as Part of New Templates. 2. Support for Avaya Aura Messaging 6.1 running as part of new templates. 3. Support for HP DL360g7 server. 4. Support for IPDECT UnGreen : Supports new "Xmobile type" "IPDECT" for "XMOBILE" Set Type 2 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Fixes in Integrated Management - Fault and Performance Manager 6.0 SP2 Table 3: Requirements delivered to P & A 6.0 SP2 1. Support for new element DL360g7 Fixes in Integrated Management - Fault and Performance Manager 6.0 SP2 Table 4: Changes delivered to Fault and Performance Manager 6.0 SP2 Problems Solutions There was no response from FPM login window when you disabled non-secure LDAP access through firewall. Login was successful even if you used an invalid certificate with SSL on openldap. Number column of Medigateway screen was sorted based on a string and not on a numeric number. There were some issues with alarms / error filters. The Resolve traps existed on FPM help pages. ProductID was not detected in the incoming trap The system send an email after 15 minutes of receiving a trap. There were issues with the Change Status option on the systems view. 1. Change Status did not display latest connection status mode 2. After changing the connection status mode, the FPM UI always displayed as busy (by way of using busy mouse) even though it was not. The new mode was also not visible. This is fixed in this release. A fix is made so that with SSL on openldap, FPM login fails for an invalid certificate. A fix ensures that number column of Mediagateway screen is sorted appropriately. The Category information is set correctly to the g3filtercategory MIB item. MO location is now set to the g3filtertable MO-Location. In custom filter Server alarms, after you select a category option "All" is available in Alarm sources. This is fixed in this release. This is fixed in this release. A fix ensures that the system sends an email immediately after receiving a trap. This is fixed in this release. 3 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 In the previous release, the trap PDUs generated by FPM after meeting threshold criteria during Performance collections had "g3alarmsmaintname" and "g3alarmsalarmtype" empty. MovePN functionality was broken. The trap PDUs generated by FPM after meeting threshold criteria during Performance collections had "g3alarmsmaintname" and "g3alarmsalarmtype" OIDs are properly populated. This is fixed in this release. You now upgrade the existing user profile for successful execution of MovePN. Note: Note: Read the note below this table to learn about MovePN. Note: Note: For successful execution of the MovePN functionality, you must be able to execute the service command. Perform the steps given below to successfully create a "cm-user". Steps to create a "cm-user" Step 1: Execute change system-param cust, and on Page 5 set Processor and System MSP? to y. Step 2: Create a new user-profile by executing duplicate user-profile 18, and on Page 17 set ipserver-interface D to wm. Step 3: Save the user profile settings. Add or edit the user profile to the elements administered in the Integrated Management Database. Click Configuration collection on the two systems from where you moved the port network. Fixes in Integrated Management - Multi Site Administration 6.0 SP 2 Table 5: Changes delivered to Multi Site Administration 6.0 SP 2 Problems Solutions There was no support for IPDECT UnGreen. There is support for IPDECT UnGreen. 4 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Fixes in Integrated Management - Multi Site Administration 6.0 SP 2 Running Remove Station task in background stopped responding and generated large log files. After using Find button to populate subscriber data an extra space character was added in the Name field and dash character was not removed from the extension. Sunday end time did not display correctly in the Service-Hours form. There was no support of long extension (more than 10 digits) for Voice Mail applications. After enabling Site Data Expansion, MSA application did not retrieve all building information from Communication manager. There was no support for XOIP Endpoint type field on the station form. The operation of Scheduled tasks was not displayed in the local.log Column name did not display in the scheduled report output. When you created a job like add station, you had an option to add a Note. before completing the job. The Note displayed in the Station / System Manager Log Viewer, but not in the local.log. There was no support for CM 6.0.1 running as part of new templates. MSA had no option to use enhanced LDAP API. No password and PIN aging and lockout rules were enforced. There was no support of DL360g7 for MSA. Running Remove Station task functions properly and no more log files are generated. After using Find button to populate subscriber data an extra space character is not added in the Name field and dash character is removed from the extension. From this release, there is support for long extension (more than 10 digits) for Voice Mail applications. There is support for XOIP Endpoint type field on the station form. A fix ensures that when you create a job like add station, and you add a Note before completing the job, the Note displays not only in the Station / System Manager Log Viewer, but also in the local.log. MSA uses the updated API provided by IMD for performing the LDAP Authentication/ Authorization check, such that MSA also takes advantage of the flexibility being provided in AIM 6.1. This has been fiixed in this release. 5 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 Enhancements in Integrated Management Performance and Administration 6.0 SP1. Table 6: Enhancements delivered to Performance and Administration Release 6.0 SP1 Enhancement The LDAP authentication is enhanced to provide support for using LDAP administrator user to search another user's attribute. Table 7: Enhancement to Fault and Performance Manager Release 6.0 SP1 Enhancements Port Network numbers are now part of the Port Networks report e-mail content. 6 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Fixes in Integrated Management Performance and Administration 6.0 SP1 Fixes in Integrated Management Performance and Administration 6.0 SP1 Table 8: Changes delivered to Fault and Performance Manager Release 6.0 SP1 Problem LDAPS authentication was failing. In the Capacity Report for buildings, there was a misalignment of the columns causing inconsistencies. The user saved some reports in the FPM, but later could not delete them. The system acknowledged the delete request, but did not delete the reports. There was a failure to generate IP DSP Summary report. An exception error was thrown up when user attempted to do so. A null pointer exception error was thrown up when Board collection attempt is made. In the previous release, reports with two or more views were not saved correctly in a file. E-mail notification is not resent when a Broken-pipe exception occurs in the First attempt. Restart Filters did not support both Interchange-Initiated and Craft-Initiated flags set to y or n. SNMP operation (fetching MOs, filter setting) failed with Authorization and no Privacy credentials in case of SNMPv3. There was no support of equipment ID information in the Performance Alarm trap. The result was that when the trap was generated by the FPM application, it does not contain the Source Region number. Solution A fix has been made so that LDAPS integration with Active Directory is successful. Null pointer exception is not thrown up when user attempts Board collection. Current release allows reports with two or more views to be saved correctly in a file. In the current release, SNMP operation (fetching MOs, filter setting) does not fail with Authorization and no Privacy credentials in case of SNMPv3. Current release has support of equipment ID information in the Performance Alarm trap. So, when trap is generated by the FPM application, it contains the Source Region number. 7 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 Table 8: Changes delivered to Fault and Performance Manager Release 6.0 SP1 Problem Logs were not getting cleared when user attempted to clear them using the clear log button. This was happening on the second attempt. Column headings were not shown for Ancc on-demand hour count report. The CPU usage used to spike up to 99% for "Fixcounts -[counts exclean]" options in the previous release causing the application to hang. Solution Current release allows user to clear logs even while attempting on the second time. Column headings display clearly in the Ancc on-demand hour count report. in the current release. A fix has been made to reduce the high CPU load while FixCounts tool runs. Table 9: Table 4: Changes delivered to Multi Site Administration Release 6.0 SP1 Problem When user opened an extension on off-px-telephone window, an unexpected window opened in MSA. The available trunk range in the trunk selection option of off-pbx-telephone form is not correct. Using Add Station option on Stations from Quick Command form appeared after selecting the extension number and pressing OK button. The user exited from the application if the user closed the Quick Command window. There was no support for IP Phone Group ID field on the station form. There was no support for Avaya Aura Messaging 6.1 running as Part of New Templates. Solution A fix stops an unexpected window from opening in MSA when user opens an off-px-telephone window. Current released has fixed the trunk range in the trunk selection option on off-pbx-telephone form. Current release has solved this problem and user can add a Station on the Stations form. Current release supports IP Phone Group ID field on the station form. Current release supports Avaya Aura Messaging 6.1 running as Part of New Templates. Table 10: Changes delivered to PA Installer Release 6.0 SP1 Problem In the previous release, several FPM Java ports support a weak SSL cipher prone to unauthorized decrypting. Solution A fix is made to the JAVA SSL configuration to remove support of algorithms causing weak SSL ciphers risks. 8 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Known issues in Performance and Administration 6.0 SP1 Known issues in Performance and Administration 6.0 SP1 Table 11: Known issue in Performance and Administration for Multi Site Administration Release 6.0 SP1 Issue On a 64 bit server, Active Directory LDAPS authentication fails for MultiSite Administration. Performance and Administration 6.0 SP1 supported packages and OS Performance and Adminstration 6.0 SP1 now supports the following packages and operating systems. Table 12: Performance and Administration supported OS Operating System Supported version name Linux Linux 5.5 and earlier versions (x86 and x64) Windows Internet Explorer 8 running on Microsoft Windows 7 professional (x86 and x64) machine as client to access Performance and Administartion applications. Table 13: Performance and Administration supported third party packages. Package name Supported version for Linux PostgreSQL (Includes all postgresql packages) 8.1.11 HTTP 2.2.3 openssl 0.9.8b-10 openldap 2.3.43-3 openssl x 2.1.22 tomcat 4-4.1.24 9 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2

Problems fixed in Integrated Management Performance and Administration 6.0 SP2 10 Release Notes Integrated Management Performance and Administration Release 6.0 Service Pack 2