Remote Expert Mobile

From DocWiki

Jump to: navigation, search

Contents

Cisco Remote Expert Mobile

Required Hardware

Tested Reference Configurations

This section lists the specifications for the C240 M3 server. The customer deployment must run in a duplexed environment using a pair of core Unified Computing System (UCS) C240 M3 servers known as Side A and Side B. Remote Expert Mobile must be installed on its own pair of Side A and Side B servers. It must not be installed co-resident on Packaged CCE Side A and Side B servers.

UCS C240 M3 Server
Server Model Cisco UCS C240 M3 Tested Reference Configuration (TRC) Server
TRC Name C240M3S(SFF)TRC#1 docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#C240_M3S_%20.28SFF.29_TRC.231


Specification-Based Hardware Support

Cisco Remote Expert Mobile supports specification-based hardware, but limits this support to only UCS B-Series blade and C-Series server hardware. This section provides the supported server hardware, component version, and storage configurations. For more information about specification-based hardware, see UC Virtualization Supported Hardware at docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware.

Hardware Requirements

Server Component Description

Cisco UCS B2XX Blade Server, such as:

  • Cisco UCS B200 M3 Blade Server
  • Cisco UCS B200 M4 Blade Server

Cisco UCS C-Series Server, such as:

  • Cisco UCS C240 M3S Server
  • Cisco C240 M4SX Server

CPU Type

Intel Xeon E5-2600 Family, 2.5 GHz physical core speed minimum

Intel Xeon E5-2600v2 family, 2.5 GHz physical core speed minimum

Intel Xeon E5-2600v3 family, 2.5 GHz physical core speed minimum

Intel Xeon E5-2600v4 family, 2.5 GHz physical core speed minimum

Intel Xeon E5-4600 family, 2.5 GHz physical core speed minimum

Intel Xeon E5-4600v2 family, 2.5 GHz physical core speed minimum

Intel Xeon E5-4600v3 family, 2.5 GHz physical core speed minimum

Intel Xeon E7-2800v2 family, 2.5 GHz physical core speed minimum

Intel Xeon E7-4800v2 family, 2.5 GHz physical core speed minimum

Intel Xeon E7-4800v3 family, 2.5 GHz physical core speed minimum

Intel Xeon E7-8800v2 family, 2.5 GHz physical core speed minimum

Intel Xeon E7-8800v3 family, 2.5 GHz physical core speed minimum

Memory
64 Gb minimum
Virtual Interface Card
In addition to legacy M71KR-Q support, all Cisco Virtual Interface Cards (VICs) are supported.

Cisco Unified Border Element (CUBE ) Enterprise Gateway

Note: Cisco Unified Border Element is optional in
Unified CCX and Unified Communications Manager
only deployments. It is required only if you need
recording at a Cisco Unified Border Element level.

Gateway

ISR G2 with a combination of CUBE-E and VXML.

Cisco Supports ISR G2, which includes 3925E and 3945E gateways.

Note: Specification-based and over-subscription policy: For specification-based hardware, total CPU reservations must be within 65 percent of the available CPU of the host. Total memory reservations must be within 80 percent of the available memory of the host. Total traffic must be within 50 percent of the maximum of the network interface card. IOPS for storage must meet the VM IOPS requirement.

Virtual Machine (OVA) Specifications

For more information regarding Virtual machine installation and configuration, refer to “Remote Expert Mobile—Installation and Configuration Guide 10.6”.

If using a UCS Tested Reference Configuration or specifications-based system, the minimum requirements for development and production systems are:


Development Systems
Deployment Type vCPU Reserved CPU Resource RAM Disk Space NIC
Small OVA (typical installation) 4 core 8400 MHz (4 x 2.1 GHz) 4 Gb 40 Gb 1 Gb


Production Systems
Deployment Type vCPU Reserved CPU Resource RAM Disk Space NIC
 Large OVA (extra preformance
& scalability capabilities)
  8core 16800 MHz (8 x 2.1 GHz)   8Gb 40 Gb 2 x1 Gb
Or
10 Gb


Refer to the VMware developer documentation for additional configuration and hardware requirements. We highly recommend using the Cisco Unified Computing System (CUCS) to simplify and maximize performance. See docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment for the current list of supported UCS Tested Reference Configurations and specs-based supported platforms.

Ensure that:

  • VT is enabled in the BIOS before installing VMware ESXi
  • the VM host “Virtual Machine Startup/Shutdown” is configured to “Allow Virtual machines to start and stop auto-matically with the system”

Co-residency support

Remote Expert Mobile can co-reside with other applications (VMs occupying same host) subject to the following conditions:

  • No oversubscription of CPU: 1:1 allocation of vCPU to physical cores must be used
  • No oversubscription of RAM: 1:1 allocation of vRAM to physical memory
  • Sharing disk storage

Note: Remote Expert Mobile must be installed on its own pair of Side A and Side B servers. It must not be installed co-resident on Packaged CCE Side A and Side B servers.

Sizing Remote Expert Mobile Virtual Machines

Remote Expert Mobile Application Server (REAS)

A REAS node can be deployed in a small OVA or large OVA.

REAS Platform vCPU Non-Transcoded Sessions Transcoded Sessions Expert Assist Sessions
Small OVA 4 core 100 per node (signaling only) 100 per node (signaling only) 100 per node


Remote Expert Mobile Media Broker (REMB)

A REMB node can be deployed in a Large OVA. Transcoding between VP8 and H.264 as well as Opus and G.711/G.729 performance varies depending on video resolution, frame rate, bitrate as well as server type, virtualization or bare metal OS installs, processors as well codec types. However, general guidelines for REMB nodes are as follows.

REAS Platform vCPU Non-Transcoded Sessions Transcoded Sessions Expert Assist Sessions
Large OVA 8 core 90 per node 0 per node NA


45 per node 5 per node NA


0 per node 10 per node NA

The following guidelines apply when clustering Cisco Remote Expert Mobile for mobile and web access:

  • Remote Expert Mobile Base HA deployment has 4 nodes (2 REAS and 2 REMB) and can support up to 100 video and audio calls in a high availability configuration.
  • All REAS nodes of must use identical OVA templates. REMB nodes should only use the large OVA templates.
  • REAS & REMB nodes may be deployed jointly on the same physical server as long server CPU, Memory and Disk space are not in contention.
  • For service continuity, all REAS nodes should not be deployed on the same physical server. All REMB nodes should not be deployed on the same physical server.
  • Up to 4 REAS and 20 REMB may be deployed to increase cluster capacity to 1,000 sessions.

Note: Remote Expert Mobile capacity planning must also consider the capacity of the associated Unified CM cluster(s) and CUBE nodes.

Rating: 0.0/5 (0 votes cast)

Personal tools