Cisco WebEx Social Installation and Upgrade Guide, Release 3.4
System Requirements
Downloads: This chapterpdf (PDF - 439.0KB) The complete bookPDF (PDF - 1.72MB) | Feedback

System Requirements

Table Of Contents

System Requirements

Browser Support and Compatibility With Other Components

Installing Plugin for Cisco Web Communicator

Overview of Cisco WebEx Social Nodes and Their Roles

Version Compatibility

Cisco WebEx Social Compute Platform

Platform

Compute

Storage

NFS Requirements and Setup

VMware vSphere Configuration for Cisco WebEx Social

Resource Protection

VMWare Sizing Tables

Disk Growth and Size

Load Balancer Information

Planning


System Requirements


This chapter explains system requirements for Cisco WebEx Social and provides related information.

This chapter includes these topics:

Browser Support and Compatibility With Other Components

Installing Plugin for Cisco Web Communicator

Overview of Cisco WebEx Social Nodes and Their Roles

Version Compatibility

Cisco WebEx Social Compute Platform

NFS Requirements and Setup

VMware vSphere Configuration for Cisco WebEx Social

Resource Protection

Disk Growth and Size

VMWare Sizing Tables

Load Balancer Information

Planning

Browser Support and Compatibility With Other Components

For a list of browsers and other components that are compatible with Cisco WebEx Social, see Cisco WebEx Social Compatibility Guide.

Installing Plugin for Cisco Web Communicator

Each Cisco WebEx Social user must install a plugin to use Cisco Web Communicator.

See the "Installation and Configuration for Cisco Web Communicator" section in Cisco WebEx Social Administration Guide for information on where the plugin can be obtained and how users can install the plugin that they need.

Overview of Cisco WebEx Social Nodes and Their Roles

Table 1-1 provides a brief description of the service that each node in the Cisco WebEx Social environment performs. The service a node performs is often referred to as a role in Cisco WebEx Social.

Table 1-1 Cisco WebEx Social Roles 

Role
Description
Requirements

Analytics Store

A Mongo database that contains information about user preferences for the purpose of providing suggestions for what communities or other aspects of Cisco WebEx Social may interest a particular user. Also used for the email digest notification and metrics features.

Minimum: 1 node.

Maximum: 2 nodes.

Note 2 nodes are recommended to provide for high availability and redundancy.

App Server

The core Cisco WebEx Social web application.

Minimum: One node.

Maximum: No limit.

Cache

A distributed, high-performance, in-memory key/value store. This node is intended to increase the speed of data access. The system tries to fetch data from this node before accessing the database and database access is a slower operation.

Minimum: 1 node.

Maximum: No limit.

Director

Used to set up your Cisco WebEx Social topology and manage various system settings and configuration options.

1 node.

Index Store

An autonomous, special-purpose instance of the Cisco WebEx Social search engine used as a pseudo-cache to offload a class of resource-intensive database queries.

Minimum: 1 node.

Maximum: 1 node.

JSON Store

A MongoDB database that stores various Cisco WebEx Social data. Provides faster access to certain data than using a relational database would allow.

Minimum: 1 node.

Maximum: 2 nodes.

Note 2 nodes are strongly recommended to provide for high availability and redundancy.

Message Queue

A message bus that provides reliable, asynchronous database updates.

Minimum: 1 node.

Maximum: 2 nodes.

Notifier

XMPP publisher for notification of end-user events, including system alerts, announcements, and activities.

Minimum: 1 node.

Maximum: 1 node.

RDBMS Store

Data store for data from the Notifier and App Server.

Minimum: 1 node.

Maximum: 1 node.

Search Store

Cisco-provided search engine for Cisco WebEx Social.

There must be a master/slave setup for the Search Store. You need one virtual machine for the Master node and one for each slave node.

Minimum: 1 Search Store master and 1 Search Store slave.

Maximum: 1 Search Store master and 10 Search Store slaves.

Worker

Improves system performance and user interaction by handling asynchronous and background processing tasks and interacting with various other roles.

Minimum: 1 node (2 for high availability).

Maximum: No limit.



Note You can use a proxy server with your Cisco WebEx Social environment. For more information, see the "Proxy Settings" section in the "Director" chapter in Cisco WebEx Social Administration Guide.


Version Compatibility

Cisco WebEx Social works with many other components, such as Show and Share, Notification, and Presence servers. For list of the versions of other components that Cisco WebEx Social supports, see Cisco WebEx Social Compatibility Guide.

Cisco WebEx Social Compute Platform

This section contains information about what Cisco supports and recommends for the Cisco WebEx Social compute platform:

Platform

Cisco recommends Vblock for Cisco WebEx Social. Deploying Cisco WebEx Social on Vblock is optional.

Compute

Cisco WebEx Social is supported on Cisco Unified Computing System servers.

Storage

Storage requirements and recommendations are as follows:

Storage vendor—Cisco WebEx Social supports the storage systems that are listed in Cisco UCS Storage Interoperability Matrix, which is available at this URL: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/
Matrix8.html

NFSv4 storage required—Cisco WebEx Social requires an NFSv4 export

Storage space recommendation—Allow for at least 500MB of usable space per user when designing a system for 10,000 or more users.

Storage performance recommendation: Allow for at least .1 IOPS per user when designing a system for 10,000 or more users

NFS Requirements and Setup

Cisco WebEx Social requires one NFS Version 4 export/share on the server and three NFS Version 4 mounts on the Cisco WebEx Social client. The NFSv4 export/share are for data store, Message Queue, and Director data backup. Table 1-2 describes these exports/shares.


NoteCisco recommends that you use the ext4 file system on your NFS server. Using the ext3 file system server can limit the number of library documents and post attachments that Cisco WebEx Social can store.

Before you install or upgrade Cisco WebEx Social, make sure that the port mapper service is running on the NFS server and that the port on which the service is running allows access.


Table 1-2 Export/Share on NFS Server 

Export/Share Name
Ownership
Purpose

cms

quad:quad (303:300)

For data store

jms

activemq:quad (301:300)

For Message Queue

backup

quad:quad (303:300)

Topology and cluster metadata from the Director


After NFS is configured in the Director, the following auto-NFS mount points are automatically configured on each Cisco WebEx Social VM:

/mnt/auto/cms (for data store)

/mnt/auto/jms (for Message Queue)

/mnt/auto/backup (for Director backup)

All of these mount points should come from the same NFS server host.


Note "root_squash" on NFS is recommended for these mount points.


Setting up an NFS server requires that you contain the exported NFS file area to a subset of the NFS server file system and prepare for multiple uses of the NFS server. For example, you can contain the area of the file system that is exposed to the outside world through NFS to a top-level directory called /export and subdirectories you create under /export.

Under the /export directory, you can create a webexsocial directory to contain all data for all Cisco WebEx Social instances.

The following procedure shows an example for setting up NFS. This procedure assumes that you are squashing the root.


Note This procedure is for a generic linux system and may not give the exact steps you need to run to achieve the NFS setup described. Refer to the vendor-supplied documentation for your storage system to achieve the same setup described in this section.


Procedure


Step 1 Run this command on the NFS server to create the /export/webexsocial folder on that server:

mkdir -p /export/webexsocial

Step 2 Take these actions on the NFS server:

a. Create subdirectories required by each instance of Cisco WebEx Social under the /export/webexsocial directory:

cd /export/webexsocial/

mkdir cms jms backup

b. After these subdirectories are created, or if they preexist, execute the following commands execute the following commands to change their ownership:

chown -vR 301:300 jms

chown -vR 303:300 cms

chown -vR 303:300 backup

c. If the root is squashed, enter the following commands to grant write permissions to the root user for these subdirectories:

chmod -R 775 /export/webexsocial/cms

chmod -R 775 /export/webexsocial/jms

chmod -R 775 /export/webexsocial/backup

Step 3 On the NFS server, create the NFS server configuration file /etc/exports with this content:

/export/webexsocial *(rw,root_squash,fsid=0,anonuid=99,anongid=99)


Note Only one line is required in the file /etc/exports. This setup will serve one or more Cisco WebEx Social instances.


Step 4 After you have finished writing the /etc/exports file, restart the NFS service by running this command on the NFS server:

service nfs restart

Step 5 (Optional but recommended) Take these actions on the NFS server:

a. Configure /etc/idmapd.conf on NFS to have the same domain name as that of /etc/idmapd.conf on the Director node.

b. After you have finished writing the /etc/idmapd.conf file, restart the RPCIDMAPD service by running the following command on the NFS server:

service rpcidmapd restart

Step 6 Sign in to the Director with administrative credentials and take these actions:

a. Select System > Configuration.

b. In the NFS area, enter the FQDN or the IP address of the NFS server in the NFS Host field.

c. In the NFS area, enter a slash (/).

d. In the NFS area, enter domain of the NFS server in the NFS Domain field.

e. In the NFS area, click Save.

f. Click Apply Config in the left panel.


VMware vSphere Configuration for Cisco WebEx Social

Cisco WebEx Social supports VMware vSphere 4.0 and 5.0.

Cisco recommends VMware vSphere 4.1 or 5.0 for Cisco WebEx Social for the following reasons:

VMware vSphere 4.1 and 5.0 CPU scheduler performance is significantly better than that of VMware vSphere 4.0 CPU scheduler.

VMware vSphere 4.1 and 5.0 have reduced latency for VMware Paravirtualized SCSI (PVSCSI) virtual adapter type compared to that of VMware vSphere 4.0. Cisco WebEx Social virtual machines use the PVSCSI adapter exclusively.

Cisco recommends that you do not run a Cisco WebEx Social node on the same VMware vSphere Hypervisor 4.0 that is running non-Cisco WebEx Social applications. If you need to run these items side-by-side, use VMware vSphere Hypervisor 4.1 or 5.0.

When running on VMware vSphere 4.1 or 5.0, Cisco WebEx Social can run side-by-side with other WebEx Social virtual machines on the same vSphere Hypervisor if CPU and memory reservations are set. CPU and memory reservations are set automatically during OVA deployment.


Note Virtual machines for Cisco WebEx Social must be layer-2 adjacent. Placing security devices or any other network appliances between Cisco WebEx Social virtual machines is not supported.


Follow these steps to perform VMWare configuration:

Procedure


Step 1 Provision the UCS server/ESX hosts for Cisco WebEx Social in to a VMware vSphere Cluster.

Step 2 Enable VMware High Availability (HA) and VMware Dynamic Resource Scheduler (DRS) on the cluster, as shown in the settings in Figure 1-1.

Figure 1-1 VMWare Settings—Enabling HA and DRS

Step 3 For DRS, leave the VMware DRS Fully Automated parameter at its default middle setting.

Step 4 Configure VMware DRS Anti-Affinity Rules to prevent VMware DRS from migrating redundant Cisco WebEx Social Virtual Machines to the same ESX hosts. See Figure 1-2 for where the Anti-Affinity Rules appear in the screen.

Figure 1-2 VMWare DRS Rules

Step 5 Configure VMware Enhanced VMotion Compatibility (EVC) (see Figure 1-3) to match the CPU in the UCS blades.

Figure 1-3 VMWare EVC


Resource Protection

Some guidelines for protecting resources are:

Monitor the Cisco WebEx Social VMware Cluster to ensure that the average CPU utilization is at 60 percent or less during steady usage and no more than 90 percent during peak usage.

Monitor the Cisco WebEx Social VMware Cluster to ensure that the Cisco WebEx Social Virtual Machines and ESX hosts do not come under memory pressure.

VMWare Sizing Tables

See the following tables for guidelines based on the number of Cisco WebEx Social users. The tables are based on a 20-percent concurrent connection of Cisco WebEx Social users.

For related information, see the "Disk Growth and Size" section.

Table 1-3 Virtual Machine Guidelines—0 to 5,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

2

4

250

Cache

2

1

16

2

Director

1

2

8

10

Index Store

1

2

8

20

JSON Store

2

2

8

150

Notifier

1

2

16

2

App Server

2

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

8

20

RDBMS Store

1

2

16

250

Worker

2

4

8

10


Table 1-4 Virtual Machine Guidelines—5,001 to 10,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

2

8

250

Cache

2

1

16

2

Director

1

2

8

10

Index Store

1

2

8

20

JSON Store

2

2

8

150

Notifier

1

2

16

2

App Server

2

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

8

20

RDBMS Store

1

4

16

250

Worker

2

4

8

10


Table 1-5 Virtual Machine Guidelines—10,001 to 20,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

2

8

300

Cache

4

1

8

2

Director

1

2

8

10

Index Store

1

4

10

20

JSON Store

2

2

8

200

Notifier

1

2

16

2

App Server

4

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

6

20

RDBMS Store

1

6

32

300

Worker

2

6

8

10


Table 1-6 Virtual Machine Guidelines—20,001 to 40,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

3

10

400

Cache

6

1

16

2

Director

1

2

8

10

Index Store

1

4

10

20

JSON Store

2

3

10

200

Notifier

1

4

24

2

App Server

6

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

6

20

RDBMS Store

1

8

32

400

Worker

2

6

8

10


Table 1-7 Virtual Machine Guidelines—40,001 to 60,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

3

12

400

Cache

6

1

16

2

Director

1

2

8

10

Index Store

1

4

10

25

JSON Store

2

3

12

250

Notifier

1

4

24

2

App Server

10

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

6

25

RDBMS Store

1

8

32

500

Worker

2

6

8

10


Table 1-8 Virtual Machine Guidelines—60,001 to 80,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

4

16

500

Cache

6

1

16

2

Director

1

2

8

10

Index Store

1

4

10

25

JSON Store

2

4

16

250

Notifier

1

8

36

2

App Server

12

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

6

25

RDBMS Store

1

8

64

500

Worker

2

6

8

10


Table 1-9 Virtual Machine Guidelines—80,001 to 100,000 Users  

Service
# of VMs
vCPUs Per VM
RAM (GB) Per VM
Minimum Disk Space (GB)

Analytics Store

2

4

16

500

Cache

6

1

16

2

Director

1

2

8

10

Index Store

1

4

10

25

JSON Store

2

4

16

250

Notifier

1

8

36

2

App Server

14

4

8

10

Message Queue

2

1

8

2

Search Store

2

2

6

25

RDBMS Store

1

8

64

500

Worker

2

6

8

10


Disk Growth and Size

Each Cisco WebEx Social virtual machine contains two virtual disks. Virtual disk 1 is used for the operating system. Virtual disk 2 internally maps to the /opt directory, which is used to store applications and their data.

All Cisco WebEx Social virtual machines support online growth of the /opt directory. This can be accomplished by either:

Expanding the existing virtual disk 2.

Adding a virtual disk. Add new disks to virtual SCSI adapter 0 first. If all ports on virtual adapter 0 are used, add a virtual SCSI adapter of type "VMware Paravirtual.".


Note Expanding virtual disk 1, which is used for the operating system, is not supported.


A cron job runs within the Cisco WebEx Social virtual machine that calls the lvm-expand.sh script every five minutes. The lvm-expand.sh script scans for new free space and new virtual disks. When either is found, the lvm-expand.sh script extends the LVM volume group, LVM logical volume, and finally the Ext4 partition. This entire process is transparent to the administrator.

Load Balancer Information

A load balancer, such as Cisco Application Control Engine, is required with Cisco WebEx Social. Cisco Application Control Engine can be deployed in Routed Mode or in Bridged Mode.

The following list includes requirements and recommendations for load balancers:

Create a maintenance page for redirecting users. Each Cisco WebEx Social virtual machine supports a maximum of 1500 concurrently connected users.

Set the maximum connections (max conns) to 1500.

Set the recover threshold (min conns) to 1400.

Persistent sessions (sometimes called Source IP Sticky sessions) are required.

When deploying Cisco WebEx Social with a load balancer, it is recommended that you define a backup server farm for situations when sufficient resources are not available to handle the client load.

Cisco recommends setting the maximum cookie size to at least 8 K.

Round Robin predictor is recommended for load balancing.

For each App Server node in your deployment, configure the load balancer health check (probe) to invoke http://App_Server_IP_Address/monit/status.do. This configuration causes an App Server node to return XML data that includes a status code and status text. For example:

<?xml version="1.0" encoding="UTF-8" ?>
<state-manager>
  <quad>
      <code>200</code>
      <status>OK</status>
  </quad>
</state-manager>

Planning

For planning purposes, it is recommended that you write down the values of the following items for each node because you will be prompted to enter these values when you install each node:

Fully qualified domain name (of each node and of the Director)

IP address

IP netmask

IP default gateway

Default DNS domain

Primary name server

Any additional name servers

Administrator password


Note DNS is required for the Cisco WebEx Social network.