Avaya Aura™ Communication Manager Release 6.0 Overview

1. Avaya Aura™ Communication Manager Release 6.0 Overview Mike Gerardi - Sunturn

2. Communication Manager 6.0 Deployment Options Defined • In R6.0, Communication Manager is deployed in two modes: • Feature server (In conjunction with Session Manager) • Evolution server (Access for endpoints & trunks) • 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 AuraTMSession Manager • Must purchase Session Manager hardware to deploy Communication Manager as a feature server • Must purchase Session Manager to deploy SIP terminals with the evolution server option • SIP Phones register to Session Manager

3. Communication Manager 6.0 Deployment Options Compared • 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

4. Avaya Aura™ Architecture May 2010 SessionManager SessionManager SessionManager SessionManager Application Avaya Aura™ Communication Manager (evolution server) Avaya Aura™ Communication Manager (feature server) Avaya Aura™ for Survivable Core SystemManager ServiceProviders Avaya Aura™ Core Connection SIP Trunks Avaya Aura™ Session Border Controller Access Communication Manager R6.x (evolution server ) Supports SIP endpoints w/o SES Communication Manager R5.2.x No SIP endpoints w/o SES Local SM + CM (feature server) CM LSP R5.2.1For use w/ R5.2.1 no SIP endpoint survivability Avaya Aura™ for Survivable Remote Avaya one-X® SIP endpoints Avaya Aura™ for Survivable Remote For use w/ CM in feature server mode Local SM + CM (evolution server) Avaya one-X® H.323/Digital endpoints Avaya one-X® SIP endpoints Non-SIP CM 5.2 Branch Avaya one-X® H.323/Digital endpoints SIP-only Branch Hybrid SIP, non-SIP Branch

5. 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 Avaya Aura™ Applications The Template System Platform Prior to CM 6.0 Communication Manager 5

6. Avaya Aura™ Communication Manager Solutions / Templates

7. Avaya Aura™ Communication Manager Templates • 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 / Survivable Core 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

8. Business Continuity – Levels of redundancy PSTN Avaya Aura™ Communication Manager R6 (Feature Server) Avaya Aura™ for Survivable Core (Feature Server) 2 1 Data Center 2 Data Center 1 Session Manager 6.0 Session Manager 6.0 3 System Manager R6 4 SM / CM on System Platform 5 5 Avaya Aura™ for Survivable Remote AudioCodes (Thin Survivable Branch) Location 1: SIP Endpoints Non-critical remote site, basic survivability during WAN outage Location 2: SIP Endpoints Critical Remote Site, requires full feature survivability in case of WAN outage Levels of redundancy

9. Avaya Aura™ Communication Manager Templates • 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) • For JITC market and JITC testing • Can be used as an LSP-like survivability • Not to be used for survivability in the civilian or commercial market, use instead Avaya Aura™ for Survivable Remote

10. Avaya Aura™ Communication Manager Templates • 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 Utility Services • 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 Utility Services • Template name: CM_SurvRemoteEmbed

11. 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 SM SM SM Communication Manager Feature Server SIP-ISC SIP-ISC Core Avaya Aura™ for Survivable Remote (Simplex) Avaya Aura™ for Survivable Remote (Embedded) SIP SIP Secondary, rainy day Secondary, rainy day Primary Service Primary Service SIP SIP 11

12. 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

13. 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

14. Software Installation and Access to Media • If the customer chooses to download software from Avaya • 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. • Download & utilize pre-migration patches (per previous CM release) • as needed to migrate data (used in migration restore step) • migrations from CM 5.2.1, 5.2.0 and 5.1.2 supported • 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 assignments

15. Software Installation and Access to Media • 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 • Download the CM super.ISO package of five CM 6.0 templates • Or utilize System Platform Console to reach PLDS directly • Bring License file and Authentication file to System Platform (SP) • WebLM Server contained on System Platform

16. Software Installation and Access to Media • 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 • 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

17. Software Installation and Access to Media • 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. 

18. System Platform (SP) – Provides • Use WebConsole • Installation • Upgrading between templates / releases • Once the first template is installed • Additional details System Platform Architecture, Administration and Maintenance by Prasad Subramanian

19. System Platform (SP) – Provides • Remote Access utilizing SAL, Secure Access Link • IP (internet) only, No modem support • Avaya exclusively uses SAL for remote access • Hardware interface for reliability • System Platform has VM restart capabilities • No SAMP, Server Availability Management Processor, support • Remove the SAMP from the migrated s8510 • System Platform interfaces with S8800 IPMI, Intelligent Platform Management Interface. IPMI has additional restart capabilities

20. System Platform (SP) – Provides Alarming • Alarming thru SAL, Secure Access Link • System Platform (SP) alarms hardware/platform items • SP manages server hardware alarms, forwards SNMP thru SAL • RAID, environmental, fans, power supplies, etc. • Applications (e.g. CM) alarm using SNMP directed thru SAL • Changes for CM 6.0 alarming • CM ‘display alarms’ will not show platform/server alarms • New SysOID for CM 6.0 (1.3.6.1.4.1.6889.1.8.1.58 – avaya-aura-cm) • SAL can forward SNMP • CM can also forward SNMP: SNMP-INADS (for Avaya) or SNMP-FPM to Fault Performance Manager or an NMS

21. System Platform (SP) – Provides • Evolving with System Platform (SP) 6.0 to utilize SP for platform type functions • Updates, e.g. service packs • Back-up and Restore •  Applying Updates and Service-Packs • System Platform WebConsole to apply Service-Packs for CM, Utility & SP • CM duplicated servers managed manually • Other options and tools • CM CLI still available • CMM uses SMI (Server Management “Web” Interface) • BSM uses upgradeSM • SUM, Software Update Manager, does not manage SP based templates, does manage firmware & CM service-packs

22. System Platform (SP) – Provides • Back-up and Restore • Use System Platform to back-up and restore SP and applications • SP Console Back-up does not back-up CMM Message Store and database • Other options and tools • CM and CMM has further back-up options thru CM’s SMI (Server Management Interface) • BSM also uses System Manager • No back-ups to Flash cards • SP supports local, SFTP, email • SP does not encrypt back-ups • Can encrypt thru CM SMI (Server Management Interface)

23. Changes with Communication Manager 6.0 • No support for CNA/CNB • Control Network A, Control Network B no longer supported • Used bonded NICs thru System Platform for redundancy • Use corporate LAN and allow customer network / routes to customize • No support for Fiber Connectivity/Center Stage Switch • No fiber connectivity including Expansion Interfaces, DS1Converter, ATM • We’ll test Center Stage Switch for federal at a later date but only for federal customers! • SES will not be supported with CM R6.0 • It is not needed with Session Manager & the Evolution Server

24. Changes with Communication Manager 6.0 • SMI, Server Management Interface, changes • Some items eliminated, some just changed • Due to using System Platform, CM changes, offer changes, etc. • Server Configuration & Configure Server • Diagnostics: Temperature/voltage • Modem, Modem Test • Network Time Sync • Server • Raid Status • Configure Time-server • Set Modem Interface • Configure Rmb • Restore Default -- now done by reinstalling the VM • Eject Cd-rom • Server Upgrades • Manage Software • Make Upgrade Permanent • Boot Partition • Update BIOS • Data Backup/restore • Format Compact • Tripwire/tripwire commands -- tripwire is no longer supported • IP phones • tftpboot

25. CM SMI Pages – Server Role

26. CM SMI Pages – Network Configuration

27. Changes with Communication Manager 6.0 • Migrations only – no upgrades from previous CM 5.x • Migrate translations plus certain platform data • CM 5.2.1, 5.2.0 and 5.1.2 - UserLogins, Logs, etc. • Licensing changes – use WebLM • License & authentication files get installed via System Platform • Increased capacities

28. Boot Time Memory configurations • Boot Time Memory (BTM) and Template Memory Sizes (configurable thru SMI with defaults set) • Match survivable with the main • Migrations from pre-6.0 used a standard or Xlarge memory configuration • If the main was/is a standard, the LSP should be medium survivable. • If the main was/is a xlarge, the LSP should be a large survivable. • If the main was/is an S8300, the LSP should be a small survivable. • CM_Duplex, CM_Simplex, CM_SurvRemote, CM_SurvRemoteEmbed templates default to large • CM_onlyEmbed defaults to small

29. Changes with Communication Manager 6.0 • Impacts to AIM, Avaya Integrated Management • No AIW, Avaya Installation Wizard • NRW, Network region Wizard, moved to separate standalone download • SUM does manages firmware & CM service-packs, not upgrades/migrations for CM 6.0 • Additional details: Avaya Integrated Management 6.0 Eran Shapiro, Al Garcia • Move items from CM to Utility Services • ESD, Enhanced System Directory • Phone and GW firmware file management including http server. Note TN firmware is not included in the Utility Services

30. Utility Services • HTTP and HTTPS fileserver for IP phones & Gateway firmware • Scheduling and control of H323 IP phone firmware upgrades • Control of IP phone settings via GUI settings editor • MyPhone (self administration tool for IP phone users) • CDR collection tools • DHCP server • Enterprise System Directory allowing LDAP lookups via IP Phones

31. System Capacities • There are some key capacity changes in CM 6.0 to align better with the Avaya reference architecture with Session Manager at the core • Better CM SIP trunk capacities • Increased station capacity • Offer capacities are now set by the deployed System Platform template • Similar to platform limits in previous releases, but a bit more hardware independent • Set by “boot time memory” parameters

32. Capacity Increases • SIP Trunking Expansion • Increased from 7,000 to 24,000 for CM in the Feature Server configuration (“IMS Enabled” set to “y”) • Increased to 12,000 CM in the Evolution Server configuration (“IMS Enabled” set to “n”) • A single CM does not support simultaneous administration of “Feature Server” SIP trunks and “Evolution Server” SIP trunks • Scale • CM now supports up to 18,000 IP endpoints • May be any mix of H.323 or SIP stations • Up to 10,000 agents are supported • SIP performance is also improved by replacing and upgrading certain components of the SIP “stack”

33. Offer Capacities determined by Template • Avaya Aura™ Main / Avaya Aura for Survivable Core (Simplex configuration) • Contrast with CM 5.2.1 S8800 simplex • 18000 H.323 / SIP stations (up from 2400) • 24000 SIP trunks in feature server mode, half call model (up from 7000) • 12000 SIP trunks evolution server (up from 7000) • Unless in a survivable configuration, then 12000 SIP trunks on main and 12000 on survivable server  • Avaya Aura Main / Avaya Aura for Survivable Core (Duplex configuration) • Contrast with CM 5.2.1 S8800/S87xx duplex • Capacities are the same as Avaya Aura Main / Avaya Aura for Survivable Core (Simplex configuration) above • Embedded CM Main Template • Contrast with CM 5.2.1 S8300D • 1000 H.323 / SIP stations (up from 450) • 4000 trunks (up from 450) • Unless in a survivable configuration, then 2000 SIP trunks on main and 2000 on survivable server 

34. Capacities by Template (continued) • Avaya Aura for Survivable Remote (Simplex configuration) • Contrast with CM 5.2.1 LSP on S8800 simplex • 5000 active H.323 / SIP stations (up from 2400) • 12000 active H.323 / SIP trunks (up from 7000) • Supports full core server translation set for survivability • Avaya Aura for Survivable Remote (Embedded configuration) • Contrast with CM 5.2.1 LSP on S8300D • 1000 active H.323 / SIP stations (up from 450) • 2000 active H.323 / SIP trunks (up from 450) • Supports full core server translation set for survivability

35. thank you Mike Gerardi mgerardi@sunturn.com 602-388-4505

36. Back-up

37. S8800 NIC Layout (rear of server) for CM 6.0 5. PCI Ethernet connector 1 (eth 5) – not used at this time (subject to change) 6. PCI Ethernet connector 0 (eth 4) – not used at this time 18. Ethernet connector 2 (eth 1) – Services Port 19. Ethernet connector 1 (eth 0) – Corporate LAN/Processor Ethernet 20. Ethernet connector 4 (eth 3) – CM duplication link (when needed) 21. Ethernet connector 3 (eth 2) – HA / 2nd NIC for bonding to eth 0 22. System MGMT (management) Ethernet connector (IMM – Integrated Management Module)