Avaya Aura® Presence Services 6.1

Service Pack 2 Release Notes Issue 1.1 May 2012

Introduction This document introduces the Avaya Aura® Presence Services Release 6.1 Service Pack 2 and describes known issues and the issues resolved in this release.

Contents Introduction ...... 1 Applicability ...... 2 Release History ...... 2 New Installs ...... 2 Upgrades ...... 2 Resolved Issues and Enhancements ...... 4 Security Issues and Mitigation ...... 7 Known Issues and Workarounds ...... 9 Determine Installed Version ...... 11 Installation ...... 12 Uninstallation...... 13 Verifying Presence Services Health ...... 14 Appendix ...... 15 RPMs Added in this Service Pack ...... 15 RPMs Updated in this Service Pack...... 15 RPMs Removed in this Service Pack...... 17 Modifying Network Parameters via System Platform ...... 27

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 1 of 31 Issue 1.1, May 2012 Applicability This Service Pack intended for customers running a 6.1 or higher installation of software-only, Avaya Aura® Presence Services Template for System Platform, or Avaya Aura® Solution for Midsize Enterprise.

Software Release History Application Version Release Date Avaya Aura® Presence Services 6.1 PS-06.01.00.00.0502 Avaya Aura® Presence Services 6.1 Patch 1 PS-06.01.00.01-0504 Avaya Aura® Presence Services 6.1 Patch 2 PS-06.01.00.02-0504 Avaya Aura® Presence Services 6.1 Service Pack 1 PS-06.01.01.00-0610 Avaya Aura® Presence Services 6.1 Service Pack 1 Patch 1 PS-06.01.01.01-0608 Avaya Aura® Presence Services 6.1 Service Pack 2 PS-06.01.02.00-0903 March 2012

New Installs In order to run Service Pack 2 of Presence Services, new installations should be performed using one of the following methods:

Standalone (Software-only) After installing Avaya Aura® Presence Services 6.1 (PS-06.01.00.00.0502) on a clean system per the Implementing Avaya Aura® Presence Services User Guide, download and install the Avaya Aura Presence Services 6.1 Service Pack 2 Software Update (PS- 06.01.02.00-0903) per the Installation section in this document. Avaya Aura® Presence Services Template for System Platform Install the Avaya Aura Presence Services 6.1 Service Pack 2 Software Template Installation ISO for System Platform on a certified platform running Avaya Aura® System Platform 6.0.3.6.3 (or later – check for applicable PCNs on support.avaya.com) per the Installation section in this document.. Avaya Aura® Solution for Midsize Enterprise Install the desired Avaya Aura® Solution for Midsize Enterprise template on a certified platform running Avaya Aura® System Platform. If the template includes a Presence Services domain running Presence Services 6.1, download and install the Avaya Aura Presence Services 6.1 Service Pack 2 Software Update (PS-06.01.02.00-0903) per the Installation section in this document.

Upgrades Upgrades to 6.1 Service Pack 2 are supported from the following releases:

Release Minimum Required Version Avaya Aura® Presence Services 6.1 PS-06.01.00.00.0502 + any patches Avaya Aura® Presence Services 6.1 Service Pack 1 PS-06.01.01.00-0610 + Patch 1

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 2 of 31 Issue 1.1, May 2012

It is always recommended to install the latest patch prior to upgrading to a new Service Pack.

All upgrades should download and install the Avaya Aura Presence Services 6.1 Service Pack 2 Software Update (PS-06.01.02.00-0903) per the Installation section in this document.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 3 of 31 Issue 1.1, May 2012 Resolved Issues and Enhancements This Service Pack is cumulative and contains all fixes contained in earlier 6.1 Service Packs and Patches plus the following:

Tracking # Issue wi00852369 If Enrollment password during PS install has "$" character then it is inserting wrong password in tm.properties file wi00878213 Disk space filled and alarm generation failing due to debug log level left on. Note: Debug info is now placed in /var/log/presence/presence_debug.log. This file is rotated by size (and compressed) as its contents are not required for audit and this prevents disk filling due to debug level being left on. Warnings and errors still go to /var/log/messages to allow alarms to work. wi00959214 PS SP template install fails wi00893151 Issue with stop.sh wi00877057 stopping and starting of PS from command line doesn't bring up all the components on xcp wi00931023 Prevent crash of sip-ps if user without domain has been added as a buddy contact in SMGR. wi00885724 Jabberd crashes randomly when the system is responding slow for some reason wi00945100 Changing the default gateway on the system platform conflicts with the IP address wi00945006 SP1 Network Config Parameters) Default Gateway changes on system platform but connection to PS is lost wi00879442 No validation in PS 6.1 Patch 2 installation wi00886627 SV Upg: No validation is being carried out on the Unistall option after SP 1 is installed wi00870637 Upgrade of PS 6.1 i3 to i5 issue with overwriting files wi00897551 REPLICATION_EXTERNAL_ID should be set to FQDN OF PS during Software only installation. wi00857049 Inconsistent population of host filters in SIP components at PS installation wi00399325 When presentity BLOCKs a watcher subscription using presence.wauth, incorrect state info is returned in Notify update wi00881526 PostgreSQL Security updates wi00872253 #18723: Security updates 9.0.3, 8.4.7, 8.3.14 and 8.2.20 released wi00943792 SMGR 6.2.10 Inventory field Type & Version values incorrect for PS 6.1 records wi00947694 Upgrade to SP 1 Patch 1 overwrites logs created from GA Patch 1 upgrade

Resolved Issues which apply to Avaya Aura® System Platform template-based installations only:

Tracking # Issue wi00886816 [RHSA-2011:0429-01] Important: kernel security and bug fix update wi00909727 Security: dbus- security update (RHSA-2010-0616) wi00909018 Security: [RHSA-2011:0927-01] Important: kernel security and bug fix update wi00906171 ASA-2010-291 - kernel security and bug fix update ( RHSA-2010-0723 wi00898703 MEDIUM Priority RapidResponse - Presence Services: [RHSA-2011:0412-01] Important: glibc security update wi00873014 [RHSA-2011:0303-01] Moderate: kernel security and bug fix update wi00857570 java needs to be updated to the current version wi00857122 Packages require updating wi00852589 Update Kernel per RHSA-2011-0004

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 4 of 31 Issue 1.1, May 2012 wi00835251 [RHSA-2010:0819-01] Moderate: pam security update wi00939337 Security: [picasso.dr.avaya.com #22703] LOW Priority RapidResponse - Presence Services: [RHSA-2011:1282-01] Important: nss and nspr security update wi00921360 Security: [RHSA-2011:1065-01] Important: Red Hat Enterprise Linux 5.7 kernel security and bug fix update wi00909743 Security: lftp security update (RHSA-2010-0585) wi00847263 [RHSA-2010:0978-01] Moderate: openssl security update wi00845949 [RHSA-2010:0926-01] Moderate: krb5 security update wi00843205 [RHSA-2010:0839-01] Moderate: kernel security and bug fix update wi00840255 Security advisory: update freetype package rpms wi00834364 [RHSA-2010:0787-01, RHSA-2010-0793] Important: glibc security update wi00961080 bind security update wi00906696 Presence Services: Oracle Java Critical Update Combined CVEs wi00907111 Presence Services: [RHSA-2011:0310-01] Critical: firefox security and bug fix update wi00907087 [RHSA-2011:0885-01] Critical: firefox security and bug fix update wi00898731 Presence Services: [RHSA-2011:0471-01] Critical: firefox security update wi00886815 [RHSA-2011:0436-01] Moderate: avahi security update wi00878654 [RHSA-2011:0373-01] Important: firefox security update wi00873897 [picasso.dr.avaya.com #19333] RapidResponse_Template - Master: [RHSA-2011:0318- 01] Important: libtiff security update wi00857575 security update (RHSA-2011-0180) wi00907087 firefox security and bug fix update (RHSA-2011-0885) wi00933877 Security: [RHSA-2011:1219-01] Moderate: samba security update wi00932560 Security: [RHSA-2011:1196-01] Moderate: system-config-printer security update wi00926896 Security: [RHSA-2011:1109-01] Moderate: foomatic security update wi00909373 Security:[RHSA-2011:1073-01] Low: bash security, bug fix, and enhancement update wi00909359 Security: [RHSA-2011:0999-01] Moderate: rsync security, bug fix, and enhancement update wi00907114 Presence Services: [RHSA-2011:0305-01] Important: samba security update wi00907105 Security: [RHSA-2011:0392-01] Important: libtiff security and bug fix update wi00898718 LOW Priority RapidResponse - Presence Services: [RHSA-2011:0428-01] Important: dhcp security update wi00907095 Presence Services: [RHSA-2011:0433-01] Moderate: xorg-x11-server-utils security update wi00952283 kdelibs and kdelibs3 security update (RHSA-2011-1385) wi00959214 PS SP template install fails wi00939709 System Platform indicates PS 6.1 template installation was completed successfully even though the opposite is true. wi00935200 During the itemplate installation of PS 6.2 i3 there is a delay of approximately 15 minutes between the time that the install is supposed to be completed (as per the install log on the GUI) and the actual installation is fully complete. wi00947785 If you attempt to rollback SP 1 when SP 1 Patch 1 is alpplied on top of it the GUI , it roll backs SP 1 Patch 1. It is expcted that it should give an error wi00894571 Patch or Service pack uninstall should only contain rollback option or rollback should be default wi00842482 vClass value in each tuple is not as per the presence model doc wi00950533 Date/time/timezone not updated when changed via CDOM wi00965318 PS 6.1 SP2 I7 drop to SV shows a kernel in use other that RHEL 5.3 wi00970558 RapidResponse - Presence Services: [RHSA-2011:1851-01] Critical: krb5 security update wi00966529 (SV) Installing 06.01.02.00.0702 displays lock file exists warning

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 5 of 31 Issue 1.1, May 2012

Please refer to previous release notes and PCNs for information about updates introduced in earlier releases.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 6 of 31 Issue 1.1, May 2012 Security Issues and Mitigation In order to address a number of security issues in Presence Services 6.1 System Platform Templates, a script will run during the installation of Service Pack 2 to remove/upgrade a number of RPM’s which are installed on the system. This script will operate on both System Platform template-based and Software-only (standalone) installations.

Service Pack 2 installations executed on software-only systems will only upgrade the installed version of Postgres and exit. Installations executed on System Platform Template-based deployments will run a sanity check on the template to ensure the environment has not been modified. If any modifications have been made to the template the Service Pack 2 installer will exit. This means no Service Pack 2 updates will be performed and no RPM removals/upgrades will occur.

It the installer exits during the sanity check it is recommended to review the log file in /tmp/UpdateTemplateRpms.log and reverting the to the original state by manually removing/upgrading/downgrading the RPMs as detailed in the log file.

If the sanity check passes, the RPMs listed in the section RPMs Removed in this Service Pack will be removed. The RPMs bundled in the UpdateTemplateWrapper.zip will be upgraded along with the installed versions of Postgres, JDK and the kernel. On successful completion, a system reboot will be performed. Presence Services has to be restarted manually after the reboot.

The script to remove/update the RPMs will be executed by the SP2 installer automatically.

The RPM updater script will alter the operating system; removing, updating and adding RPMs. The changes are detailed in the appendices as follows:

• RPMs which will be removed are listed in the section RPMs Removed in this Service Pack

• RPMs which are updated are listed in the section RPMs Updated in this Service Pack

• RPMs which have been added, due to new dependencies are listed in the section RPMs Added in this Service Pack

The script will complete by executing a system reboot, assuming it has successfully performed the RPM updates. If a silent installation is performed, verify successful execution by checking the log.

Note: By updating the Red Hat template, it shall be no longer possible to install/rollback previous, current or subsequent service packs or patches using the graphical installer. All subsequent installs must be performed using the silent install method.

Software-only deployments:

Software-only customers for Presence Services are required to manually upgrade their operating system to use Red Hat kernel release 2.6.18-274.7.1 (RHEL 5.7). Packages are also

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 7 of 31 Issue 1.1, May 2012 required to be upgraded to the releases as defined in the section RPMs Updated in this Service Pack.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 8 of 31 Issue 1.1, May 2012

Known Issues and Workarounds The following issues were known at the time of this Service Pack release:

Tracking # Issue n/a During PS install, if one does not enter required SAL details, the install hangs with error replace caf.zip. Workaround: Please make sure to enter SAL details at the time of PS installation. wi00966611 Incorrect cursor behavior during an install or uninstall on PS (If installing using putty from windows) Workaround: After initiating the silent install via putty press any numerical or alpha char and press “enter” this brings up the install GUI or continue silent install. Alternatively install from the console. wi00902967 DNS value not updated in /etc/resolv.conf file during Network Parameter changes on System Platform PS template (should only be 2 records in file – Search & Nameserver) Workaround: Have a single entry for “search” and “nameserver” when changing network parameters via the System Platform Presence Services UI. wi00963051 monit summary not updated with new PS hostname after presence hostname change Workaround: Use following commands: monit stop monit start wi00966609 installing 06.01.02.00.0702 displays izpack errors in PS-install.log (Install is successful but errors in log) Note: No known negative impact to SP2 functionality wi00939709 System Platform indicates PS 6.1 SP2 template installation was completed successfully even though the opposite is true. Note: In this case consult the installation logs for further information and cause of install failure. wi00978547 Location of changePSFQDN.sh has changed Note: Location has changed from /opt/Avaya/Presence/presence/bin to /opt/Avaya/Presence/install/scripts/ wi00944411 Presence Services doesn't show up under Managed Elements SMGR 6.2.10.0 Workaround: 1) Go to SMGR admin interface. 2) Click "Inventory" -> "Manage Elements" 3) Click "New" button 4) Select "Presence Services" as type 5) Set "Name" as a short host name (or other name which makes sense) 6) Set "Node" as FQDN of PS server 7) Click "Commit" n/a Secondary DNS parameter change: The current implementation only supports a change of the Primary DNS network parameter via System Platform User interface. Furthermore, the /etc/resolv.conf system file must contain only two line entries for search domain nameserver n/a System Platform Backup/Restore Process: The following instructions must be adhered to when performing a backup and restore in conjunction with network parameter changes via System Platform. Note: Backup(s) taken before IP and hostname change cannot be used for restore after IP and hostname change. Backup Login to Presence services server using ssh.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 9 of 31 Issue 1.1, May 2012 Change user to root Stop Presence by running, /opt/Avaya/Presence/presence/bin/stop.sh Start postgres service by running, service postgresql start Run Backup from System platform webconsole, Server Management -> Backup/Restore page Start Presence by running start.sh located under /opt/Avaya/Presence/presence/bin/start.sh Restore Login to Presence services server using ssh. Change user to root Stop Presence by running, /opt/Avaya/Presence/presence/bin/stop.sh Start postgres service by running, service postgresql start Run restore from System platform webconsole, Server Management -> Backup/Restore page Start Presence by running start.sh located under /opt/Avaya/Presence/presence/bin/start.sh wi01000236 As a customer I am unable to re-install PS6.1 SP2 on system platform template after executing a rollback of this software release

User Impact: If customer executes a roll-back of PS r6.1 SP2 on system platform template and subsequently attempts to re-install this software release, the installation will fail sanity check for OS and RPMs and will block install (re-install of PS Service Pack software changes in this case) i.e. creates an issue for a customer seeking to re-install SP2 on system platform template as subsequent installation will fail because RHEL OS is no longer as expected (5.3) having been upgraded during initial install to (5.7)

Note: For documented workaround instructions, refer to the Installation section in this document.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 10 of 31 Issue 1.1, May 2012 Determine Installed Version The currently installed version of Presence Services can be verified by logging in to the shell of the Presence Services machine and issuing the command:

/opt/Avaya/Presence/presence/bin/swversion.sh

Refer to the table in the Software Release History section to determine the installed release based on the version string.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 11 of 31 Issue 1.1, May 2012 Installation

For a re-installation post roll-back on system platform of Presence Services 6.1 Service Pack 2 (PS-06.01.02.00-0903) please refer to step 1 as documented below.

For a first-time system platform or software only installation of Presence Services 6.1 Service Pack 2 (PS-06.01.02.00-0903) proceed to step 6 as documented below

Reinstallation post roll-back 1. On the Presence Services 6.1 Server, back-up the file PS_RPMSanitycheck.sh extracted from PS-06.01.02.00-0903.zip by re-naming as BCKUP_PS_RPMSanitycheck.sh 2. Download the script file Avaya Aura® Presence Services 6.1 Service Pack 2 PS_RPMSanitycheck.sh from PLDS (PS000000032) 3. Copy the script file to the Presence Services 6.1 server and to same location as BCKUP_PS_RPMSanitycheck.sh 4. Re-name the script file Avaya Aura® Presence Services 6.1 Service Pack 2 PS_RPMSanitycheck.sh as PS_RPMSanitycheck.sh 5. Please proceed to step 11.

First-time Installation 6. For System Platform installations (Presence Services Template for Avaya Aura® System Platform or Avaya Aura® Solution for Midsize Enterprise), perform a backup of server using the System Platform Webconsole Backup and Restore webpage. For information regarding this feature refer to the Avaya Aura® System Platform Release Notes located on support.avaya.com. Before proceeding, upgrade Avaya Aura® System Platform to release 6.0.3.6.3 (or later – check for applicable PCNs on support.avaya.com) Note: The installation of this service pack alters the operating system of the Presence Services template, therefore a backup must be performed in the event the template must be reinstalled to return to the previous state. 7. Download Service Pack 2 (PS-06.01.02.00-0903.zip) from PLDS. 8. Copy the ZIP file to the Presence Services 6.1 server. 9. Login into the presence server as craft and execute the “su -“ command and enter the root user’s password. 10. Unzip the file: unzip PS-06.01.02.00-0903.zip 11. Stop Presence Services: /opt/Avaya/Presence/presence/bin/stop.sh Note: It is important to verify that Presence Services has stopped before proceeding with the install of the service pack. This can be done using the following command: monit summary

The output of the command should show the processes as “not monitored” (i.e stopped) except the System that appears as “running”, The install should not be attempted before all process have stopped.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 12 of 31 Issue 1.1, May 2012 12. Run the PS-06.01.02.00-0903.sh script with the desired install option: For Graphical mode: ./PS-06.01.02.00-0903.sh –ci To launch the graphical installer. Follow the instructions and then click Done to complete the installation.

OR

Silent/Remote install mode: Run the install script and supply properties file: ./PS-06.01.02.00-0903.sh –ci \ autoInstall_Presence_Services.properties Please make sure that the above script has executable permission. 13. (Software-only installations) Restart Presence Services: /opt/Avaya/Presence/presence/bin/start.sh

OR

(System Platform template-based installations) Once rebooted restart presence services using the following script: /opt/Avaya/Presence/presence/bin/start.sh

Please make sure that all health checks are done and are successful. The minimum list of health checks to be performed is listed in the Verifying Presence Services Health section.

Uninstallation System Platform template-based installations:

As this service pack alters the operating system of the Presence Services template, it is necessary to restore the presence services template to the service pack pre-install state. The Presence Services command line interface, uninstall of this service pack is not supported on System Platform Presence Services templates. Please reinstall the previous Presence Services template and restore the backup created on System Platform prior to Service Pack 2 installation. For more information on the operating system changes refer to the Security Issues and Mitigation section of this document. Please refer to previous release notes and PCNs for information about updates introduced in earlier releases.

Software-only installations:

1. Stop Presence Services: /opt/Avaya/Presence/presence/bin/stop.sh 2. Run the PS-06.01.02.00-0903.sh script with the desired uninstall option: Graphical mode (Standalone only): ./PS-06.01.02.00-0903.sh –cu to launch the graphical installer.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 13 of 31 Issue 1.1, May 2012 Follow the instructions and then click Done to complete the installation.

OR

Silent/Remote install mode: Run the install script and supply properties file: ./PS-06.01.02.00-0903.sh –cu autoUninstall.properties

Notes:

1. If you want to completely uninstall the product in the silent install mode, edit the autoUninstall.properties file to change Uninstall option to “uninstall” 2. The security patches applied to the Presence Services Postgres Database will not be rolled back on uninstall of the Service Pack.

Verifying Presence Services Health The following steps are intended to be a brief guide to aid in executing a minimal set of health checks of components involved in the Presence Services solution.

1) Access the PS XCP controller at https://:7300/admin and verify all the components are green. 2) Use the “monit summary” command to make sure that all processes shown are in “running” state. 3) Run /opt/Avaya/Presence/presence/bin/presstatus tool to check the PS components status. Make sure that license is not expired and the user count under the user management component is correct 4) Make sure that the PS replica status is in a synchronized state. This can be checked from System Manager: dashboard  services  replication psreplica_6.1 5) Run following command on Presence Services to confirm that the users are provisioned: psql -U postgres -d xcp - "select * from users"; 6) Make sure that alarms are working by generating a test alarm using the following utility: /opt/Avaya/SPIRIT/6.1.5/scripts/utils/generateTestAlarm.sh (Alarms can be viewed on the System Manager: dashboard services  events  alarms section)

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 14 of 31 Issue 1.1, May 2012

Appendix

RPMs Added in this Service Pack The following RPM packages were added due to new dependencies introduced in Service Pack 2:

dmraid-events fipscheck-lib hmaccalc iscsi-initiator-utils libgomp python-libs sgpio RPMs Updated in this Service Pack The following RPM packages are updated as part of Service Pack 2:

acl-2.2.39-6.el5.i386.rpm audit-libs-1.7.18-2.el5.i386.rpm audit-libs-python-1.7.18-2.el5.i386.rpm authconfig-5.3.21-7.el5.i386.rpm autofs-5.0.1-0.rc2.156.el5_7.4.i386.rpm bash-3.2-32.el5.i386.rpm bind-libs-9.3.6-16.P1.el5.i386.rpm bind-utils-9.3.6-16.P1.el5.i386.rpm binutils-2.17.50.0.6-14.el5.i386.rpm bzip2-1.0.3-6.el5_5.i386.rpm bzip2-libs-1.0.3-6.el5_5.i386.rpm chkconfig-1.3.30.2-2.el5.i386.rpm compat-libstdc33-3.2.3-61.i386.rpm coreutils-5.97-34.el5.i386.rpm cpio-2.6-23.el5_4.1.i386.rpm crash-4.1.2-8.el5.i386.rpm cryptsetup-luks-1.0.3-8.el5.i386.rpm curl-7.15.5-9.el5_7.4.i386.rpm cyrus-sasl-lib-2.1.22-5.el5_4.3.i386.rpm db4-4.3.29-10.el5_5.2.i386.rpm device-mapper-1.02.63-4.el5.i386.rpm device-mapper-event-1.02.63-4.el5.i386.rpm device-mapper-multipath-0.4.7-46.el5_7.1.i386.rpm dmidecode-2.11-1.el5.i386.rpm dmraid-1.0.0.rc13-65.el5.i386.rpm dos2unix-3.1-27.2.el5.i386.rpm e2fsprogs-1.39-33.el5.i386.rpm e2fsprogs-libs-1.39-33.el5.i386.rpm ethtool-6-4.el5.i386.rpm expat-1.95.8-8.3.el5_5.3.i386.rpm file-4.17-15.el5_3.1.i386.rpm

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 15 of 31 Issue 1.1, May 2012 filesystem-2.4.0-3.el5.i386.rpm findutils-4.2.27-6.el5.i386.rpm fipscheck-1.2.0-1.el5.i386.rpm freetype-2.2.1-28.el5_7.1.i386.rpm gdbm-1.8.0-26.2.1.el5_6.1.i386.rpm gettext-0.17-1.el5.i386.rpm glib2-2.12.3-4.el5_3.1.i386.rpm glibc-2.5-65.i686.rpm glibc-common-2.5-65.i386.rpm -1.4.1-3.el5_4.8.i386.rpm grep-2.5.1-55.el5.i386.rpm grub-0.97-13.5.i386.rpm gzip-1.3.5-13.el5.i386.rpm hwdata-0.213.24-1.el5.noarch.rpm initscripts-8.45.38-2.el5.i386.rpm iproute-2.6.18-11.el5.i386.rpm iptables-1.3.5-5.3.el5_4.1.i386.rpm iputils-20020927-46.el5.i386.rpm kernel-xen-2.6.18-274.7.1.el5.i686.rpm kpartx-0.4.7-46.el5_7.1.i386.rpm krb5-libs-1.6.1-62.el5.i386.rpm less-436-7.el5.i386.rpm libacl-2.2.39-6.el5.i386.rpm libevent-1.4.13-1.i386.rpm libgcc-4.1.2-51.el5.i386.rpm libgcrypt-1.4.4-5.el5.i386.rpm libselinux-1.33.4-5.7.el5.i386.rpm libsemanage-1.9.1-4.4.el5.i386.rpm libsepol-1.15.2-3.el5.i386.rpm libstdc4.1.2-51.el5.i386.rpm libsysfs-2.1.0-1.el5.i386.rpm libtool-ltdl-1.5.22-7.el5_4.i386.rpm libuser-0.54.7-2.1.el5_5.2.i386.rpm libvolume_id-095-14.27.el5_7.1.i386.rpm -2.6.26-2.1.12.el5_7.1.i386.rpm logrotate-3.7.4-12.i386.rpm lvm2-2.02.84-6.el5_7.1.i386.rpm man-1.6d-2.el5.i386.rpm man-pages-2.39-17.el5.noarch.rpm mkinitrd-5.1.19.6-71.el5.i386.rpm module-init-tools-3.3-0.pre3.1.60.el5_5.1.i386.rpm nash-5.1.19.6-71.el5.i386.rpm net-snmp-libs-5.3.2.2-14.el5_7.1.i386.rpm net-tools-1.60-81.el5.i386.rpm newt-0.52.2-15.el5.i386.rpm nspr-4.8.8-1.el5_7.i386.rpm nss-3.12.10-7.el5_7.i386.rpm ntp-4.2.2p1-15.el5.i386.rpm ntsysv-1.3.30.2-2.el5.i386.rpm numactl-0.9.8-12.el5_6.i386.rpm openldap-2.3.43-12.el5_7.9.i386.rpm openssh-4.3p2-72.el5_7.5.i386.rpm openssh-clients-4.3p2-72.el5_7.5.i386.rpm

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 16 of 31 Issue 1.1, May 2012 openssh-server-4.3p2-72.el5_7.5.i386.rpm openssl-0.9.8e-20.el5.i686.rpm pam-0.99.6.2-6.el5_5.2.i386.rpm pam_krb5-2.2.14-21.el5.i386.rpm parted-1.8.1-28.el5.i386.rpm passwd-0.73-2.i386.rpm pciutils-3.1.7-3.el5.i386.rpm pcre-6.6-6.el5_6.1.i386.rpm perl-5.8.8-32.el5_6.3.i386.rpm popt-1.10.2.3-22.el5_7.2.i386.rpm procps-3.2.7-17.el5.i386.rpm psmisc-22.2-7.el5_6.2.i386.rpm python-2.4.3-44.el5_7.1.i386.rpm readline-5.1-3.el5.i386.rpm redhat-release-5Server-5.7.0.3.i386.rpm rmt-0.4b41-5.el5.i386.rpm rpm-4.4.2.3-22.el5_7.2.i386.rpm rpm-libs-4.4.2.3-22.el5_7.2.i386.rpm rpm-python-4.4.2.3-22.el5_7.2.i386.rpm sed-4.1.5-8.el5.i386.rpm setup-2.5.58-7.el5.noarch.rpm shadow-utils-4.0.17-18.el5_6.1.i386.rpm sqlite-3.3.6-5.i386.rpm sudo-1.7.2p1-10.el5.i386.rpm sysfsutils-2.1.0-1.el5.i386.rpm sysklogd-1.4.1-46.el5.i386.rpm SysVinit-2.86-17.el5.i386.rpm tar-1.15.1-30.el5.i386.rpm tcpdump-3.9.4-15.el5.i386.rpm tcp_wrappers-7.6-40.7.el5.i386.rpm tcsh-6.14-17.el5_5.2.i386.rpm traceroute-2.0.1-6.el5.i386.rpm tzdata-2011l-4.el5.i386.rpm udev-095-14.27.el5_7.1.i386.rpm util-linux-2.13-0.56.el5.i386.rpm vim-minimal-7.0.109-7.el5.i386.rpm vixie-cron-4.1-77.el5_4.1.i386.rpm watchdog-5.6-1.el5.i386.rpm wget-1.11.4-2.el5_4.1.i386.rpm xinetd-2.3.14-13.el5.i386.rpm zlib-1.2.3-4.el5.i386.rpm PyXML-0.8.4-4.el5_4.2.i386.rpm RPMs Removed in this Service Pack The following RPMs are obsolete or no longer required in Service Pack 2 and have therefore been removed:

a2ps acpid alchemist alsa-lib alsa-utils

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 17 of 31 Issue 1.1, May 2012 amtu anacron apmd arts aspell aspell-en at atk attr audiofile audit authconfig- avahi avahi-compat-libdns_sd avahi-glib avahi-qt3 bitmap-fonts bitstream-vera-fonts bluez- bluez-libs bluez-utils busybox cadaver ccid cdparanoia-libs checkpolicy chkfontpath comps-extras conman coolkey cpp cpuspeed cups cups-libs cyrus-sasl cyrus-sasl-plain dbus dbus-glib dbus-libs dbus-python dejavu-lgc-fonts Deployment_Guide-en-US desktop-backgrounds-basic desktop-file-utils dhclient dhcpv6-client dnsmasq docbook-dtds dosfstools dump elinks emacs

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 18 of 31 Issue 1.1, May 2012 emacs-common emacs-leim emacspeak enscript esound fbset fetchmail finger firstboot firstboot-tui fontconfig foomatic freeglut ftp gail gamin-python GConf2 gdm ghostscript giflib glx-utils gnome-doc-utils gnome-keyring gnome-mime-data gnome-mount gnome-python2 gnome-python2-bonobo gnome-python2-canvas gnome-python2-extras gnome-python2- gnome-python2-gnomevfs gnome-python2-gtkhtml2 gnome-vfs2 gnu-efi gnupg gpm gtk2 gtk2-engines gtkhtml2 hal hal-cups-utils hicolor-icon-theme hpijs hplip htdig htmlview ifd-egate ipsec-tools iptables-ipv6 iptstate irda-utils irqbalance

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 19 of 31 Issue 1.1, May 2012 jwhois kbd kdebase kdelibs kdnssd-avahi kexec-tools krb5-auth-dialog krb5-workstation ksh kudzu lcms lftp libaio libart_lgpl libbonobo libbonoboui libcroco libdaemon libdmx libdrm liberation-fonts libfontenc libFS libglade2 libgnome libgnomecanvas libgnomeui libgsf libhugetlbfs libICE libIDL libjpeg libmng libnotify libogg libpcap libpng libraw1394 librsvg2 libselinux-python libselinux-utils libSM libtiff libvorbis libwnck libX11 libXau libXaw libXcomposite libXcursor libXdamage libXdmcp libXext

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 20 of 31 Issue 1.1, May 2012 libXfixes libXfont libXfontcache libXft libXi libXinerama libxkbfile libxml2-python libXmu libXpm libXrandr libXrender libXres libXScrnSaver libXt libXTrap libXtst libXv libXxf86dga libXxf86misc libXxf86vm linuxwacom lm_sensors m2crypto m4 mailcap mailx make mdadm mesa-libGL mesa-libGLU mgetty microcode_ctl mkbootdisk mlocate mozldap mtools mtr mutt nano neon NetworkManager NetworkManager-glib nfs-utils nfs-utils-lib notification-daemon notify-python nscd nss_db nss_ldap nss-tools OpenIPMI

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 21 of 31 Issue 1.1, May 2012 OpenIPMI-libs openjade opensp openssh-askpass ORBit2 pam_pkcs11 pango paps patch pax pcsc-lite pcsc-lite-libs perl-String-CRC32 pinfo pirut pkgconfig pkinit-nss pm-utils policycoreutils policycoreutils-gui ppp procmail psacct psgml psutils pycairo pygobject2 pygtk2 pygtk2-libglade pyOpenSSL pyorbit PyQt python-elementtree python-iniparse python-ldap python-numeric python-sqlite python-urlgrabber pyxf86config qt quota rdate rdist readahead redhat-artwork redhat-lsb redhat-menus redhat-release-notes rhel-instnum rhgb rhn-check rhn-client-tools rhnlib

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 22 of 31 Issue 1.1, May 2012 rhnsd rhn-setup rhn-setup-gnome rhpl rhpxl rng-utils rp-pppoe rsh rsync sabayon sabayon-apply samba-client samba-common scrollkeeper selinux-policy selinux-policy-devel selinux-policy-targeted sendmail setarch setools setroubleshoot setroubleshoot-plugins setroubleshoot-server sgml-common shared-mime-info sip slrn smartmontools sos sox specspo startup-notification stunnel svrcore synaptics syslinux system-config-date system-config-display system-config-kdump system-config-keyboard system-config-language system-config-lvm system-config-netboot system-config-netboot-cmd system-config-network system-config-network-tui system-config-printer system-config-printer-libs system-config-rootpassword system-config-securitylevel system-config-securitylevel-tui system-config-services system-config-soundcard

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 23 of 31 Issue 1.1, May 2012 system-config-users talk tcl tclx telnet tftp-server tk tmpwatch tree ttmkfdir udftools unix2dos urw-fonts usbutils usermode-gtk vconfig vim-common vim-enhanced vnc-server vte wdaemon wireless-tools words wpa_supplicant Xaw3d xkeyboard-config xml-common xorg-x11-apps xorg-x11-drivers xorg-x11-drv-acecad xorg-x11-drv-aiptek xorg-x11-drv-apm xorg-x11-drv-ark xorg-x11-drv-ast xorg-x11-drv-ati xorg-x11-drv-calcomp xorg-x11-drv-chips xorg-x11-drv-cirrus xorg-x11-drv-citron xorg-x11-drv-cyrix xorg-x11-drv-digitaledge xorg-x11-drv-dmc xorg-x11-drv-dummy xorg-x11-drv-dynapro xorg-x11-drv-elo2300 xorg-x11-drv-elographics xorg-x11-drv-evdev xorg-x11-drv-fbdev xorg-x11-drv-fpit xorg-x11-drv-glint xorg-x11-drv-hyperpen xorg-x11-drv-i128 xorg-x11-drv-i740

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 24 of 31 Issue 1.1, May 2012 xorg-x11-drv-i810 xorg-x11-drv-jamstudio xorg-x11-drv-joystick xorg-x11-drv-keyboard xorg-x11-drv-magellan xorg-x11-drv-magictouch xorg-x11-drv-mga xorg-x11-drv-microtouch xorg-x11-drv-mouse xorg-x11-drv-mutouch xorg-x11-drv-neomagic xorg-x11-drv-nsc xorg-x11-drv-nv xorg-x11-drv-palmax xorg-x11-drv-penmount xorg-x11-drv-rendition xorg-x11-drv-s3 xorg-x11-drv-s3virge xorg-x11-drv-savage xorg-x11-drv-siliconmotion xorg-x11-drv-sis xorg-x11-drv-sisusb xorg-x11-drv-spaceorb xorg-x11-drv-summa xorg-x11-drv-tdfx xorg-x11-drv-tek4957 xorg-x11-drv-trident xorg-x11-drv-tseng xorg-x11-drv-ur98 xorg-x11-drv-v4l xorg-x11-drv-vesa xorg-x11-drv-vga xorg-x11-drv-via xorg-x11-drv-vmmouse xorg-x11-drv-vmware xorg-x11-drv-void xorg-x11-drv-voodoo xorg-x11-filesystem xorg-x11-fonts-100dpi xorg-x11-fonts-75dpi xorg-x11-fonts-base xorg-x11-fonts-ISO8859-1-100dpi xorg-x11-fonts-ISO8859-1-75dpi xorg-x11-fonts-misc xorg-x11-fonts-truetype xorg-x11-fonts-Type1 xorg-x11-font-utils xorg-x11-server-utils xorg-x11-server-Xnest xorg-x11-server-Xorg xorg-x11-twm xorg-x11-utils xorg-x11-xauth

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 25 of 31 Issue 1.1, May 2012 xorg-x11-xfs xorg-x11-xinit xorg-x11-xkb-utils xsri xterm xulrunner yelp ypbind yp-tools yum yum-metadata-parser yum-rhn-plugin yum-security yum-updatesd

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 26 of 31 Issue 1.1, May 2012 Modifying Network Parameters via System Platform Avaya Aura® Presence Services 6.1 Service Pack 1 introduced support enabling the ability to change network parameters: Presence Services hostname, IP address, netmask, gateway, domain search list and DNS on System Platform Presence Services templates. Since Service Pack 2 is cumulative, it also permits this functionality.

Note that when changing the Presence Services hostname, the user must run a script on the Presence Services template domain after changing the Presence hostname on System Platform.

After changing any of the supported network parameters, the /opt/Avaya/Presence-VA/psva/ps- sp-utils/SPchangeParam.log file can be used to check the progress of the change.

1. Change Primary DNS DNS can be changed from System platform web console screen Server Management  Network Configuration The field name is: Primary DNS (Under General Network settings)

After it is changed and setting updated successfully on this page, SSH to the Presence Services template domain and verify this configuration file has a new DNS value: /etc/resolv.conf

2. Change Gateway Gateway can be changed from System platform web console screen Server Management  Network Configuration The field name is: Default Gateway (Under General Network settings)

After it is changed and setting updated successfully on this page, SSH to the Presence Services template domain and verify this configuration file has a new Gateway value: /etc/sysconfig/network-scripts/ifcfg-eth0

3. Change Domain Search list Domain search list can be changed from System platform web console screen Server Management  Network Configuration The field name is: Domain Search List (Under General Network settings)

After it is changed and setting updated successfully on this page, SSH to the Presence Services template domain and verify this configuration file has a new domain search list value: /etc/resolv.conf

4. Change Default Netmask Default netmask can be changed from System platform web console screen Server Management  Network Configuration The field name is: Netmask (Under Domain network Interface- > Domain 0 ->

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 27 of 31 Issue 1.1, May 2012 avpublic)

After it is changed and setting updated successfully on this page, SSH to the Presence Services template domain and verify this configuration file has a new netmask value: /etc/sysconfig/network-scripts/ifcfg-eth0

5. Change Presence IP Address Access the System Manager via and change the new Presence IP for the Presence entry. For example: In the /etc/hosts file of SMGR change presence IP address to new IP address.

The Presence VM IP address can be changed from System platform web console screen Server Management  Network Configuration The field name is: IP address of the presence_va

After it is changed and the setting updated successfully on this page, try to access Presence VM with its new IP.

If Presence is accessible with new IP address then try to do some basic testing to see after IP changes things are working fine. a. Go to Presence XCP controller UI and see all the component are up and running. b. On Presence box, go to $SPIRIT_HOME/scripts/utils/ and run this script ./generateTestAlarm.sh and verify on the SMGR GUI under Events->Alarming section if the test alarms are coming. c. Go to the SMGR GUI, under Replication and check if Presence replica is still in Synchronized state.

After changing the Presence Services IP, all clients using the Presence IP has to be restarted with new the Presence IP.

6. Change Presence Hostname Pre-PS Hostname change Steps: a. Go to SMGR GUI under replication section and remove the replica for PS with old hostname. b. Make sure the new PS hostname is resolvable from the SMGR, for example adding new hostname entry in the SMGR /etc/hosts file or add in the DNS.

Changing PS Hostname: Presence Hostname can be changed from System platform web console screen Server Management  Network Configuration The field name is: presence_va hostname

To change the Presence Services hostname in the Presence domain, manually run the script /opt/Avaya/Presence/install/scripts/changePSFQDN.sh. In parallel you can

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 28 of 31 Issue 1.1, May 2012 see the status in the log file /opt/Avaya/Presence-VA/psva/ps-sp- utils/SPchangeParam.log

Once the log file indicates the hostname has changed, perform the following basic test to verify the hostname change succeeded and basic services such as replication, alarming, and all PS components are still up and running:

a. Go to Presence XCP controller UI and see all the component are up and running. b. On Presence box, go to $SPIRIT_HOME/scripts/utils/ and run this script ./generateTestAlarm.sh and verify on the SMGR GUI under Events->Alarming section if the test alarms are coming. c. Go to the SMGR GUI, under Replication and check if Presence replica is still in Synchronized state.

Post-PS Hostname change Steps:

1. Re-Configure the LPS client a. Take a backup of LPS client file generic.keystore.jks. b. Replace the LPS client generic.keystore.jks file with the PS generic.keystore.jks located under $PRES_HOME/jabber/xcp/certs/ c. Update the hostname name entry in the LPS .properties file with the new hostname value. 2. Re-Configure the SIP Tester client a. Take a backup of generic.keystore.jks file under the SIP tester client. b. Replace the SIP tester generic.keystore.jks file with the PS generic.keystore.jks located under $PRES_HOME/jabber/xcp/certs/ 3. Re-Configure the OCS a. Step1: Modifying Presence Services Server CA certificate to Microsoft Edge Server Trusted Root Certificates i. On the Presence Services server locate the certificate with name similar to export-xxx.trusts in the $PRES_HOME/jabber/xcp/certs directory and copy to the Microsoft Edge server. ii. To import the new hostname certificates in Edge Server to Microsoft 1. Remove the old hostname certificate for the old hostname a. In MMC, open Certificates Snap-in for Edge Server b. Open Certificates/Trusted Root Certification Authorities/Certificates. c. Remove the certificate may display as Default. iii. To import the new hostname certificates in Edge Server to Microsoft: a. In MMC, open Certificates Snap-in for Edge Server b. Open Certificates/Trusted Root Certification Authorities/Certificates. c. In the left-hand pane, click on All Tasks > Import.

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 29 of 31 Issue 1.1, May 2012 d. The system launches the Certificate Import Wizard. Follow the steps of the Wizard and browse for the export-xxx.trusts file you copied in Step 1. iv. Verify the Certificate is in the Certificates/Trusted Root Certification Authorities/ Certificates list. You may need to use the refresh button to update the list. The certificate may display as Default. b. Step 2: Modifying OCS Edge IM service provider i. Go to Start > Control Panel. The system displays the Control Panel window. ii. Double-click Administrative Tools, and then double-click Computer Management. iii. Under Services and Applications, select Microsoft Office Communications2007. iv. Right-click Microsoft Office Communications 2007 and select Properties > IM Provider Tab. v. On the IP Provider tab, click Edit. vi. Put the new PS FQDN in ”Network address of the IM service provider Access Edge” vii. Click OK. c. Step 3: Adding a DNS new hostname SRV(Services location) record for the OCS Gateway i. Adding a new host (A) for new hostname 1. Right-click on the domain created and choose New Host (A). 2. In the New Host dialog box, enter the Presence Services server name and IP address. For example, chat.pres.test.com or chat.example.com for the two example domains given earlier. 3. Click Add Host and then click Done. Note: When you add New Host (A) in DNS, check the associated pointer. This may eliminate the need to add the machine name to the Reverse Lookup Zone if that zone already exists. ii. Removing the old host(A) for old hostname d. Step 4: Modifying the SRV record for new hostname i. In the Service field, enter _sipfederationtls. ii. In the Port number field, enter 5061. iii. In the Host offering this service field, enter the FQDN of the new Presence Service server hostname. For example, chat.pres.test.com or chat.example.com for the two example domains given earlier. iv. Click OK . v. Click Done. e. Step5 : Modifying reverse pointer

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 30 of 31 Issue 1.1, May 2012 i. Right-click on Reverse Lookup Zone ii. Find the Pointer(RTR) record for the PS server ip address. iii. Double click the Pointer(RTR) record for the PS server ip address, change the “Host name” to the new PS server hostname. f. Step 6: Testing DNS records from Microsoft Edge Server i. Open a console on the Microsoft Edge. ii. Run nslookup .The system displays the IP address of Presence Services (PS). iii. Run nslookup .The system displays the FQDN of the Presence Services. iv. Run .The system displays the FQDN and IP address of the Presence Services and port5061. g. Step7: Restart OCS Edge Server

7. Change Presence Timezone Change the time zone of the Presence Services Template hosted by System Platform by the performing the following steps: a. To change the time zone via the System Platform User Interface, click on Server Management in the left panel of the UI, then click on Date/Time Configuration. b. The Date/Time Configuration page is now displayed in the user interface, in the Set Date and Time panel you may select the desired time zone and click Set Time to save the configuration change. c. Run the date command to see if the new time zone is updated, it takes few minutes. #date Wed Dec 21 15:02:47 GMT 2011-12-21

Note: in the above example time zone is changed to GMT

When the time zone on the Presence Services Template is changed using the System Platform User Interface , System Platform must be manually rebooted, this in turn will force a reboot of the Presence Services Template and the time zone change will take effect

Avaya Aura® Presence Services 6.1 SP 2 Release Notes Page 31 of 31 Issue 1.1, May 2012