avayaauracm6.0overview

Avaya Aura™ Communication Manager Release 6.0 Template Overview

CONFIDENTIAL& NOT TO BE DISCLOSED BEFORE JUNE 8TH.

Avaya – Proprietary. Use pursuant to Avaya policy.

– Key points to understand the CM6.0

• Two modes CMs

• System Platform & CM6.0 Template

• Supported CM servers

• Software Access & Licensing via PLDS

2

Communication Manager 6.0 Overview

Avaya – Proprietary. Use pursuant to Avaya policy. 3

Communication Manager 6.0 Deployment Options Defined

�In R6.0, Communication Manager is deployed in two modes:

– Feature server

– Evolution server

�Material Code and Price is the same for both

– Since they are just administrable options for the same software

�Simple to administer

– Just a single field in the CM SIP trunk configuration to Avaya

AuraTM Session Manager

�Must purchase Session Manager to deploy Communication

Manager as a feature server

�Must purchase Session Manager to deploy SIP terminals

with the evolution server option


� Feature server is the descriptor for the option of deploying Communication Manager 6.0 in the core or remote, in half call model, supporting only SIP endpoints with full application sequencing

• SIP Endpoints register with Session Manager

• Communication Manager employs the half call model

• Supports only G450/G430 gateways

• Supports full application sequencing

� Evolution server is the descriptor for the option of deploying CM 6.0 in the core or remote, in full call model, supporting both SIP and non-SIP endpoints with limited application sequencing

• H.323/Digital/Analog endpoints register with Communication Manager

• SIP endpoints register with Session Manager

• All endpoints receive service from Communication Manager

• Only supports implicit sequencing (limited application sequencing)

• Communication Manager employs the full call model

• Supports all current Communication Manager gateways and Port Networks

Communication Manager 6.0 Deployment Options Compared


Avaya Aura™ Architecture May 2010

Communication

Manager R5.2.x

No SIP endpoints

w/o SES

Service

Providers

System

Manager

SessionManager

Avaya Aura™ Core

SIP

Trunks

Access

ConnectionSessionManager

Avaya one-X®

SIP endpoints

SessionManager

SessionManager

Local SM + CM

(feature server)

Avaya Aura™ Session

Border Controller

Avaya Aura™

Communication Manager

(feature server)

Avaya Aura™ for

Survivable Core

Avaya Aura™ for

Survivable Remote

For use w/ CM in feature

server mode

Communication

Manager R6.x

(evolution server )

Supports SIP endpoints

w/o SES

Local SM + CM

(evolution server)

CM LSP R5.2.1For use w/ R5.2.1

no SIP endpoint

survivability

Avaya one-X®

SIP endpoints

Avaya Aura™ for

Survivable Remote

Avaya one-X®

H.323/Digital endpoints

Avaya one-X®

H.323/Digital endpoints

Application

SIP-only Branch

Hybrid SIP, non-SIP Branch

Non-SIP CM 5.2 Branch

Avaya Aura™

Communication Manager

(evolution server)


Avaya Aura™ Communication Manager Templates

� Every release of Communication Manager 6.0 will be on the Avaya AuraTM System Platform

� A template is a configuration of applications running on System Platform

�Simpler and easier to install, configure and manage

Communication ManagerAvaya Aura™ Applications

System Platform

Prior to CM 6.0

The Template


Avaya Aura™ Communication Manager Solutions / Templates

7

Avaya Aura™ CM Main / Avaya

Aura™ for Survivable Core

Duplex version

Avaya Aura™ CM Main / Avaya

Aura™ for Survivable Core

Simplex version

Avaya Aura™ for Survivable Remote

Simplex version

Avaya Aura™ for Survivable Remote

Embedded version

Avaya Aura™ CM

Main

Embedded version

Template Name

CM_Duplex CM_Simplex CM_SurvRemote CM_SurvRemoteEmbed CM_onlyEmbed

Domain 0/1 Hypervisor (Dom0)

CDOM (Dom1): SAL

Hypervisor (Dom0)

CDOM (Dom1): SAL

Hypervisor (Dom0)

CDOM (Dom1): SAL

Hypervisor (Dom0)

CDOM (Dom1): SAL

Hypervisor (Dom0)

CDOM (Dom1): SAL

Dom 2 CM 6.0 Utility Services Utility Services Utility Services Utility Services

Dom 3 CM/CMM 6.0 CM 6.0 CM 6.0 CM/CMM 6.0

Dom 4 Session Manager 6.0 for Survivable Remote

Session Manager 6.0 for Survivable Remote

Use Case Large Enterprises (>5000 stations) who want a CM feature server and survivable feature server. Or as access elements.

Duplex: 18K H.323 or SIP endpoints

Equal or greater than 5.2 capacity

6000 CM mailboxes

To survive endpoints at remote sites (H.323, digital, analog, SIP). LSP migration.

•Simplex: 2400+ SIP/ H.323 active stations (5000 station)

•Embedded: 450+ SIP/ H.323 active stations (1000 station)

450+ SIP/H.323 endpoints; (1000 stations)

HW 2 - S8800 S8510 w/ 8G or S8800

S8510 w/ 8G or S8800 S8300D S8300D


� Avaya Aura™ CM 6.0 offers two main/core templates

– Installed on S8800 or S8510 server with System Platform

� Avaya Aura™ Communication Manager - Duplex CM Main / SurvivableCore Template (for S8800 only)

– Template includes CM 6.0

– Requires two servers (same identical server hardware) and can be a Main (default) or ESS-like survivability

– Template name: CM_Duplex

� Avaya Aura™ Communication Manager - Simplex CM Main / Survivable Core Template (for S8800 and S8510)

– Template includes CM 6.0, CMM 6.0 and Utility Services

– Template name: CM_Simplex

– Can be a Main (default) or ESS-like or LSP-like survivability



� Avaya Aura™ CM 6.0 offers one embedded main template

– Embedded is on the S8300D server with System Platform

� Avaya Aura™ Communication Manager - Embedded CM Main Template (for S8300D only)

– Template includes CM/CMM 6.0 (in the same VM) and Utility Services

– Template name: CM_onlyEmbed

– Can be a Main (default)



� Avaya Aura™ CM 6.0 offers two survivable remote templates

– Installed on S8800/8510 or S8300D server with System Platform

� Avaya Aura™ CM for Survivable Remote (for S8800 and S8510)

– Enables ESS-like or LSP-like survivability

– Template includes CM 6.0, Branch Session Manager 6.0 and UtilityServices

– Template name: CM_SurvRemote

� Avaya Aura™ CM for Embedded Survivable Remote (for S8300D)

– Enables survivability of telephony and access at remote locations in a LSP-like mode

– Template includes CM 6.0, Branch Session Manager 6.0 and UtilityServices

– Template name: CM_SurvRemoteEmbed



Thick Remote Office Survivability: 100% SIP endpoints - utilize CM Feature Server

� For Survivable Remote Sites: Utilize system platform with Branch SM and CM feature server on either a simplex

(S8800, S8510) or embedded S8300D server

� 96xx SIP Phones register to (1) the main SM, (2) a backup main SM, (3) and the Local BSM. On a WAN outage the

local SM and CM feature server take over.

� Media services provided by the local H.248 gateway during sunny and rainy day scenarios

CoreSM

SMSM

Primary Service

Primary Service

Secondary, rainy day Secondary,

rainy daySIP

SIP

SIP

SIP

Communication Manager Feature Server

SIP-

ISC

SIP-

ISC

Avaya Aura™ for Survivable

Remote (Simplex) Avaya Aura™ for

Survivable Remote

(Embedded)


Avaya AuraTM Communication Manager 6.0 Servers

�S8300D

� Embedded blade for Avaya Aura Gateways (G450/30,350,250,700)

�S8510 Server - not used for duplication

� Use in a simplex migration by adding memory add 6GB to total of 8GB

� most have 250GB HDD but if 146G HDDs, add third 146GB HDD and RAID 5

�S8800 Server for Communication Manager 6.0

� 700478514 comcode, with a single CPU-quad core, 12 GB RAM

� Three 146 GB hard disks (HDD) in RAID 5, 272GB useable

� 6 total NICs: 2 on mother board, 2 on daughter card, 2 on PCI NIC

� Single power supply (with optional second power supply)

� Software duplication available, hardware duplication is not offered

12


Communication Manager on System Platform

�All instances of Communication Manager 6.0 run on System Platform

– CM is in its own virtualized machine (VM) and does not “own the hardware”

�All platform (Server-type) items managed by System Platform

�Installation via a solution template (CM with BSM & …) after System Platform installed

�The five CM 6.0 templates are all packaged in a single CM_super.iso

– CM_Duplex, CM_Simplex, CM_onlyEmbed, CM_SurvRemote, CM_SurvRemoteEmbed

13


Software Installation and Access to Media (via PLDS)

�If the customer chooses to download software from Avaya

1. Customer/partner will go to the download pages on support.avaya.com which will be linked to PLDS

– the CM pages look a lot like they do today for CM 5.x.

2. Download & utilize pre-migration patches (per previous CM release)

– as needed to migrate data (used in migration restore step)

– migrations from CM 5.2.1only supported today. Others translation only migration

3. Customer/partner will download System Platform (SP) 6.0, burn a .ISO DVD & install System Platform on the server

– Insert the bootable SP.ISO DVD into the server’s drive

– Walk thru nominal questions, e.g. VLAN assignments14


Software Installation and Access to Media

4. Download the Installation Wizard to collect CM initial configuration data/information

– Install Wizard is customized per template to gather user inputs: IP addresses, hostnames, proxy, DNS servers, initial cust login, etc.

– Install Wizard runs standalone w/o server hardware, run on PC

– Save EPW file to import initial CM configuration data at install

5. Download the CM super.ISO package of five CM 6.0 templates

– Or utilize System Platform Console to reach PLDS directly

6. Bring License file (from PLDS) and Authentication file (from AFS) to System Platform (SP)

– WebLM Server contained on System Platform

15



7. Install one of the templates via System Platform Console

– Initial template install will initialize the Install Wizard

• Import saved EPW information

• Else real-time Install Wizard will prompt for initial configuration data –THIS IS REQUIRED

8. Configure CM and other applications through standard interfaces accessed directly into the VM

– CM and CMM use SAT, SMI Web Pages, ProVision, etc.

– BSM uses Avaya AuraTM System Manager

– Utility Services Web Pages

16



�If the customer chooses to receive physical media, there are optional orderable items:

– System Platform.ISO DVD

– CM_super.ISO DVD

– RAID conversion CDs that are needed for server configuration set-up/changes for S8800 and certain S8510 migrations

�Customer/Partner will still have to download the following from support.avaya.com or PLDS, Product Licensing and Delivery System

– pre-install patches, service packs, firmware updates, etc.

17


thank you

David Ng

avayaauracm6.0overview

Documents