Open Mic on Sametime9 Install -Best Practices

Open Mic on
Sametime 9 Installs – Best practices,
tips and tricks
Date: 20th
March, 2014

| © 2014 IBM Corporation22
Open Mic Team
• Subhashini Srinivasan – IBM ICS Technical Lead for Sametime Install/System
Console
• Presenter
• Subhashini Raman - IBM ICS Software Engineer, Sametime Install
• Presenter
• Pankaj Khamkar - IBM ICS Software Engineer, Sametime Install
• Presenter
• Vinayak Tavargeri – IBM ICS Support
• Facilitator for Open Mics

3 | © 2014 IBM Corporation
Source If Applicable
IBM Presentation Template Full Version
Agenda
■ Overview
─ What's new in Sametime 9 Installs
─ What will be covered in this call
■ Sametime Video MCU installation
■ Sametime Video Manager
─ Changes in Sametime 9.0
─ Media manager Components
─ Installing Video Manager – Preparation & Planning
─ Installing Video Manager - Install
─ Video Manager Uninstallation
─ Video manager Logs Location
■ Sametime Community server, Gateway and Client installs
─ Changes in Sametime 9 around installation and upgrade of Sametime Community server, Gateway server
and Sametime client components
■ Open Q&A

Sametime Video MCU Installation

Video MCU overview
■ Non-Websphere server with no Java requirements at runtime
■ Non-Installation Manager install, simple RPM-based install. Requires Java for installation.
■ VMCU server is a standalone node (no federation, no WAS concepts)
■ VMCU scaling is farm-based.
■ Linux only install supported on RHEL 5, RHEL 6, SLES11
■ Set of total 15 RPMs
■ RPM install to be invoked via a shell script - installvideomcu_xxxx.sh
■ console.properties file to be filled in for SSC communication
Avoid Trouble:
Linux admins may want to install the RPMs directly using the rpm -ivh command. This will
NOT work. The console.properties file has to be filled out and shell script invoked for
installation

VMGR LB
VMGR LB
VMGR LB
IP
S
P
R
A
Y
E
R
CF + PR
VMGR
VMGR
VMGR
VMCU farm
VMCU farm
VMCU farm
VMGR LB/sprayer name updated in
stavconfig.xml. This is updated from
Admin pages/SSC GA. Plan creation
order matters
Each VMGR LB routes to other
VNGRs based on load
VMGR figures out
Which VMCU to route
to

Prerequisites – Before you begin
Install

VMCU hardware requirements
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?
deliverableId=1351634674358&duComponent=Server_E7EE9E00FECA11E2ABB41FF3CA6B1291

Prerequisites for installation
■ Java > 1.6
■ Plan created and ready in SSC.
■ Third party RPMs (coming up in the following slides) installed. http://www-
01.ibm.com/support/docview.wss?rs=0&context=SSCKJBV&uid=swg21649532&loc=en_US&cs=utf-
8&lang=
■ Root-only installation
■ / partition should have enough disk space. Cannot install on any other partition or split it across
multiples. Mounted drives may also have unexpected installation issues.

Other handy links to browse prior to beginning
installation..
■ http://www-01.ibm.com/support/docview.wss?uid=swg27007792 → OFFICIAL
system requirements
■ http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?
lookupName=Administering+Sametime+9.0+documentation#action=openDocum
ent&content=catcontent&ct=prodDoc --> Installation/Administration home page
■ http://www-01.ibm.com/support/search.wss?
&tc=SSCKJBV&atrn1=SWVersion&atrv1=9.0 → Technotes for ST 9 installation.
MUST READ BEFORE PROCEEDING WITH INSTALL

Video MCU pre-reqs for RHEL 5
Download and install the following 3rd party RPMs in the order below if not
previously installed:
■ — glibc-2.5-*.el5_9.5.x86_64.rpm
■ — glibc-2.5-*.el5_9.5.i386.rpm
■ — glibc-common-2.5-*.el5.x86_64.rpm
■ — zlib-1.2.3-*.el5.x86_64.rpm
■ — zlib-1.2.3-*.el5.i386.rpm
■ — libgcc-4.1.2-*.el5.i386.rpm
■ — libgcc-4.1.2-*.el5.x86_64.rpm
■ — libstdc++-4.1.2-*.el5.i386.rpm
■ — libstdc++-4.1.2-*.el5.x86_64.rpm
■ — libxml2-2.6.26-2.1.*.el5_9.2.i386.rpm
■ — libxml2-2.6.26-2.1.*.el5_9.2.x86_64.rpm
■ — openssl-0.9.8e-*.el5_9.1.x86_64.rpm
■ — openssl-0.9.8e-*.el5_9.1.i386.rpm
■ — mailcap-2.1.23-*.fc6.rpm
Depending on the specific environment, other 3rd party RPMs may be needed.
Any minor release versions is the 3rd party dependencies are supported, but more recent major
release versions are not supported.

Sametime Video MCU prereqs on RHEL 6
Download and install the following 3rd party RPMs in the order below if not
previously installed:
■ — glibc-2.12-1.*.el6.x86_64.rpm
■ — glibc-2.12-1.*.el6.i686.rpm
■ — glibc-common-2.12-1.*.el6.x86_64.rpm
■ — zlib-1.2.3-*.el6.x86_64.rpm
■ — zlib-1.2.3-*.el6.i686.rpm
■ — libgcc-4.4.7-*.el6.i686.rpm
■ — libgcc-4.4.7-*.el6.x86_64.rpm
■ — libstdc++-4.4.7-*.el6.i686.rpm
■ — libstdc++-4.4.7-*.el6.x86_64.rpm
■ — libxml2-2.7.6-*.el6_4.1.i686.rpm
■ — libxml2-2.7.6-*.el6_4.1.x86_64.rpm
■ — openssl098e-0.9.8e-*.el6_2.2.x86_64.rpm
■ — openssl098e-0.9.8e-*.el6_2.2.i686.rpm
■ — mailcap-2.1.31-*.el6.noarch
■ — compat-expat1-1.95.8-8.el6.i686.rpm

Other RHEL 6 RPMs...
■ The previous slides are from Polycom's official documentation. We've found it
works for most machines. But there are some cases when the VMCU still
doesn't function right after everything's installed.
■ One of our support people found these are also needed:
─ openldap-2.4.23-32.el6_4.1.i686
─ cyrus-sasl-lib-2.1.23-13.el6_3.1.i686

Sametime Video MCU prereqs on SLES 11
■ Download and install the following 3rd party RPMs in the order below if not
■ previously installed:
■ — glibc-2.11.3-17.31.*.x86_64.rpm
■ — glibc-32bit-2.11.3-17.31.*.x86_64.rpm
■ — zlib-32bit-1.2.3-106.*.x86_64.rpm
■ — zlib-1.2.3-106.*.x86_64.rpm
■ — libgcc46-32bit-4.6.1_20110701-0.13.*.x86_64.rpm
■ — libgcc46-4.6.1_20110701-0.13.*.x86_64.rpm
■ — libstdc++46-32bit-4.6.1_20110701-0.13.*.x86_64.rpm
■ — libstdc++46-4.6.1_20110701-0.13.*.x86_64.rpm
■ — libxml2-32bit-2.7.6-0.13.*.x86_64.rpm
■ — libxml2-2.7.6-0.13.*.x86_64.rpm
■ — libopenssl0_9_8-0.9.8j-0.26.*.x86_64.rpm
■ — libopenssl0_9_8-32bit-0.9.8j-0.26.*.x86_64.rpm
■ — aaa_base-11-6.65.*.rpm
Depending on the specific environment, other 3rd party RPMs may be needed.
Any minor release versions is the 3rd party dependencies are supported, but more recent major
release versions are not supported.

Technotes related to pre-requisite RPMs needed for
VMCU
■ http://www-01.ibm.com/support/docview.wss?
rs=0&context=SSCKJBV&uid=swg21649532&loc=en_US&cs=utf-8&lang=
AVOID TROUBLE!
MOST LIKELY SUPPORT SITUATION. ALWAYS, ALWAYS DOUBLE CHECK PREREQs and MAKE SURE THEY ARE INSTALLED.

Installation, best practices, tips n'
tricks

Deployment – Installing Video MCU
■ Download e-Image zip file or ISO
■ Fill out console.properties file
■ Install pre-requisites for the Video MCU.
■ Chmod 777 for all the shell scripts
■ Run the platform specific shell script
•On RHEL 6 and SLES11, there are no RPM built-in checks for
dependencies. Getting pre-requisites correctly installed is a MUST.

VMCU Install details
■ Installation location is /opt/IBM/Sametime/STVideoMCU. THIS IS FIXED.
■ The main installation log is located inside
/opt/IBM/Sametime/STVideoMCU/logs
■ SSC ConsoleUtility log is also located in here.
■ VMCU is a WITH SSC install. No support for post-registration with SSC.

VMCU – Best Practices
■ Need to make sure that both the soft_mcu service and the REST API are up.
■ REST API uses apache httpd
■ The VMCU files are primarily located at:
─ /mcms
─ /opt/apache
─ /tmp
■ Need to clean up all the above directories to clean up a “dirty” machine.
■ The VMCU uses the /tmp directory at runtime.
■ There is a mix of 32-bit and 64-bit RPMs in the dependency list. Please note the dependencies list
carefully
■ When installing via yAST or yum, each pre-req RPM installs a series of dependencies that it needs.
Order matters!
■ MCU install is root-only.
■ Partitioned systems will have issues installing. A single partition with enough space is needed for the
VMCU.
■ Multi-IP machines are not supported for the VMCU.
■ /tmp is a system directory. When recreating /tmp, need to make sure the permissions are set to 1777
for the folder. Set permissions using:
chmod 1777 /tmp
Restart VMCU service

Video MCU Ports
■ Make sure these ports are not blocked by any firewall
Port/Range Usage
443 https/XML API to DMA
8080 http/XML API to DMA
4443 https/REST
5060 SIP / UDP or TCP
5061 SIP / TLS
3478 STUN/TURN
40000-49999 RTP /UDP or TCP

Validating a VMCU installation

Validating a VMCU install
■ Installation should complete successfully. Log should not show errors or failures. Start with the main
installation log and check the /tmp/startup_logs/InstallValidator.log as well.
■ Server should be running. Check by:
─ service soft_mcu status
• Perform a video call to the MCU – this is the ultimate test
• Verify that there are no core dumps:
ls –lrt /output/core
• Verify by netstat command that the following ports are in use:
■ Verify that the following ports are not blocked by the firewall:
Port/RangeUsage
443https/XML API to DMA
8080http/XML API to DMA
4443https/REST
5060SIP / UDP or TCP
5061SIP / TLS
3478STUN/TURN
40000-49999RTP/UDP or TCP

Validation of VMCU install (contd..)
■ Be able to see the VMCU in the SSC admin pages
■ Add the VMCU to the DMA via the SSC admin pages

How to uninstall and clean up..
■ To uninstall the VMCU, cd into /opt/IBM/Sametime/STVideoMCU
■ Run uninstallvideomcu.sh script
■ This will uninstall the VMCU and also update status in SSC
■ Using rpm -e to forcibly remove all RPMs will have same effect but may leave
vestiges of the VMCU on the file system. Better to run the script to make sure we
have prereq checking/enforcement.
■ For clean-up, refer to Slide 34 for more information.

Cleaning up a partial install or a failed install..
STEPS to follow to clean up partial install:
1. Cd into /opt/IBM/Sametime/STVideoMCU directory
2. If file contents are present in here, then run uninstallvideomcu.sh
3. If nothing is present in this directory, you will have to clean up manually.
4. Run rpm -e `rpm -qa|grep ibm-sametime` - This will remove all RPMs starting
with ibm-sametime
5. Run rpm -e `rpm -qa|grep Sametime` - This will remove the Sametime-
VideoMCU-Installer RPM
6. Delete /opt/IBM/Sametime/STVideoMCU directory
7. Delete contents of tmp. WARNING: If there are multiple pieces of software
running and using /tmp, then this has to be done very carefully.
8. If the /tmp directory itself is deleted, then recreate with 1777 permissions
9. Finally, run the installvideomcu_XXXX.sh script again.

VMCU Troubleshooting
Collecting logs

VMCU log locations..
Location Description
/opt/IBM/Sametime/STVideoMCU/logs/ Main install log file location + SSC
related log files. Start here always
when doing debug.
/tmp/startup_logs/ Next place to look to debug install
issues. Contains server startup logs,
install validation logs etc..
/mcms/LogFiles/ VMCU runtime logs in zipped up format.
Files are not readable directly despite
.txt extension. Place to look for runtime
VMCU issues.

Collecting logs
The following instructions enable you to launch the Log Collector script:
To start the Log Collector component:
1) Ensure that the soft_mcu service is running by typing the following command:
service soft_mcu start
The “soft_mcu is already running” message appears when the service is already
operational.
The script accepts one parameter.
2) Run the following script with one of the parameters in Table 3-3, "Script Parameter"
below:
/mcms/Scripts/LogCollector.sh
For example, to collect logs for the previous two hours, type /mcms/Scripts/
LogCollector.sh -2h
Switch Description
h Displays explanations of the available parameters
m The time duration for log collection in minutes. This
must be proceeded by a positive integer.
h The time duration for log collection in hours. This
d The time duration for log collection in days. This

Collecting logs (contd)
■ When the Log Collector is running, dots are displayed every 10 seconds on the Shell.
■ When the Log Collector is completed, a .tgz file is created in the folder /mcms/LogFiles.
■ Inside the .tgz file are the following files if they exist:
— MCMS/CS/AMP/VMP/Startup logs
— Core dumps
— TCP dumps
— Configuration files
■ To log network traffic, enter the following commands:
■ tcpdump -i eth0 -s0 -w tcpdump_eth0.cap
■ tcpdump -i lo -s0 -w tcpdump_lo.cap
■ Sniffer files are located in the folder /output/tcp_dump.
■ Press the CTRL+C keys to stop logging network traffic. This action deletes all of the
temporary files.
■ To retrieve the file, you can use a file transfer software such as WinSCP.

VMCU troubleshooting
Common problems, Tips and tricks..

Troubleshooting – general steps..
■ Check memory/hardware requirements
■ Check if server is up:
─ service soft_mcu status
─ The result should be that the server is running. If not,there's a problem.
■ Check if all RPMs are installed by typing in the following:
─ rpm -qa | grep ibm-sametime → 14 RPMs
─ rpm -qa| grep Sametime-VideoMCU → 1 RPM
■ Check the InstallValidator.log under /tmp/startup_logs and search for “FAIL”. Typically, this points
to the issue.If dependencies are missing, install missing dependencies. 9/10 times this is the
problem.
■ Check for partitions or multiple-IPs on the system
■ Check the core dump area for memory related errors
■ Check /tmp/startup_logs for information on startup problems

Most common problems with VMCU installation..
■ Prerequisite RPMS not installed correctly. Some are missing. 90% of the times this is the issue
■ Hardware requirements are not met.
■ Unsupported OS (SLES 12) was used. This manifests in weird issues with SSC communication.
■ Non-root installation
■ Installation on a partition without enough disk space.

/tmp directory contents were deleted while VMCU was
running
PROBLEM:
■ While VMCU is running, /tmp directory contents got deleted.
■ VMCU goes into a bad state. REST API may not work properly
SOLUTION:
■ Stop the VMCU – service soft_mcu stop
■ Clear out /tmp again
■ Start the VMCU. Will mostly fix this. - service soft_mcu start
■ Worst case, restart the Linux OS
■ Things should start working after restarting the soft_mcu service.

Recreating /tmp still doesn't work. Argh!
PROBLEM:
/tmp directory was deleted and recreated. VMCU doesn't start up after this.
SOLUTION:
/tmp is a system directory. When recreating /tmp, need to make sure the
permissions are set to 1777 for the folder. Set permissions using:
Chmod 1777 /tmp
Restart VMCU service.

Sametime Media Manager – Video
Manager Installation

Big Changes in Sametime 9.0
■ WebSphere Application Server – Network Deployment should be installed separately. It is not bundled
with Sametime Installers
■ It is important to install WAS – Network Deployment not Liberty Core or any other edition.
■ DB2 Server is not packaged with Sametime anymore.
■ Installation Manager version 1.6.2 should be installed first.
■ Instructions here: - http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?
lookupName=Administering+Sametime+9.0+documentation#action=openDocument&res_title=Installing
_Installation_Manager_st9&content=pdcontent
■ WebSphere Application Server should be installed along with all the ifixes.
■ Instructions here :- http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?
_WebSphere_Network_Deployment_st9&content=pdcontent
■ DB2 should be installed by following these instructions :-
■ http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?
_DB2_on_AIX_Linux_or_Windows_st9&content=pdcontent

Sametime Media Manager - Components
■ Proxy Registrar
■ Conference Focus
■ Sametime Video Manager - New
■ Sametime Video MCU – New
■ Packet Switcher is Removed

Installing Sametime Video Manager - Overview
■ Sametime Video Manager – installs VMGR, solid DB and load balancer.
■ Solid DB – Relational , in- memory database.
■ It is a standalone Node – No federation.
■ VMGR and Load Balancer are WebSphere Applications.
■ Solid DB is installed at /opt/solidDB/soliddb-7.0.
■ Ports used are : 5060 / 5061, 8443 , 9043 , 7443, 7445, 5080/5081
■ VMGR does not use WebSphere SIP Container .

Installing Sametime Video Manager - Preparation
■ Needs a dedicated machine.
■ 8 core, 8 GB
■ For detailed requirements :- http://www-01.ibm.com/support/docview.wss?uid=swg27007792
■ Needs 'root' access.
■ Machine with mutiple IP address may not work as expected

Tip #1: All plans should be created beforehand
■ There is a complex interdependency between the media manager components. So it is very
important to have all the plans ready before starting installation.
■ Failing to do so may result in incomplete installation. Post install tasks will fail and additional manual
steps may be needed to fix the problem.

Tip #2: Order of plan creation is very important
The plans should be strictly created in a particular order.
Type 1 : PR and CF installed separately,
1.Create PR plan
2.Create VMGR plan
3.Create CF plan
4.Install PR
5.Install VMGR
6.Install CF
Type 2 : PR CF installed together ,
1.Create VMGR plan
2.Create PRCF plan
3.Install VMGR
4.Install PRCF

Installing Sametime Video Manager – Post Install Tasks
Overview
■ At the end of VMGR install, three post install tasks are done. Each task communicates with SSC
and gets the required details.
■ 1. Create a default Conference template
■ 2. Add SIP Peer
■ 3. Create a new User
Sametime
System
Console
Sametime VMGR
installing.....
Installer makes a call to SSC
SSC responds by sending installer requested details

Tip #3 Before installing Sametime Video Manager,
disable requiretty
■ To disable in RHEL :-
■ Run sudo /usr/sbin/visudo
■ Go to insert mode
■ Change Defaults requiretty to Defaults !requiretty
■ Save and close the file.
■ To disable it in SLES11 SP2 :-
■ Please just append Defaults !requiretty in this file and save it.

Installing Sametime Video Manager - Preparation
■ Failing to follow Tips #1-3 will result in post install failure. The installation will complete with a warning
saying “Exception thrown when trying to register the Sametime Media Server with Sametime System
Console Server. Please register the server with Sametime System console by running the
registerproduct.sh utility ”
■ Workaround:- Run registerproduct.bat/sh utility to complete the set up.
■ Instructions here :- http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?
lookupName=Administering+Sametime+9.0+documentation#action=openDocument&res_title=Regist
ering_a_new_Sametime_Video_Manager_with_the_Sametime_System_Console_st9&content=pdco
ntent

Tip #4 Order in which server would be stopped and started in
Sametime VMGR
Stopping the Server:-
1. STMediaServer
2. Solid DB
Instructions to stop Solid DB :- http://pic.dhe.ibm.com/infocenter/soliddb/v7r0/index.jsp?topic=
%2Fcom.ibm.swg.im.soliddb.gettingstarted.doc%2Fdoc%2Fs0000027_stoppingDB.html
Starting the Server:-
1. Solid DB
To start Solid DB :-
/opt/solidDB/soliddb-7.0/bin> solid -c /opt/solidDB/soliddb-7.0/eval_kit/standalone/
2. STMediaServer
For command ref. See link:-
http://www-10.lotus.com/ldd/stwiki.nsf/xpDocViewer.xsp?lookupName=Administering Sametime
9.0
documentation#action=openDocument&res_title=Starting_and_stopping_the_Sametime_Video_Ma
nager_st9&content=pdcontent

Installing Sametime Video Manager – Uninstallation
V. Uninstalling Sametime Video Manager
1.Stop the server (solid DB and Media Server) before uninstalling.
2.After Uninstallation :- Make sure that solid DB is uninstalled properly. Solid DB is always located at
/opt/solidDB/soliddb-7.0/

Installing Sametime Video Manager – Collecting Logs
■ Like any other server , run collect logs utility to collect all necessary logs.
■ To run collect logs utility, go to product install location – for eg: For vmgr,
/opt/IBM/WebSphere/MediaServerVMGRPN/collectlogs/
■ Run collectlogs.sh
■ Send the resulting zip file from /tmp/SametimeInstallLogs.zip
■ For VMGR, additionally solid DB logs are also needed.
■ Thet solid DB logs needed are :-
■ /opt/solidDB/soliddb-7.0/eval_kit/standalone/solmsg.out
■ /opt/solidDB/soliddb-7.0/eval_kit/standalone/logs
■ /opt/solidDB/soliddb-7.0/logs

Sametime 9 Community Server,
Gateway and Client Installs

© 2014 IBM Corporation51
Overview of changes in Sametime 9 around installation of Sametime
Community Server, Sametime Gateway Server and Sametime client
components
 Community Server install & upgrade
– Classic Meetings removed
– Option to Install without SSC available but not supported
– Incremental hot fix installer removed
– Network client installation now requires an external HTTP server, e.g. Apache Tomcat
– Entry server now renamed as Limited Use Edition
– An upgrade of a Limited Use (Entry) server to Standard server is supported; reverse not supported
– Muti-tenancy solution introduced (binaries and configuration files installed under <domino binaries
directory> on Windows and under <domino data directory> on UNIX platforms
 Gateway Server install & upgrade
– WebSphere Application Server is no more installed during Gateway installation
– Manual JMS configuration required post Gateway installation (scripts included in installable)
– No in-place upgrade available to upgrade older v8.5.x Gateway servers to v9.0
 Client install & upgrade
– Sametime Embedded Add-on v9.0 shipped along with Notes 9.0.x client

Sametime 9 system requirements
http://www-01.ibm.com/support/docview.wss?uid=swg27007792
 OS platform support (support for some older platforms, e.g. Solaris, dropped; support for some newer
advanced OS platforms added, e.g. Ubuntu 12.04 LTS x86_32)
 Middleware software prerequisites (Domino 9.0 32 bit is supported for Community Server 9.x,
WebSphere Application Server 8.5.5.x is supported for Gateway Server 9.0)
 Language support (Support for Thai and Catalan languages has been added to client installation)

OS libraries required for installing Sametime Community/Gateway
servers in GUI mode on RHEL 6.x 64-bit
64 bit versions of following packages are required on 64bit RHEL
6.x platform
compat-libstdc++-33-3.2.3-69
compat-db-4.6.21-15
libXp-1.0.0-15.1
libXmu-1.0.5-1
libXtst-1.0.99.2-3
libXft-2.1.13-4.1
pam-1.1.1-4
gtk2-2.18.9-4
gtk2-engines-2.18.4-5
rpm-build-4.8.0-12
elfutils-0.148-1
elfutils-libs-0.148-1
ksh-20100621-2
Additionally, the 32-bit versions of the following packages are also
required on 64 bit RHEL 6.x platform:
compat-libstdc++-33-3.2.3-69
compat-db-4.6.21-15
libXp-1.0.0-15.1
libXmu-1.0.5-1
libXtst-1.0.99.2-3
libXft-2.1.13-4.1
pam-1.1.1-4
gtk2-2.18.9-4
gtk2-engines-2.18.4-5
glibc-2.12-1.7
libgcc-4.4.4-13
libstdc++-4.4.4-13
libXi-1.3-3
Apart from these following libraries are required on ANY Linux
platform:
libstdc++.so.5
libstdc++-libc6.1-1.so.2 is

OS libraries required for installing Sametime Community/Gateway
servers in GUI mode on SLES 11 SP2 64-bit
■ libgcc43-32bit-4.3.4_20091019-0.7.35.x86_64.rpm
■ libstdc++43-32bit-4.3.4_20091019-0.7.35.x86_64.rpm
■ Libstdc++33-3.3.3-11.9
■ libstdc++33-32bit-3.3.3-11.9
■ Libstdc++43-4.3.4_20091019-0.7.35
■ libstdc++43-32bit-4.3.4_20091019-0.7.35
■ libstdc++43-devel-4.3.4_20091019-0.7.35
■ libstdc++-devel-4.3-62.198
Apart from these SLES specific packages, libstdc++-libc6.1-1.so.2 library is also required on all Linux platforms
Above mentioned RPM files could be found on x86_64 CD/DVD image of SLES 11.x at
/mnt/suse/x86_64/

Known issues around installation & upgrade of
Sametime Community server / Mux & Sametime
Gateway server (Technotes available)
 Upgrading the Sametime Community server from 8.5.2 to 9.0, get error
message Exception in thread "Thread-4" on Domino console.
 Anonymous login by token feature does not work in Sametime®
Community Server v9.0 on AIX or Linux.
 IBM Sametime Community Mux v9.0 installer does not upgrade an existing
installation of v8.5.x Community Mux on the same computer
 Unable to add local community to Sametime Gateway using Deployment
Manager

Sametime clients (Technotes available)
 Failure in upgrading IBM® Sametime® Connect client v8.0.2 to v9.0
 JVM error during Sametime 9 Connect client installation on Mac OS X 10.9
 Upgrading Sametime Connect Client v8.5.x to v9.0 succeeds on Ubuntu
Linux 10.04 LTS (32 bit) but subsequent upgrade to v9.0 HF1 fails (TN #
1664287 ...yet to be published)
 Sametime Contacts panel does not appear in IBM® Notes® 9.0 client

Sametime Office Integration (Technotes available)
 Upgrading Sametime Connect 8.5.2 / IFR1 to v9.0 fails on Windows with
Sametime Office Integration 8.5.2 / IFR1 installed
 Upgrading Sametime Connect 9.0 GOLD to v9.0 HF1 fails on Windows
with optional Office Integration features enabled into target 9.0 GOLD
client (TN# 1658061 ...yet to be published)
 Upgrading Sametime Outlook Integration v8.5.2 or v8.5.2 IFR1 to v9.0 fails
 Sametime Office Integration add-ins become inactive after repairing a
corrupt installation of Sametime Office Integration 9.0

Other known issues (To be documented as
Technotes)
 GUI mode install for Sametime Community / Gateway server doesn't work
due to missing OS libs (both 32 bit and 64 bit versions of them) on
advanced Linux platforms (e.g. RHEL 6.x x86_64)
 CS LU 8.5.x/9.0 to CS 9.0 HF1 upgrade turns existing Limited Use server
to Standard edition
 2 doc icons appear for Sametime Connect client on OS X 10.9

Common install / upgrade issues faced with older versions of Sametime
 Security pop ups when ST connect client connects to ST advanced or meeting server over
SSL
 Customizations of client installer kit; e.g. combining GOLD and hot fix install kits, replacing
default version of Embedded ST Add-on in Notes install kit with an other desired one,
integrating third party plugins with client install kit, adding custom preferences to
plugin_customization.ini, using non-default JVM for client install etc.
 Installing ST client in Citrix environment with system account, installing ST client on remote
machines from central location using enterprise push tools such as Altiris
 Notes client fails to launch after upgrade (unavailability of XCOPY command causing OI base
feature configuration to fail during install/upgrade).

Open Mic on Sametime9 Install -Best Practices

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à Open Mic on Sametime9 Install -Best Practices

Similaire à Open Mic on Sametime9 Install -Best Practices (20)

Plus de Vinayak Tavargeri

Plus de Vinayak Tavargeri (7)

Dernier

Dernier (20)

Open Mic on Sametime9 Install -Best Practices