Cisco TelePresence Management Suite Provisioning Extension Why upgrade to Cisco TMSPE? White Paper August 01 This document was written and prepared by Dale Ritchie in Cisco s Collaboration Infrastructure Business Unit (CIBU), Oslo, Norway. Contents Cisco TMS Agent Legacy a brief background... 1 Cisco TMS Agent Legacy the challenges... Cisco TMSPE the answer... 3 Cisco TMSPE the features... 3 Cisco TMSPE the big picture... 4 Product documentation... 4 Conclusion... 4 Document revision history... 4 Cisco TMS Agent Legacy a brief background As shown in the graphic below, the Cisco TMS Agent Legacy model utilized a full mesh, multi-master replication model using OpenDS as its LDAP database. The Cisco TMS Agent application along with its OpenDS database was installed to both Cisco TMS (local TMS Agent) and the Cisco VCS or VCSs (remote TMS Agent). Cisco TMS <=13. Core TMS TMS Agent OpenDS full-mesh, multi-master replication VCS X7.x TMSAgent VCS X7.x TMSAgent Cluster Replication D14969.0 Page 1 of 5
Bi-directional Connections Cisco TMS Agent Legacy the challenges But what does fully meshed, multi-master replication model really mean? To best illustrate this, see the slides below, where as you add more replicating nodes, in particular as you scale in this model, the number of connections that are required to take place between those nodes increases. : +1 = 1 8 1 7 3: + = 3 4: +3 = 6 5: +4 = 10 3 4 5 6 6: +5 = 15 7: +6 = 1 8: +7 = 8 9: +8 = 36 10:+9 = 45 Connections= N ( N -1 ) 1400 100 1000 Connection s N N 800 600 400 00 0 0 10 0 30 40 50 Nodes Cisco TMS Agent Legacy the challenges As discussed above, Cisco TMS Agent Legacy was severely challenged when it came to scaling as well as becoming unstable and unpredictable in large networks. For example, some of the reasons for this instability were: Total number of replicating nodes. High latency or instability in the network between replicating nodes. OpenDS replication collisions which would create memory stress on the replicating nodes, in some cases requiring a restart of the OpenDS on some or all the replicating nodes, Cisco TMS or Cisco VCS. Re-indexing of the OpenDS database on the replicating nodes, which could also cause memory stress on the replicating nodes and in some cases require restarting OpenDS on some or all the replicating nodes. Properly identifying and diagnosing problematic replicating nodes. Another challenge was that Cisco TMS Agent Legacy was embedded in the Cisco TMS core application, which meant that any problems with the agent on Cisco TMS would also disrupt regular Cisco TMS services, and Cisco VCS services when Cisco VCS servers were affected. We have also identified a Java vulnerability on Cisco VCS when running Cisco TMS Agent Legacy mode. Switching to TMS Provisioning Extension mode turns off the old TMS Agent Legacy mode and deactivates Java Virtual Machine on the VCS, thus removing the vulnerability. The bug toolkit identifier for this issue is CSCtu1769. TMS Agent Legacy mode will be completely removed from Cisco VCS in version X8.0 software. In preparation for this upgrade, we strongly recommend installing Cisco TMSPE. Cisco TMSPE White Paper Page of 5
Cisco TMSPE the answer Cisco TMSPE the answer As shown on the slide below, and compared to the Cisco TMS Agent Legacy model, the architecture of the solution was completely redesigned for Cisco TMSPE. Note in particular the numbers of connections as compared to nodes: 3 Cluster of 6 Nodes IPSec Cluster DB Replication 4 Nodes Status Quo: 76 Connections New Method: 64 Connections 4 5 6 1 HTTPS REST JSON API 13 18 17 16 15 14 1 11109 8 7 HTTPS REST JSON API 19 4 3 1 0 Looking at the scaling comparison between the two models when it comes to bi-directional connections and nodes, Cisco TMSPE clearly reduces this challenge as well: Cisco TMSPE the features Cisco TelePresence Management Suite Provisioning Extension 1.0 is an add-on replacement application for the Cisco TMS Agent Legacy on the Cisco TMS server with the following main features: Independent installer (only installed to the Cisco TMS server). SQL database on Cisco TMS server is the single configuration source for replication. Migration tool for Cisco TMS Agent Legacy to Cisco TMSPE (moving from OpenDS to SQL). Cisco VCS pulls data from Cisco TMSPE using APIs. Auto created phone book includes all provisioning users. Tailored phone books based on groups and subgroups of provisioning user can be created as desired. Cisco TMSPE White Paper Page 3 of 5
Cisco TMSPE the big picture Any phone book/corporate directory from Cisco TMS can be provisioned to any supported device. Import users from Microsoft & generic LDAP sources (AD, LDAP, LDAPS). User personalization and administrative device configuration control for devices supporting Cisco TMSPE (such as Jabber Video (Movi), E0, EX60, EX90, MX00, MX300). Cisco TMSPE Diagnostics health checks are run at regular intervals and can also be performed on demand. End-user FindMe portal on Cisco TMS using Microsoft Active Directory login, instead of Cisco VCS web UI. Increase scale from 10,000 to 100,000 users and devices. Cisco TMSPE the big picture The slide below depicts an overall view of the Cisco TMSPE model: Cisco TMS 13.+ Core TMS Cisco TMSPE HTTP(S) HTTP(S) REST API Cisco VCS X7.1+ Cluster DB Erlang Cisco VCS X7.1+ Cluster DB Erlang Cluster Replication IPSec Product documentation The following documents can be found on our website and provide guidance on installation, initial configuration and operation of the product: Cisco Telepresence Management Suite Provisioning Extension Software Release Notes Cisco Telepresence Management Suite Provisioning Extension Deployment Guide Cisco Telepresence FindMe User Guide Conclusion Learning from the Legacy TMS Agent challenges, Cisco TMSPE becomes the next generation product in architecture, stability and scale when it comes to the large scale provisioning of users and endpoints through the Cisco Telepresence Video Communication Server (Cisco VCS). Document revision history Date Revision Description 01-06-0 01 Initial version. 01-08-08 0 Added information about Cisco VCS vulnerability in Legacy mode. (ID CSCtu1769) Cisco TMSPE White Paper Page 4 of 5
Document revision history THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. 01 Cisco Systems, Inc. All rights reserved. Cisco TMSPE White Paper Page 5 of 5