IBM Sametime & Best Practices for Deployment

Transcription

1 IBM Sametime & Best Practices for Deployment Pat Galvin STSM, IBM Unified Communications & Collaboration Binh Nguyen STSM, IBM Unified Communications & Collaboration November 2011

2 Agenda IBM Sametime Review Audio / Video features Sametime Advanced Capacity Planning Approach & Basic Metrics Deploying for High-Availability Clustering & Failover Disaster Recovery Multi-site deployment Deploying for Audio/Video Firewall traversal

3 Sametime Key Themes Web browser meetings improvements to extend access and reach Audio video management tools to help accelerate adoption Mobile access - new devices and capabilities New options to simplify SUT deployment Sametime GA on 1 June 2011! 3

4 Audio and video in the Web meetings client Browser plug-in installs on demand or pre-installed; also supports 3rd party video integration Call and video controls List of participants shows connection, presence and muted status. Call Controls: - Connect/disconnect - Adjust Volume - Hold/Resume Moderator Controls: - Mute/unmute all - Mute another person - Lock call - End call for everyone - Hang up participant Video Controls: - Show/ hide own video - Hold/resume - Pause/resume 4

5 Audio/Video in Browsers: Native Softphone Web softphone is only a few Mbs in size. approx 2.7 Mb(download) 6Mb(uncompressed) Web UI (JSP/HTML/JavaScript/DOJO) Browser Plugins Webplayer It can be easily downloaded via an update site provided in server configuration. Media Plug-in Manager Native Softphone The softphone version is stored in plugins.ini file and is maintained by the Plug-in Manager component. SIP/SIPS TLS STUN/TURN (ICE SDK) Video Engine RTP/SRTP RTCP Transport: TCP/UDP 5

6 A richer Web meetings experience Click to return to the meeting room center Meetings open in a new tab or window Jump forward or backwards in the slide deck Create and send polls Pointer and highlighters 6

7 Improved controls and management tools Manage access to meeting rooms Prevent entry ahead of room owner or manager Eject users End meeting session for all Delete rooms from the server A tool for administrators Delete rooms from the server Click to end the meeting 7

8 Sametime Bandwidth Manager Protects network by restricting bandwidth used for Sametime audio/video Manages calls to available bandwidth at each location Uses bandwidth policies based on classes of users Ted VP (US) Amadou (France) Gail VP (China) Raphael (Brazil) 8

9 Bandwidth Management Endpoint A 1 4 SIP Proxy Endpoint B Call control INVITE sip:b From: sip: A@domain To: sip:b@domain Contact: sip:<ip A> payload SDP 2 3 Bandwidth Mgr INVITE sip:b From: sip: A@domain To: sip:b@domain Contact: sip:<ip BWM> payload SDP - modified Accept, reject, modify video bandwidth based on policies Centrally manage, provision, and monitor 9

10 Support for Dual Audio/Video Adapters Simultaneously connect Sametime to a 3rd-party audio and video system Users select appropriate service for each call or conference Administrators manage access to each service via policies Voice Audio Bridge Connector Sametime Media Manager Voice and Video Video Conferencing Connector 10

11 Sametime mobile client for Android Presence and IM Send images over IM SUT Dialer Place calls from your mobile phone via SUT Calls back to device to avoid outgoing mobile charges Use the preferred number and device to avoid mobile charges Change preferred SUT device directly from the Android phone 11

12 Sametime meetings client for Blackberry devices 12

13 Sametime SUT Lite Client Community Server Sametime Proxy\Registrar vp sip Sametime Client sip 3rd Party PBX sip Phones 13

14 Sametime SUT Lite Client A separate entitlement from ST Standard Use Sametime rich client for making and receiving audio/video calls Uses Sametime SIP Trunking Does not require SUT TAS or TCS More limited functionality than full SUT Soft phone only No conferencing, device management, call-routing, mobile... Upgradable to full SUT Certified with specific partners Cisco, Avaya are 1st candidates 14

15 Sametime Advanced New release of Sametime Advanced Chat room LDAP group ACL's Improved scalability for alerting/ broadcasts Server side MQTT replaces Event Broker Compliance logging API's Capture chat room activity Partnering with Actiance, Permessa, Instant Technologies and others Sametime System Console support for deployment/management Consistent platform support with Sametime Standard New: group support for chat room access Support for latest server OS platforms WAS 7.x and DB2 9.5/9.7 support 15

16 Agenda Sametime Review Audio / Video features Sametime Advanced Capacity Planning Approach & Basic Metrics Deploying for High-Availability Clustering & Failover Disaster Recovery Multi-site deployment Deploying for Audio/Video Firewall traversal

17 Capacity Planning What compute resource (CPU & RAM) will be needed? The process is based on an operational model: How many users? What is peak concurrency rate? Eg, 50k users, peak rate of 75%, we size for 37.5k active users. Different services have different concurrencies. Chat usually is highest 50% or more. Meetings is usually ~10%. Look at your calendar the proportion of your scheduled meetings that have web meetings is your meetings concurrency. IBM Techline provides the questionnaire. Accessed by IBM account teams on behalf of customers. 17

18 Capacity Planning Example 70,000 users sizing: Community server: 2 servers of 2 cores (3 GHz), 4 GB RAM each. MUX server: 2 servers of 2 cores (3 GHz), 4 GB RAM each. Meetings: 5 servers of 4 cores (3 GHz), 4 GB RAM each. WebSphere proxy: 2 servers of 4 cores (3 GHz), 4 GB RAM each. DB2 server: 1 server of 8 cores, 16 GB RAM. AV Packet Switcher: 3 servers of 8 cores (3 GHz), 4 GB RAM each. Proxy/Registrar, Conference Focus: 2 servers of 4 cores (3 GHz), 4 GB RAM each. M A X E E L P O Y L N 18

20 Deployment for High Availability Achieve Continuous Service Even if one component fails, users may either not even notice it, or lose service momentarily, but can immediately reconnect and be serviced by a different component, without losing data No down time No Single Point of Failure Scalability Be able to support a large number of users on a single system Fundamental Pattern: Single Entry Point to a Clustered Service Via: Load Balancer IP Sprayer Rotating DNS 20

21 Foundation for High Availability Community Server & Domino Domino clustering & Replication IBM WebSphere components All new components in Sametime 8.5.x are based on WebSphere. LDAP and DB2 in general Use a Load-Balanced entry point for configuration and planning even if you are initially configuring the service against a single host. Virtualization is supported for all components Quickly add new servers based on CPU/RAM equivalents. 21

22 WebSphere High Availability Basics IBM WebSphere All new components in Sametime 8.5.x are based on WebSphere. Node: A HW server where WebSphere code is installed. A node can be a standalone WebSphere deployment. Profile: A runtime configuration on a HW server; multiple profiles can exist on a single HW server. Deployment Manager (DM): Management/configuration application for a multi-node WebSphere deployment. Cell: A set of nodes managed by a DM. Server: An instance of a WebSphere process that handles/processes requests. A single profile may support multiple servers. Cluster: A group of servers, either spanning multiple nodes (horizontal) or on a single node (vertical). 22

23 Sametime System Console 23

24 Sametime System Console Acts as the Deployment Manager for the entire deployment Centralizes WebSphere, Sametime and Policy management Guided Activities to Plan LDAP and DB2 prerequisites Deployments of each product component Clustering of each product component Deployment plans are validated to ensure that the installations are successful Will not let plans proceed if prerequisite conditions are not met Visually see status of deployments and version information Once Clustering Activities are complete Synchronization of all nodes is possible Starting/Stopping/Restarting can be done remotely Visual indicators for cluster and application server status No Run-Time dependency 24

25 DB2 High Availability One method is to use Microsoft Cluster Service (MSCS). MSCS combines 2 nodes into a single virtual IP. All data is stored on a shared disk. When Computer A is unresponsive, MSCS switches traffic to Computer B. Same pattern can be created in Linux/AIX with Tivoli System Automation (TSA). Note: Requires additional DB2 PVUs for this config. 25

27 Deployment for Disaster Recovery Key pattern: Primary / secondary site, data replication The primary site handles all functions in normal operation. Secondary site handles functions when primary has failed or is inaccessible. Replication needed to keep the two in synch. Global Traffic Manager Network component that routes traffic to either primary or secondary. Based on health checks. 27

28 Deployment for Disaster Recovery Primary Site Clients Load Balancer Meetings Node Meetings Node Global Traffic Manager replication Secondary Site Load Balancer Meetings Node Meetings Node 28

29 Full System DR Example ISSL can provide architecture services for HA/DR. 29

31 Sametime Audio-Video Components SIP Proxy/Registrar Conference Manager Packet Switch Bandwidth Manager Meeting Server HTTP VP Community Server VP Bandwidth Manager Sametime Client SIP Proxy / Registrar Conference Manager Media Packet Switch 31

32 How Does Audio/Video Work? SIP Proxy/Registrar 1) Alice and Bob REGISTER their IP addresses with the SIP P/R 2) Alice wants to call Bob. 3) Alice sends an INVITE to the SIP P/R. 4) The SIP P/R knows Bob's address and is able to forward the INVITE to him. SIP INVITE To: From: c=in IP SIP Media/RTP 5) Bob responds with a similarly formatted OK. 6) Alice and Bob exchange media using the exchanged IP addresses. Alice Bob

33 What Happens with NAT? SIP Proxy/Registrar 1) Alice REGISTERs her private IP address, ) When Alice calls Bob, she sends an INVITE just like before: INVITE To: From: c=in IP SIP SIP ) Bob then tries to send media to Alice's PC using the NAT Media/RTP 4) Result: FAILURE. Alice public IP is different from her private IP. Alice Bob

34 Network Address Translation NAT is a technique used (1) To hide private addresses from a public network, and (2) To conserve addresses in the public IPV4 address space. All NAT firewalls work by mapping a private address/port combination to a public address/port combination. Eg., /137 to /137. NAT firewalls differ based on what peers are able to do: Symmetric NAT: Only an external peer that receives a packet from the internal peer can use that address/port. Different requests to the same internal address/port and mapped to different external ports. Most restrictive. Full-cone NAT: All incoming requests to the same private address/port are mapped to the same public address/port. Any external peer can use an address/port mapping. Least restrictive. Restricted NAT: All incoming requests to the same private address/port are mapped to the same public address/port, but only external peers that have received a packet from the internal peer can use that mapping. Medium restrictive. 34

35 Sametime NAT traversal for audio/video Enables audio and video connectivity across firewalls Supports ICE/STUN/TURN standards Corporate Network Public Network DMZ Sametime clients (rich or web)* Sametime Media Manager Internet New:Sametime TURN server Sametime clients (rich or web)* Partner/home Network NAT Router Sametime clients (rich or web)* * Requires updated Sametime clients (rich or web) 35

36 Sametime Audio/Video & Firewalls Sametime and most IP audio/video systems use a common strategy for transporting media across NAT firewalls: Use some intermediate server to determine public addresses. Attempt different combinations of addresses to get best media route. Standards in play are STUN, TURN and ICE: STUN: Session Traversal Utilities for NAT, provides means for clients to discover their public address(es). TURN: Traversal Using Relay NAT, provides a means to relay media between endpoints separated by NATs; usually used when a symmetric NAT is involved. ICE: Interactive Connectivity Establishment, protocol used by clients to determine optimal path to other endpoint. Depending on the number of firewalls and type of NAT Symmetric, Restrictive, etc. these protocols may be able to negotiate P2P media flows. 36

37 Example Scenario One participant behind a NAT firewall. SIP Proxy/Registrar SIP SIP TURN Server Media/RTP Media/RTP NAT Media/RTP?? P2P is possible in some environments. Alice Bob 37

38 Thanks! Sametime wiki: Sametime blog: 38