AVAYA Avaya Aura System Platform R6.2.2 Release Notes Issue 1.3

Transcription

1 AVAYA Avaya Aura Release Notes Issue 1.3 INTRODUCTION This document introduces the Avaya Aura and describes new features, known issues and the issues resolved in this release. WHAT S NEW IN SYSTEM PLATFORM Backup and Restore progress reporting supports progress reporting for system backup and restore operations. It provides this information automatically on either the Backup tab or the Restore tab in the Management Console (as appropriate for the particular operation). The backup progress window shows: Time-stamped progress messages from System Platform and applications running on local template virtual machines (VMs), including messages filtered directly from backup logs, for example, dataset backup start, pause, end, or failure. A backup process countdown timer. The timer counts down until the operation ends successfully, halts due to errors or manual termination, or the estimated timer value expires. The countdown timer value supplements progress message content, enabling you to make a more informed decision about whether a problem occurred requiring a system recovery. The restore progress window shows: Time-stamped progress messages for restoration of System Platform and application datasets, including messages filtered directly from the restore logs, for example, dataset restore start, pause, end, or failure. A restore process countdown timer. The timer counts down until the operation ends successfully, halts abruptly due to system errors, or the estimated timer value expires. As with the backup countdown timer, the restore timer value supplements progress message content, enabling you to make a more informed decision about whether a problem occurred requiring a system recovery. 1

2 Backup and Restore progress monitoring runs automatically for the following operations: Manual backup Template upgrade backup Manual restore Template upgrade restore Swversion command enhancements enhances the swversion (software version) command used by Avaya Services agents to quickly determine: the server type, the versions of software and patches on the server, supporting more efficient system verification and fault isolation, the software version for every template VM active on the system, the IP address for every template VM active on the system, and the time of the last installation or upgrade of the solution template. Management Console context-sensitive Help enables Management Console users to: display descriptions for all configurable System Platform VM, Server, and User management fields, navigate all field descriptions in a Help browser window independent of the Management Console, navigate all field descriptions from the Help browser Contents tab, navigate all field descriptions in alphabetical order from the Help browser Index tab, and search all field descriptions for specific text references from the Help browser Search tab. SOFTWARE RELEASE VERSIONS Release Date File Name Avaya Aura System Platform R1.0 August 2009 vsp iso Avaya Aura System Platform R1.1 November 2009 vsp iso February 2010 vsp iso Pack R1.1.1 Pack R February 2010 vsp-patch noarch.rpm Pack R April 2010 vsp-patch noarch.rpm Pack R June 2010 vsp-patch noarch.rpm 2

3 Release Date File Name Pack R August 2010 vsp-patch noarch.rpm Pack R November 2010 vsp-patch noarch.rpm Pack R February 2011 vsp-patch noarch.rpm Pack R December 2011 vsp-patch noarch.rpm Avaya Aura System Platform R6.0 June 2010 vsp iso ( ) Avaya Aura System Platform Patch R August 2010 vsp-patch noarch.rpm Avaya Aura System Platform S8300D Pre-Upgrade Patch R February 2011 vsp-patch noarch.rpm Avaya Aura System Platform Pre- Upgrade Patch R May 2011 vsp-patch noarch.rpm August 2010 vsp iso Pack R6.0.1 ( ) Avaya Aura System Platform S8300D Pre-Upgrade Patch R February 2011 vsp-patch noarch.rpm Avaya Aura System Platform Pre- Upgrade Patch R May 2011 vsp-patch noarch.rpm November 2010 vsp iso Pack R6.0.2 ( ) Pack Patch R November 2010 vsp-patch noarch.rpm Pack R February 2011 vsp-patch noarch.rpm Avaya Aura System Platform S8300D Pre-Upgrade Patch R April 2011 vsp-patch noarch.rpm Avaya Aura System Platform Pre- Upgrade Patch R May 2011 vsp-patch noarch.rpm February 2011 vsp iso Pack R6.0.3 ( ) Pack R April 2011 vsp-patch noarch.rpm Pack R August 2011 vsp-patch noarch.rpm Pack R September 2011 vsp-patch noarch.rpm Pack R December 2011 vsp-patch noarch.rpm Pack R April 2012 vsp-patch noarch.rpm 3

4 Release Date File Name Pack R June 2012 vsp-patch noarch.rpm Pack R January 2013 vsp-patch noarch.rpm Avaya Aura System Platform R6.2 March 2012 vsp iso ( ) Pack R April 2012 vsp-patch noarch.rpm Pack R ( ) July 2012 vsp iso Pack R November 2012 vsp-patch noarch.rpm Avaya Aura ( ) December 2012 vsp-patch noarch.rpm Avaya Aura System Platform R February 2013 vsp-patch noarch.rpm Avaya Aura System Platform R vsp-patch noarch.rpm 4

5 Upgrades Upgrades to R6.2.2 are supported from R Please refer to the template documentation for addition upgrade information. The System Platform compatibility matrix (PSN003312u) is maintained at: Resolved Issues and Updates 1. Underscore is now permitted in the trust enrolment password for applications such as Branch Session Manager. 2. User passwords rules displayed on the Management Console now show the minimum change interval and password history requirements. 3. Fixed a refresh issue where a patch installation might still show in progress when in fact it is complete. The previous workaround was to refresh the browser window manually. 4. Resolved an issue following patch installation where the Patch Detail page might not display automatically upon installation completion. 5. Fixed a problem where Domain-0 s logging to the Console Domain would stop if the Console Domain s IP address was changed after installation. 6. Additional checks on space on the file system are performed before proceeding with upgrades and installations. 7. System Platform now clearly indicates when a template installation or upgrade is complete. 8. Resolved an issue where the Management Console would not return to the Template Search page when a user cancelled a template installation in the Template Network Configuration page. 9. Resolved an issue where a solution template patch rollback could leave the template VM unbootable if the Services VM was disabled. 10. A High Availability (HA) issue when the standby hostname was part of the main server hostname (i.e. HAserver and server ) where some of the configuration would be lost when HA was started has been resolved. 11. Issue with dom0 being used has the hostname for Domain-0 causing a problem with starting HA has been fixed. 12. Issue with some hardware errors not getting logged in certain cases has been resolved. 5

6 13. Fixed an issue where the battery learn cycle triggered a false RAID battery alarm. 14. Prevented raising a false alarm when the Console Domain was rebooted. 15. Enhanced the alarming mechanism to prevent false alarms around excess Management Console High Virtual Memory Usage. 16. Fixed an issue where large log files can cause a display error in the Management Console log viewer. 17. NTP will now start even if the NTP server name contains a hyphen. 18. Changing time zone on the Console Domain now correctly triggers a system reset to ensure all processes pick up the new time. 19. IPv6 stateless address auto-configuration (SLAAC) has been disabled on System Platform. Previously, the system could acquire a SLAAC address as well as its static IPv6 address and display the SLAAC address on the Management Console. 20. An issue regarding an alarm being generated when a user logs in via the Management Console and changes his/her own password has been resolved. 6

7 Known Issues and Workarounds 1. If the time and date on System Platform Date/Time Configuration page is moved back to a time that is earlier than the time of System Platform installation, the sanity heartbeat mechanism between System Platform and the VMs could be affected. The machines will reboot and the template may need to be reinstalled to recover the sanity process. Setting the time backwards will only trigger this problem if the time is moved to before System Platform was installed. For example, if System Platform was installed with a system time of November 26th, 11:00 AM and the time is then set to November 25th, 10:00AM, then the sanity heartbeat mechanism between System Platform and the VMs will invalidate the template certificates and the sanity process will fail. The template would need to be re-installed to refresh the template certificates. 2. Occasionally, the System Platform patch installation page continues to display is being installed even when the patch is complete. Workaround: Manually refresh the browser via the browser refresh button. System Platform will display has been successfully installed if the patch has completed at that time. If "is being installed" remains to be displayed, please continue to wait. Note: System Manager updates may take up to 45 minutes to install. 3. Occasionally on R6.2.2, when a template upgrade is cancelled, System Platform will display the new template version on the manage page even though the system has rolled back to the previous version. This is a display issue and can be corrected by restarting the Console Domain. 4. Host names consisting of only numeric digits are not supported. They will not allow System Platform to boot up. 5. At the end of a template installation on R6.2.2, the modal panel message that indicates installation is complete incorrect states template upgrade is complete when the message should state template installation is complete. This is only a display issue and the installation is complete when the message appears. 6. IPv6 address display. When IPv6 is enabled and configured, System Platform only displays Console Domain's and Domain-0's IP v6 addresses on the Manage Machines page. The templates IPv6 addresses (including Services VM) can be found on the Network Configuration page. 7

8 7. When System Platform is removed from the system, it causes a problem with the path for the getlogs command on Domain-0. Workaround: 1. ssh to dom0 as admin and then switch to root 2. cd /tmp 3. [root@dom0 tmp]#./getlogs Collecting commands history... Copying files... All files have been copied Running commands In a System Platform High Availability (HA) system, do not make user administration changes including password modifications on the standby/secondary server before starting HA on the primary server. Upon starting HA: Changes made on the standby server cause the primary server to unexpectedly synchronize to the latest (new/modified) settings. LDAP replication, by default, captures the most recent administrative entries made on either the primary server or the standby/secondary server. These conditions can result in an unexpected updates to the primary server. 9. Applying System Platform patches on HA failover systems. Unless the release notes for a patch specify otherwise, apply the patch on both machines if the patch includes a Domain-0 patch. Always check the patch release notes for the detailed information on how to apply the patch on HA systems. On a HA failover system, stop HA and remove the HA configuration before applying the patch and apply it on the System Platform Management Consoles of both the primary and secondary nodes. For any operation that requires HA to be stopped (platform upgrade, template upgrade and patch application), the stop HA should be followed by the removal of the HA configuration. The user may then configure and start HA after the operation is completed. 10. In a HA configuration, any hardware maintenance (e.g. replacing hard disks or power modules) must be conducted on the standby server after it is powered down. If the current active server needs hardware maintenance, perform an interchange to make it a standby server and then perform the maintenance operation after the server is powered down. If this guideline is not followed, it is possible that the HA system may not work as desired once the hardware is replaced. 8

9 11. Failure to remove HA before performing a platform upgrade could lead to an incorrect configuration of the system and the inability to start HA. This condition could lead to the necessity of re-installing System Platform on the affected systems. 12. After HA has finished synchronizing the drives, do not immediately perform a manually interchange. Some processes are still running and this may cause an issue if a manual interchange is performed too quickly. Wait 90 seconds before starting a manual interchange after the synchronization is complete. This issue is only present immediately after the drives synchronize. A manual interchange can be conducted normally at any other time. 13. Upgrading from R6.0.3 to R6.2.1 may hang at the HA synchronization step. After upgrading from R6.0.3 to R6.2.1 on an HA pair following the steps of stop HA and remove HA configuration, when HA is started, the HA synchronization step may hang and may say, Waiting for Connection. This can be rectified by rebooting the standby server while HA is running. 14. Alarm Generation will be delayed when the crossover connection is removed and reconnected in HA scenario. In an HA scenario where the crossover connection is removed and reconnected, a delayed alarm (the delay might be more than 1 hour) will be observed on an SNMP trap receiver. This could be caused by a full scan of the System Platform logs by the System Manager spirit agent. 15. On HA configurations, AVPC (VSP High Load Average CDOM) and AVPC22010 (VSP High disk read rate on disk (sda)) alarms are logged incorrectly due to the HA process running. 16. Virtual Machine state shows as stopped when running Machine Preserving High Availability (MPHA). During a MPHA operation or after an interchange, a machine s state may briefly show as stopped on the Management Console Manage page. This is only a display issue and machine operation is completely unaffected. 17. Do not use the media check on an HP DL360 G7, the installation will stall. If this occurs, reboot the server and proceed with the installation without performing the media check. 18. System Platform upgrades using a USB device are not supported on an HP DL360 G7. When used for System Platform upgrades, USB drives cause boot problems on the HP DL360 G7. USB devices may be used for template upgrades, although the USB drive must not be attached when the System Platform upgrade is performed. 9

10 19. Changing the password for the first time while logged into WebLM causes Tomcat catalina.out to error and lists exceptions. This issue resides in WebLM standalone releases (all releases up to 4.5.5). The issue does not impact WebLM functionality. 20. The CDOM fully qualified hostname in /etc/hosts is not correct after being renamed from the Management Console. If a user renames the Console Domain hostname using an extension of the old hostname, the Console Domain hostname in /etc/hosts hosts file will be misconfigured as shown in the following example: Old hostname: hostname.example.com New hostname: hostname-2.example.com Resulting misconfigured new fully qualified hostname in the /etc/hosts file: hostname-2-2.example.com When changing the Console Domain hostname, do not use an extension of the existing hostname. 21. From the Management Console, static routes can only be added to the public bridge (avpublic). 22. The System Platform Management Console will not be accessible if the Domain-0 disk becomes full. Domain-0 should not be used for file storage. System Platform will rotate log files and remove old tmp files to ensure files and directories are prevented from growing larger than their allowed sizes. However, directly loading large files unrelated to System Platform onto Domain-0 could fill the hard drive and result in system issues. 23. Internet Explorer (IE) may not load pages when accessing the Management Console. When accessing the Management Console page, IE (versions 7, 8 or 9) may display the following error: Internet Explorer cannot display the webapp, or it may stay within the current page instead of navigating to the selected page. This happens when a page cannot respond to IE within 30 seconds. The problem has been observed on some template installation/upgrade pages, on the High Availability Configuration page and on the Network Configuration page. If IE is your preferred browser, consider applying the proposed solutions form the Microsoft Knowledge Base ( 10

11 24. Depending on the BIOS version, it is possible to receive Invalid checksum errors during ACPI processing at boot time. These errors occur when the ACPI tables in the BIOS contain incorrect checksums. BIOS vendors often only test their BIOS on Windows. Windows is more lenient with ACPI checksums. As a result, invalid checksums in ACPI tables escape this type of testing. Linux is less forgiving of checksum errors and they are occasionally received during start up. These errors are dependent purely on the version of BIOS installed. Sometimes, upgrading the BIOS will resolve the errors. Linux ignores the offending ACPI table and System Platform makes no use of ACPI power management, so these errors are completely benign. 25. When running System Platform on a S8300D from the gateway, the session icc command will not work unless the gateway is running firmware version or higher. 26. Patch search results may not display. When using HTTP to download a patch, System Platform may not locate the patch file when the user enters the full patch URL (one that includes the patch filename). For example, may mean System Platform does not locate the patch correctly. One workaround is to use just the directory URL and not include the filename. For example, enter and then select the correct patch from the resulting list. However, this will not work if the web server does not allow browsing on that directory. In that instance, point the web browser at the patch and download it to a PC and then upload it to the server using the Local File System option on the patch upload page. Using a DVD or USB stick to deliver the patch file to the system would also be valid options. 27. Kernel patching rollback limitation automatic fall back to a previous kernel will not occur if the new kernel panics. The RHEL 5 based distribution of CentOS is missing the grub-set-default command which causes the system to not automatically fall back to a previous kernel if the new kernel panics. Additional information on the CentOS bug may be obtained at 11

12 28. If the reboot button is selected, but the VM never shuts down or restarts, the Management Console will display the rebooting status indefinitely. Workaround: In the case where the VM is a Windows HVM, log into Windows from vnc and shutdown the instance gracefully (consult documentation for applications running on Windows operating systems for more information). For other VMs that hang in the shutdown process, manually issue an xm destroy command (ensure the VM is actually stuck, some VMs are slow to shutdown and may take up to 30 minutes). Using the xm destroy command on a VM that is in the process of shutting down rather than one that has stalled may result in issues. Advanced users may be able to use xm console <machine name> to check the state of the machine from its console. 12

13 Service Pack Patches please ensure that the appropriate application template has approved the patch prior to installation 1. Avaya Aura System Platform Patch This patch includes the following: - A resolution for the issue of changing the Console Domain hostname via the Management Console did not update a SAL configuration file which affected alarming. - Resolved an error when attempting to set the time from NTP servers during installation. - A High Availability start up issue has been resolved. - A resolution for the issue of a template upgrade rolling back to a previous IP address. - Resolved a number of security issues. The patch should be installed on or on The Management Console will automatically restart following installation of the patch in order for the changes to take effect. The installation of is not service affecting to the template applications. File Name: vsp-patch noarch.rpm File Size: 112 MB MD5 Checksum: d6fa68f b42407e258d0f8a4d 2. Avaya Aura System Platform Patch This patch includes the following: - Application of patches when High Availability is configure is now blocked to prevent versioning issues between the active and standby servers. - Resolved an upgrade issue from R6.0.3 in which the backup restore is not allowed. This is specifically seen with the OneX CES template. - When System Platform or was removed from the system, it caused a problem with the path for the getlogs command on Domain-0. This issue has been resolved. - A Machine Preserving High Availability (MPHA) configuration issue on the HP DL360 G7 server has been resolved along with a number of other MPHA issues for the Application Enablement Services template. - Disallowed anonymous bind and NULL BASE queries. The patch should be installed on , , or on The Management Console will automatically restart following installation of the patch in order for the changes to take effect. The installation of is not service affecting to the template applications. 13

14 File Name: vsp-patch noarch.rpm File Size: 114 MB MD5 Checksum: e7846be8d3ec851b3c14fdc0f3d9b87d 14