Avaya Aura System Manager 6.3 Service Pack 1 Release Notes

Transcription

1 Avaya Aura System Manager 6.3 Service Pack 1 Release Notes Issue: 1.0 February

2 2013 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not 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. Customer and/or 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 the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. 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 through the Avaya Support Web site: License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. 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 Products, originally sold by Avaya and ultimately utilized by End User. License type(s) 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 Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. 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 identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: 2

3 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 Web site: Trademarks Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: 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 Support Web site: 3

4 Contents Introduction... 5 Product Support Notices... 5 Problems fixed in Avaya Aura System Manager 6.3 Service Pack Operational Assistance... 8 System Manager Software System Manager Download and Installation Points to remember before a fresh installation or an upgrade Installing the Service Pack Supported upgrades Technical support Appendix A: Compatibility matrix for the System Manager 6.3 and System Platform software versions

5 Introduction This Release Notes gives you information about installation downloads and the supported documentation of Avaya Aura System Manager 6.3 Service Pack 1. This Release Notes also contains information about features, known issues, and the possible workarounds in this Release. You must install System Manager 6.3 Service Pack 1 on System Manager 6.3 GA. Product Support Notices Some product changes are documented as Product Support Notices (PSN). The PSN number defines the related document. To read a PSN description online: 1. Go to the Avaya Support website at 2. On the main menu, click Downloads and Documents. 3. In the Enter Your Product Here field, enter System Manager or select Avaya Aura System Manager from the list. 4. In the Choose Release field, click 6.3.x. 5. Click Documents. 6. Check Product Support Notices. 7. Click Enter. 8. To open a specific PSN, click the PSN title link. 5

6 Problems fixed in Avaya Aura System Manager 6.3 Service Pack 1 The following are the fixes delivered in Avaya Aura System Manager 6.3 Service Pack 1 software Release. Table 1: Fixes delivered to System Manager 6.3 Service Pack 1 Keyword Description ID Reference Alarming Alarming UI does not show the Alarms due to authorization issue. wi Service pack installation should fail with appropriate error message if iptables wi on System Manager is turned off. Installation Fail to execute tshark command. wi Authentication Geographic redundancy Enable port 111 for TCP in firewall configuration. System Manager/Quantum Single Sign On Session capability through command line Interface (CLI) not operational. Issues with e Token user functionalities in System Manager 6.3 Release. User accessing the links (policy link) gives the system error or some of the links are missing due to QuantumElementType permission not getting published properly. GEO Configuration fails if System Manager is having FQDN in uppercase or mixed case. During Recovery, file replication is not working for some sets of files. Enable replication does not work properly. wi wi , wi , wi wi wi Wi wi wi Help Management Update on User Management help information. wi Default access point for Communication Manager should be in read only mode. wi Inventory Management Licensing Role Management Rediscovery not picking up CM Access profile. Collected inventory lists both the edited and original element when the IP is edited on 'Manage Element' page. System Manager returns bad response to Communication Manager (CM) license request. Refer the Operational Assistance section for workaround steps in case of older clients. Custom role(s) created prior to upgrade with dot in the name, is not getting displayed after upgrading to System Manager 6.3 GA release. Refer the Operational Assistance section for one time correction steps. Buttons on top of graphical table are not always enabled correctly. wi wi wi wi wi User Interface After applying System Manager 6.2 service pack 3 on System Manager 6.2 GA, wi links to some applications (Deployment Manager, Patch Manager, SNMP Profiles, and Secure FTP Token) redirect to User Management User time zone shows as blank if users were created with time zone before the wi DST change. Conferencing Multicabinet: Only one Phone numbers record in BSRes2 ResourceDDIPhone wi table is displayed, it should allow multiple. Clicking on Home/Elements/Meeting Exchange/ Services, the HTTP Status 500 wi error appears in System Manager 6.3. Messaging Sync with Modular Messaging fails. Wi Communication Manager System Manager replaces secondary extensions of Modular Messaging Subscribers during sync. Circular coverage path references causing initialization/incremental synchronization to fail. Display Language field in global endpoint change is missing unicode2 4 options Wi wi wi

7 compared to individual endpoint editing. When a user assigned endpoint as template, it also saves the original user, so whenever the template is assigned to an endpoint the user is too set as stationuser. Tenant Number outside acceptable values when bulk exporting users with Communication Manager communication profile. In case of Communication Manager interchange when the active Communication Manager IP is in the "Alternate IP Address" field certain functionality needing Communication Manager interaction does not work. Abbreviated dialing personal list is not updated after committing endpoint changes. Global endpoint change for button assignments for alias templates is not working. System Manager does not seem to support standard Communication Manager feature "Enhanced Call Pickup Alerting" in Endpoint Templates. Delete of Hunt group associated to user and remove endpoint option checked fails user delete. Incremental synchronization is failing if there is delete announcement or release station commands in Communication Manager s list history. Bulk import fails for a user with agent communication profile which has all the data required except template name. Bulk Delete fails for deleted stations from Communication Manager SAT. In Edit User with Agent Communication Profile, Delete Agent on Unassign of Agent from User or Delete User actual value is considered as per previously saved in db value. Browser related issue: Drop down provided on NCM screen is having issue. On Remove options page, while selecting any option inside "Default Settings for All Systems" the option is only applicable to the systems shown in that page at that particular time. wi wi wi wi wi wi wi wi wi wi wi wi wi

8 Operational Assistance Table 4: Known limitations and workarounds in Avaya Aura System Manager 6.3 Service Pack 1 Release Keyword Description ID Reference Workaround Role Management Communication Manager Authentication Geographic redundancy Custom role(s) created prior to upgrade, with dot in the name, is not getting displayed after upgrading to System Manager 6.3 GA release. Roles page is not getting displayed for custom user. Issue in adding new agent if "Password" and "Confirm Password" fields are assigned. If Notify Sync feature is enabled for a CM on a standalone System Manager, after setting up Geographic Redundancy, notification messages would not be sent to Secondary System Manager. System Manager skips "change locations" Element Cut Through screens on SMGR 6.2 when using IE7 and IE8 Authentication scheme is reset to local users after making changes to Authentication servers System Manager does not display the notification on the secondary System Manager dashboard, if the primary System Manager is shutdown after GR is enabled. System Manager does not support rollback for Disaster recovery. Disaster recovery implies the primary site wi Create a new role. 2. Assign/copy permissions from the existing non functional role to this new role from UI 3. Execute script /home/ucmdeploy/quantum/findusersforr ole.sh, this will provide all the users having non functional role assigned to them. You need to pass System Manager UI username and role name as inputs parameters to the script. You will need to pass wildcard in quotes. #sh /home/ucmdeploy/quantum/findusersforrole.sh admin role* 4. Assign the newly created role to all those users. 5. Delete the older non functional role from UI wi No workaround available wi Use Internet Explorer 8.x, 9.x or 10.x. wi Browse to Home / Elements / Inventory / Manage Elements and select CM and click on Edit button. 2. Browse to Attributes Section and make sure that Enable Notifications check box is checked and click on commit button. wi wi wi wi Do not use IE7 or IE8 while running change locations using Element Cut Through. 1. Verify the Authentication scheme after making changes to authentication servers. 2. In case the authentication scheme has changed to local users. Reset it to the older value. Navigate to GR Health page on the secondary System Manager server; check the heartbeat status of Application system health. Ensure that you perform System Platform (SP) backup before performing disaster recovery. If disaster recovery fails, then restore this SP backup. 8

9 Trust management Bulk export Bulk import System ACL Import users Bulk Export restoration on the newly installed primary server when the old primary is not available with the secondary database. After applying a patch, the Geographic Redundancy link on System Manager dashboard is intermittently not accessible. Exceptions are seen in Geo Redundancy page in the following scenarios: 1) Database is down. 2) JBoss is getting restarted. 3) Secondary System Manager is down. 4) Primary System Manager server is down. 5) Some internal error occurred. The console page displays these exceptions in workflows such as enable replication, disable replication, activation, deactivation, and recovery. System Manager 6.3 does not display the auto session time out pop up message for the Certificate Authority page after the session timeout has occurred. The Certificate Authority page is accessible by Home / Services /Security/Authority. In 6.3, bulk export of users operation takes more time than previous release. Enforced ACL rules are not imported into System Manager. Users with circular dependencies cannot be bulk imported. Example of circular dependency: User A has User B in his contact list denoted by A B. Also, User B has User A in his contact list denoted by B A User Bulk export cannot be run through admin user. wi wi wi wi wi wi wi Restart JBoss. Wait for the process to complete before proceeding. After the Postgres or JBoss starts, the exceptions disappear. Log on to System Manager again and work on the new session. Create Enforced ACL rules using System Manager Web console. Workaround available. Contact Avaya Technical Support. Run the export tool using root user through SSH. 9

10 Directory synchronization User Management Scheduler Backup and restore Licensing When the user runs any directory synchronization operation and then navigates to Manage Users page, an error window keeps popping up when the user tries to refresh the Manage Users page. On the Directory Synchronization page (Home/Users/Directory Synchronization/Sync Users/ New User Synchronization Datasource), when the user tries to edit the added data sources, JBoss error or some internal error has occurred in the service error is thrown intermittently. The authorized user with custom role is unable to see the Show Deleted Users console page and hence cannot permanently delete the user or restore the deleted user. If you duplicate user (Home /Users / User Management / Manage Users / Duplicate) who has the group membership value configured, then the duplicated user does not have group membership data. Job state of the disabled job gets changed to enable after upgrade. Select ALL is not required on the backup and restore Web page as System Manager supports restoring one backup at a time. System Manager does not function after the restore with backup taken on System Manager with a different IP or FQDN. System Manager returns bad response to Communication Manager license request. wi wi wi wi wi wi wi wi Click Manage users from the navigation panel instead of refreshing. Click Sync Users again. The Show Deleted Users console page is displayed when logged in as user name as admin. Add group memberships manually after saving the user details. Disable the job from the Scheduler user interface after the upgrade. Do not select ALL. Restore one backup at a time. This issue is observed intermittently. Hence, restore with the same backup file again that was tried before the System Manager become nonfunctional. If this issue observed with older clients then follow below workaround steps(this workaround disables persistent connections facility): 1. Stop JBoss using the command # service jboss stop 2. Open 10

11 Role Management CS1000 System Manager 6.3 Web Console does not display proper error message while performing simultaneous role modifications on two different session windows. CS1000 and Administrators page opens a new window instead of new tab. Cannot Launch Element Manager for CS1000 from System Manager using Firefox browser. Cannot update CS1000 endpoint user from Secondary System Manager active when the primary System Manager server is down. The specified DN does not get created through CS1000 Communication Profile. UPM Generic Account Manager link is broken. Add CS1000 Endpoint Profile for the user that failed on the secondary System Manager server when the primary System Manager server is down. The activated secondary System Manager server cannot launch CS1000 member element manager when the primary System Manager server is not reachable from the secondary System Manager Server. Online help content does not have DTLS configuration for CS1000 elements. wi wi wi wi wi wi wi wi wi $JBOSS_HOME/server/avmgmt/deploy/j bossweb.sar/server.xml 3. Go to the connector tag of port Add the following parameter to this tag maxkeepaliverequests="1" 5. Save the change. 6. Start JBoss by using the command # service jboss start Note: This port (52233) should be used for further communication with licensing manager in System Manager. Use Internet Explorer 8.x, 9.x or 10.x. To configure DTLS for CS1000, perform following steps: 1. Go to Home/Elements/Inventory/Manage Elements. 2. Select the CS1000 element. 11

12 Inventory Management Deleted node in CS1000 element manager does not synchronize to CS1000 system in System Manager deployment page. Home/Users/Administrators/E lements page. Failed to add Group in Element tree on Home/Users/Administrators/E lements page. Even after giving 'View' permissions to a Role, the user with that role can create 'new' configurations Access point is not getting added when passing appsystem with type Communication Manager (CM) to Element service for addition. Problems 1. System Manager does not support geographic redundancy (GR) for Communication Managers (CMs) discovered through Inventory application. 2. System Manager does not support GR for Communication Managers (CMs) added through bulk import. The administrator cannot wi wi wi Click More Actions/Configure Identity Certificates. 4. Select the Dtls and click Replace. 5. Select option Replace this Certificate with Internal CA Signed Certificate and provide common name, keysize and algorithm. 6. Click Commit. If an Administrator is having trouble deleting a CS1000 node from the Deployment Page through Element Manager, perform the following workaround: 1) Access the Element tree view and delete Node information for the CS100 group. 2) Deployment Manager Page will automatically be update (deleted CS1000 node) 3) Then Administrator can undeploy the member server. If an Administrator is having trouble adding a group in the Element page on Home/Users/Administrators/Elements page perform the following workaround: Option1: Use Firefox 8.x, 9.x or 10.x. Option2: Use Internet Explorer 8 in Compatibility Mode. Option3: You can create groups from the Home/Users/Groups & Roles/Groups page Also, can assign add roles or assign roles to the group using Home/Users/Groups & Roles/Roles page wi Browse to Home / Elements / Inventory / Manage Elements and select Communication Manager (CM) and click on Edit button 2. Browse to Access Point Section and provide the details as shown below Name="CMGeoWSURL" Access Point Type="GRCommunication" Protocol="https" Host="localhost" Port="443" Path="/iptcmgeo/ws/geoservice" order="0" 12

13 Communication Manager Geographic Redundancy perform any Geographic Redundancy related operations on such Communication Managers (CMs). Manage / Unmanage operations while an element is in unreachable state are not allowed. wi

14 System Manager Software System Manager Download and Installation # Action Notes 1. Download the System Platform Patch rpm from the Avaya PLDS Web site. 2 Download System Manager 6.3 Service Pack 1 System_Manager_06_03_ServicePack1_r1212.bin file from the Avaya PLDS Web site. Verify that the md5sum for the downloaded rpm matches the md5sum on the Avaya PLDS Web site. PLDS download ID: SMGR63SP101 Md5Sum: 06d67a3680c771c928c1c03b5de2f6f3 3. Install System Manager 6.3 Service Pack 1. You must install System Manager 6.3 Service Pack 1 on System Manager 6.3 Release. For more information, see Installing the Service Pack section for the steps to install System Manager 6.3 Service Pack 1. Points to remember before a fresh installation or an upgrade 1. Install System Manager 6.3 Service Pack 1 on System Manager 6.3 Release if deployment is based on System Platform environment. Note: System Manager Service pack 1 release not supported for VMWare deployment. 2. Backup and Restore through System Platform. The backup data obtained from System Platform must be restored on the same version of System Platform. 3. Backup and Restore through System Manger. The backup data obtained from System Manager must be restored on the same version of System Manager. 4. Upgrade the System Platform to patch before upgrading to System Manager 6.3 Service Pack 1 Release. 5. When System Manager Restore operation is in progress, do not perform activities such as rebooting the system, restarting the server, or the database. System Manager might not start and might go into irreparable state. 6. If iptables service is turned off on the System Manager machine, then service pack installation will not proceed, also admin should not override/change existing iptables configurations (if it has been stopped, to add new configurations). 7. If service pack needs to be applied on GEO servers, disable Geo Replication from Primary server. 8. Apply this service pack on both System Manager servers which are used for Geo Configuration. 9. Upgrade Session Manager and Communication Manager after the System Manager upgrade. Upgrade or install System Manager before you upgrade or install any of the elements like Session Manager and Communication Manager. The version of the elements at any point in time must always be compatible with the version of System Manager. 14

15 Installing the Service Pack Before you begin: Install System Manager 6.3 Service Pack 1 on System Manager 6.3 Release if deployment is based on System Platform environment. Note: System Manager Service pack 1 release not supported for VMWare deployment. Make sure that the existing System Manager is fully installed and is functional. To check the application state, log on to System Manager Web Console with admin credentials. Before you install System Manager 6.3 Service Pack 1, take a backup of the system and store the backup on an external device. If service pack needs to be applied on GEO servers, disable Geo Replication from Primary server. Apply this service pack on both System Manager servers which are used for Geo Configuration. To install System Manager 6.3 Service Pack 1 Release, perform the following actions: Installing the service pack through System Platform Web Console Installing the service pack through System Platform Web Console is the preferred method of installation. 1. Log on to System Platform Web Console with admin credentials. 2. Download the service pack: a. Click Server Management > Patch Management. b. Click Download/Upload. c. On the Search Local and Remote Patch page, select the location to search for the service pack from the following list: Avaya Downloads (PLDS) HTTP SP Server SP CD/DVD SP USB Disk Local File System d. If you select HTTP or SP Server, provide the URL to the service pack. e. In case of HTTP, click Configure Proxy to specify a proxy server if required. f. If you select Local File System, click Add to locate the service pack file on your computer and then upload. g. Use Search to search the required service pack. h. Choose the service pack, and click Select. 3. Install the service pack by performing the following steps: a. Select Server Management > Patch Management. b. Click on Manage. 15

16 c. On the Patch List page, the status of the patch ID System_Manager_R6.3_ServicePack1_1212 must be Not Installed. d. Click on a patch ID System_Manager_R6.3_ ServicePack1_1212 to see the details. e. On the Patch Detail page, click Install. f. Wait for the patch installation to complete. 4. Verify the service pack installation using one of the following ways: From System Platform Web Console: a. Log on to System Platform Web Console with admin credentials b. Click Server Management > Patch Management. c. Click Manage. d. On the Patch List page, verify that the status of the patch ID, System_Manager_R6.3_ServicePack1_1212, is Pending. If the status is: Pending The service pack is applied and must be committed or rolled back. Installed The service pack is in the installed state. Not Installed The service pack is not installed. Installation has failed. From System Manager Web Console: a. Log on to the System Manager Console. Click About on the top right corner of the Home page. Verify that the system displays the version information in the following format: System Manager Service Pack1 Build No Software Update Revision No: Perform one of the following on System Platform Web Console: a. If the Service Pack installation is successful, commit the service pack installation using the following steps: 1. Click Server Management > Patch Management. 2. Click on Manage. 3. On the Patch List page, the status of the patch ID System_Manager_R6.3_ServicePack1_1212 must be Pending. 4. Click the patch ID System_Manager_R6.3_ServicePack1_1212 to see the details. 5. On the Patch Detail page, click Commit. b. If the Service Pack installation fails, click Rollback. 6. After you upgrade the system to Service Pack 1, reboot the System Manager from System Platform or from System Manager CLI to get the updated kernel running in memory. 16

17 Supported upgrades Note: To upgrade older System Manager Release to System Manager 6.3 Release, see Upgrading to Avaya Aura System Manager to 6.3. To upgrade System Manager 6.3 GA to Service Pack 1 Release, perform the following steps: 1. Upgrade System Manager 6.3 GA to System Manager 6.3 Service Pack 1 Release a) Apply System Platform Patch. b) Install System Manager 6.3 Service Pack 1. 17

18 Technical support Avaya Technical Support provides support for System Manager 6.3 IF you find any problems with System Manager 6.3: Retry the action. Carefully follow the instructions in the printed or online documentation. See the documentation that ships with your hardware for maintenance or hardware related problems. Note the sequence of events that led to the problem and the exact messages that the system displays. For more information, see the troubleshooting section of the Avaya product documentation. If you continue to have problems, contact Avaya Technical Support using one of the following methods: Log on to the Avaya Support website at Call or send a fax message to Avaya Support on one of the telephone numbers in the Support Directory listings on the Avaya Support website. Using Avaya Global Services Escalation Management, you can escalate urgent service issues. For more information, see the list of Escalation Contacts on the Avaya Support website. Before contacting Avaya Support, keep the following information handy: Problem description. Detailed steps to reproduce the problem, if any. The release version in which the issue occurs. Note: To know the release version and build number, log on to System Manager and click About on the dashboard. The status of the System Manager software. If the software is an upgrade, provide the current release number. The log files. a. System Manager JBoss server log file available at $JBOSS_HOME/server/avmgmt/log/server.log. b. Additional System Manager Logs available in the $AVAYA_LOG/mgmt location. Contact support tasks Avaya Support might request for notification files for analysis of your application and the application environment. For information about patches and product updates, see the Avaya Support website at 18

19 Appendix A: Compatibility matrix for the System Manager 6.3 and System Platform software versions System Manager 6.3 System Platform Release Build Number Release Required Patch 6.3 System Manager GA Build No Software Update Revision No: Service Pack 1 System Manager Service Pack1 Build No Software Update Revision No: