Скачать презентацию LINK TO RECORDED PRESENTATION http uconnect demoavaya com p Скачать презентацию LINK TO RECORDED PRESENTATION http uconnect demoavaya com p

6dab4296ffab10e0b4b41f365864eac6.ppt

  • Количество слайдов: 60

LINK TO RECORDED PRESENTATION http: //uconnect. demoavaya. com/p 23768869/ CONFIDENTIAL& NOT TO BE DISCLOSED LINK TO RECORDED PRESENTATION http: //uconnect. demoavaya. com/p 23768869/ CONFIDENTIAL& NOT TO BE DISCLOSED BEFORE JUNE 8 TH.

Avaya Aura Conferencing TM Presenter: Ignacio Miranda CONFIDENTIAL & NOT TO BE DISCLOSED BEFORE Avaya Aura Conferencing TM Presenter: Ignacio Miranda CONFIDENTIAL & NOT TO BE DISCLOSED BEFORE JUNE 8 TH

Overview § § New Release Offering Enterprise Edition and Standard Edition Aura Conferencing Standard Overview § § New Release Offering Enterprise Edition and Standard Edition Aura Conferencing Standard Edition TM § § § § Solution Installation Licensing System Configuration Management Solution Modeller Logging and Alarming Upgrades Aura Conferencing Enterprise Edition TM § § § Solution Installation Licensing System Configuration Management Solution Modeller Logging and Alarming Upgrades Avaya – Proprietary. Use pursuant to Avaya policy. 3

New Release Offering Extends Avaya Aura. TM integration through platform adoption – foundation application New Release Offering Extends Avaya Aura. TM integration through platform adoption – foundation application for enterprise communications Simplifies administration and lowers cost of serviceability (Avaya Aura. TM System manager, Avaya Aura. TM System platform) Deployment on Avaya’s System Platform Rapidly deploy pre-configured systems into the field. It will also provide the ability to run several Avaya products on a single server. Integration with Avaya’s System Manager which will include webbased configuration, common logging, and SNMP Support for Avaya’s Secure Access Link Standard Edition will Replace the MX Express technology This release will be capable of supporting Asian (double byte) languages Licensing will be Integrated with Avaya’s PLM framework Avaya – Proprietary. Use pursuant to Avaya policy. 4

Standard VS Enterprise Bridge Standard Audio Bridge IP H. 323 Y Y TM Y Standard VS Enterprise Bridge Standard Audio Bridge IP H. 323 Y Y TM Y (through Avaya Aura Communication Manager) IP SIP Y Y Maximum Capacity 300 4000 Single Server Y Languages Y Y SNMP Y Y Adhoc Conferencing Y Y Disaster Recovery Video Enterprise Y Y Database Interface (API or Stored Procedures) Y Y Flex Call Flow Y Y Bridge Talk Y Real-Time Conference Control API Y Y Avaya – Proprietary. Use pursuant to Avaya policy. 5

Standard VS Enterprise Standard Media Server Enterprise SRTP Y Y Video Conferencing Y Multiple Standard VS Enterprise Standard Media Server Enterprise SRTP Y Y Video Conferencing Y Multiple Codecs Y Separate Media Server Y Multisite Y Conference Viewer LDAP Integration Y Y Audio Console CRS Y Y Y Applications Standard Y Enterprise Y Self Reg Web Scheduling and Web Admin Y Y SMS Notifications Y Y Wholesaler / Reseller Model Billing Y Y Reporting Y Y Email Notification Subsystem Y Y Multi-system Logical Cabinet Redundancy Y Y Y Avaya – Proprietary. Use pursuant to Avaya policy. 6

Standard VS Enterprise Groupware Enterprise Standard Outlook Integration Y Y OCS 2007 R 2 Standard VS Enterprise Groupware Enterprise Standard Outlook Integration Y Y OCS 2007 R 2 Integration Y Y Sametime Integration Y Y Adobe Integration Y Y Notes Integration Y Y AWC Recording Server AWC Playback Server AWC Integration Y Y Avaya – Proprietary. Use pursuant to Avaya policy. 7

Aura Conferencing Standard Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. 8 Aura Conferencing Standard Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. 8

Standard Solution Single server solution Standard IBM 3550 M 2 aka. Avaya S 8800 Standard Solution Single server solution Standard IBM 3550 M 2 aka. Avaya S 8800 MX 6. 0 S 8800 Comcode is 700500427 The orderable code is 229568 Requires installation of System Platform ISO, provided via CD System Platform ISO installs the Cent. OS, the XEN software and other software/tools to provide virtualization Requires the installation of a system platform template that contains the following VM images: § § § System Manger Web Conferencing Web Portal plus Audio Console Client Registration Server Application server/Media Server Standard Edition will be the upgrade path for Meeting Exchange Express 300 port systems. The upgrade from these older platforms to Standard will be a forklift upgrade. All configuration managed through System Manager web interface. Avaya – Proprietary. Use pursuant to Avaya policy. 9

Standard Solution Diagram The light blue is the Domain-0 which represents System Platform and Standard Solution Diagram The light blue is the Domain-0 which represents System Platform and needs to be installed on the server before a template can be applied. The darker blue represents the conferencing Virtual Machines that will form the Standard Edition Template. The template includes the whole solution except for the system platform that has to be installed in the machine initially. Upgrades will be provided as a new template Conferencing Standard Edition Template Avaya – Proprietary. Use pursuant to Avaya policy. 10

Server Specification Application Aura. TM Conferencing Standard Edition Make/Model IBM X 3550 M 2 Server Specification Application Aura. TM Conferencing Standard Edition Make/Model IBM X 3550 M 2 Processor Two x Quad Core Intel® Xeon Processor X 5570 4 C (2. 93 GHz 8 MB L 3 Cache 1333 MHz 95 w) Memory 24 GB (12 x 2 GB DDR 3 -1333 2 Rx 8 LP RDIMM) Bezel AVAYA BEZEL Raid RAID 5 - MR 10 i Integrated RAID Controller. Disk Drives 3 x 300 GB SAS 2. 5" 10 K RPM Hard Drive. Addl NIC's Broadcom Corporation Net. Xtreme II BCM 5709 Gigabit Ethernet Removable Media DVD-R/W SATA slimline Power Supply 2 x 675 W 12 V Hotplug AC power supply. Fans Redundant Multi-Speed Fans Firmware IMM v 1. 05, RAID v 11. 0. 1 -0019, u. EFI v 1. 03 and HDD v 1. 05 Avaya – Proprietary. Use pursuant to Avaya policy. 11

Avaya Aura™ Conferencing Standard Edition Installation Conferencing R&D Avaya – Proprietary. Use pursuant to Avaya Aura™ Conferencing Standard Edition Installation Conferencing R&D Avaya – Proprietary. Use pursuant to Avaya policy. 12

Installing Standard Edition First The System Platform ISO has to be installed, it contains Installing Standard Edition First The System Platform ISO has to be installed, it contains the CENTOS OS and the template management console which will allow the installation of templates. Use the Template DVDs or Download a Template from PLDS website. “plds. avaya. com” Using System Platform install the template Via the GUI. Avaya – Proprietary. Use pursuant to Avaya policy. 13

The IP address for all the Virtual Machines will have to be configured during The IP address for all the Virtual Machines will have to be configured during the Installation of the Template After the template is installed , the Windows Virtual Machines for the CRS and AWC will have to be activated with a valid license from Microsoft, for the Windows server 2008 Windows required updates will have to be installed after the system is up and running The Antivirus has to be installed after the update Avaya – Proprietary. Use pursuant to Avaya policy. 14

AURA Conferencing Licensing TM Avaya – Proprietary. Use pursuant to Avaya policy. 15 AURA Conferencing Licensing TM Avaya – Proprietary. Use pursuant to Avaya policy. 15

Licensing • Licensed Attributes Feature Name VALUE_CONF_EDITION Feature Description Standard or Enterprise VALUE_CONF_AWC_USERS Maximum Licensing • Licensed Attributes Feature Name VALUE_CONF_EDITION Feature Description Standard or Enterprise VALUE_CONF_AWC_USERS Maximum Avaya Web Conferencing (AWC) Users AWC licensing mechanism same as 5. 2 FEAT_CONF_AWC_RECORDING_P AWC Recording/Playback LAYBACK AWC licensing mechanism same as 5. 2 VALUE_CONF_EXTERNAL_UC_CI_ Maximum External UC Client Integration USERS Users VALUE_CONF_AUDIO_PORTS Maximum Audio Ports per Application Server VALUE_CONF_VIDEO_PORTS Not currently used. VALUE_CONF_ISAC_CODEC_PORT Not currently used. S Avaya – Proprietary. Use pursuant to Avaya policy. 16

Licensing 4 A newly installed Conferencing system will have a grace period of 30 Licensing 4 A newly installed Conferencing system will have a grace period of 30 days in the following cases: – There is no license or it is not valid – To get the Grace Period started the system has to be able to register with SMGR at least once – The SMGR is down or cannot be contacted 4 The Grace period will allow all components to operate as normal up to their maximum default value 4 Once the Grace Period expires the system will stop functioning 4 Once a valid license is retrieved from Web. LM the components are configured as per the licensed and started 4 A valid license will never expire 4 The license is cached in the local system and will be updated only if new licenses are installed or de-installed in the Web. LM server 4 In the case of a license failure an alarm and log statement will be raised 4 In a multisystem scenario there is a single license with the total number of ports for the customer: – Each bridge takes the number of ports its configured for – If not enough ports are available in the license it will take the max available Avaya – Proprietary. Use pursuant to Avaya policy. 17

Licensing CRS Licensing 4 Pulls the Edition from the license, to know whether it Licensing CRS Licensing 4 Pulls the Edition from the license, to know whether it is Enterprise or Standard 4 Pulls the number of external UC CI users, for every user that tries to use the SOAP adaptor. External adaptors, like Microsoft, OCS, IBM, Outlook. 4 The Grace Period will allow the CRS to have as many users as required up to the maximum. Once the grace period expires none will be allowed. 4 It manages how many users get a license internally 4 When the grace period finishes, the Users are still allowed to complete their session but no new sessions will be allowed WEB Portal Licensing 4 Query for VALUE_ACC_EDITION, to know if it is enterprise or standard 4 The distinction is just a formality, the software behaves the same way in standard and enterprise 4 During Grace Period Enterprise will be assumed 4 If there is a license failure, or grace period expires, the web portal will still run, but it will display a page saying that the license is expired. Avaya – Proprietary. Use pursuant to Avaya policy. 18

Licensing Bridge Licensing 4 The Licence Proxy will retrieve the VALUE_ACC_AUDIO_PORTS and the VALUE_ACC_EDITION Licensing Bridge Licensing 4 The Licence Proxy will retrieve the VALUE_ACC_AUDIO_PORTS and the VALUE_ACC_EDITION properties from the license server 4 The num. Channels value in system. cfg will be populated with the VALUE_ACC_AUDIO_PORTS count prior to the processes start up 4 If the server edition is standard, only G. 711 codecs will be allowed 4 During Grace Period the proxy manager will check if the system is running in SP, if so it will assume standard and allow 300 ports if not it will assume enterprise and allow 3200 ports. AWC Licensing 4 In Conferencing 6. 0 we will be licensing AWC using DCLs proprietary license, without any changes to the way it was normally done in 5. 2 Avaya – Proprietary. Use pursuant to Avaya policy. 19

Configuring system 4 View license details or installing a new license file – https: Configuring system 4 View license details or installing a new license file – https: //135. 64. 26. 160/SMGR - admin/admin 123 – Navigate to Licenses: • Server Properties – display the details needed to create a license file • Install License – provides a page to install a new license file • Licensed Products – shows the installed license and its usage Avaya – Proprietary. Use pursuant to Avaya policy. 20

Licensing License Installation GUI 4 Interface to install the license for the product 4 Licensing License Installation GUI 4 Interface to install the license for the product 4 One single license for the product per site, with all the properties acquired by the customer Avaya – Proprietary. Use pursuant to Avaya policy. 21

AURA Conferencing System Configuration Management TM Avaya – Proprietary. Use pursuant to Avaya policy. AURA Conferencing System Configuration Management TM Avaya – Proprietary. Use pursuant to Avaya policy. 22

Configuration Management 4 Aura Conferencing Element Manager will provide configuration pages to be able Configuration Management 4 Aura Conferencing Element Manager will provide configuration pages to be able to setup TM the Bridge. 4 The configuration Manager will GET the configuration data for all the components 4 It Queries the bridge regularly and caches the information in the System Manager 4 Each component (Bridge, CRS, Web Portal…. ) continues to use their specific configuration files and databases, with their current specific formats. 4 The new configuration changes are verified before they are SET back to the components. 4 If two people make changes to the configuration in parallel, the last one will get a warning and the option to either discard the changes or overwrite the other parallel changes. 4 If a configuration parameter exists in any of the configuration files that is not managed by the configuration manager, this parameter will not be modified or affected when changes are made to that file via the System Manger GUI 4 Manual changes could be made to the original configuration files (this is strongly discouraged) 4 Any changes made to the files will be picked by the Configuration Manager and displayed next time someone access the web pages Avaya – Proprietary. Use pursuant to Avaya policy. 23

Configuration Management AWC Configuration 4 The configuration of AWC will be done via its Configuration Management AWC Configuration 4 The configuration of AWC will be done via its own WEB pages 4 The Conferencing element manager will have a link to the AWC WEB pages 4 There are certain parameters in the Web Portal and CRS that need to be exposed and affect the configuration of AWC Avaya – Proprietary. Use pursuant to Avaya policy. 24

Configuring system 4 Adding Conferencing nodes – bridge/crs/wp and AWC to the SMGR – Configuring system 4 Adding Conferencing nodes – bridge/crs/wp and AWC to the SMGR – https: //135. 64. 26. 160/SMGR - admin/admin 123 – Navigate to Elements => Inventory => Manage Elements – Add the 4 entities selecting Type Conferencing 6. 0, committing changes each time Avaya – Proprietary. Use pursuant to Avaya policy. 25

Configuring system 4 Useful information – Accounts/passwords • BRIDGE craft/craft 01 – sroot/sroot 01 Configuring system 4 Useful information – Accounts/passwords • BRIDGE craft/craft 01 – sroot/sroot 01 • CRS administrator/gatekeeper • WP craft/craft 01 – sroot/sroot 01 • AWC administrator/gatekeeper • System Manager – root/root 01 (shell) admin/admin 123 (web) • System Platform admin/admin 01 • Dom 0 root/root 01 Avaya – Proprietary. Use pursuant to Avaya policy. 26

Avaya Aura™ Conferencing 6. 0 Solution Modeller The replacement for EPW Avaya – Proprietary. Avaya Aura™ Conferencing 6. 0 Solution Modeller The replacement for EPW Avaya – Proprietary. Use pursuant to Avaya policy. 27

Avaya Aura™ Conferencing 6. 0 Solution Modeler 4 Supports configuration of Bridge, CRS, AWC Avaya Aura™ Conferencing 6. 0 Solution Modeler 4 Supports configuration of Bridge, CRS, AWC and Web 4 Supports backward compatibility within a Major. Minor i. e. within 6. 0. ? . ? 4 The default values are the default values of the systems it was built against. Note: if the default values have changed between 6. 0. a. b. c and 6. 0. x. y. z and you load a model created with 6. 0. a. b. c into 6. 0. x. y. z the default values will not be updated. 4 If a parameter can be configured from the conferencing element manager in Avaya Aura™ System Manager, it can be pre-configured from Avaya Aura™ Conferencing 6. 0 Solution Modeler We take the same Conferencing Element manager and package it in both Avaya Aura™ System Manager and Avaya Aura™ Conferencing 6. 0 Solution Modeler Avaya – Proprietary. Use pursuant to Avaya policy. 28

Avaya Aura™ Conferencing 6. 0 Solution Modeller Architecture 4 Solution Modeller takes the Conferencing Avaya Aura™ Conferencing 6. 0 Solution Modeller Architecture 4 Solution Modeller takes the Conferencing EM and embeds it in a standalone web server that runs from a laptop. 4 It is the same EM as bundled in System Manager therefore no issues with synchronization. Conferencing Element Manager 4 Will provide some default models reflecting common configuration scenarios. 4 Models can then be exported for subsequent import into the Conferencing Element Manager running in System Manager 4 Importing a configuration exported from the Solution Modeller into System Manager will behave the same as importing a configuration from another System Manager. 4 Note: Models do not contain the actual IP addresses of servers. The Import functionality within the Conferencing Element Manager in System Manager provides a means for resolving which servers are which System Manager IPTCM Element Manager Session Manager Element Manager Conferencing Element Manager SFS Element Manager Conferencing 6. 0 Solution Modeller Conferencing Element Manager Solution Modeller UI Default Models Presence Element Manager Avaya – Proprietary. Use pursuant to Avaya policy. 29

Avaya Aura™ Conferencing 6. 0 Solution Modeller Architecture (continued) 4 The embedded web server Avaya Aura™ Conferencing 6. 0 Solution Modeller Architecture (continued) 4 The embedded web server is configured to listen for connections from local host only and to listen on a random port. 4 System Requirements: – Java Development Kit version 6. 0_18 or newer – 2 GB RAM – 1 GB free disk space Avaya – Proprietary. Use pursuant to Avaya policy. 30

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 On start up it shows an Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 On start up it shows an application window with buttons to exit and to launch a browser (as it listens on a random port) 4 The application can only be accessed from the computer on which it is running. TM Avaya Aura Conferencing 6. 0 Solution Modeller Avaya Aura™ Conferencing 6. 0 Solution Modeller Avaya – Proprietary. Use pursuant to Avaya policy. 31

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 Same look and feel as System Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 Same look and feel as System Manager 4 Solutions component is used to manage models: – Provision servers into the model – Save / Load current model – Throw away the model and start again 4 Conferencing Element Manager is the same as in System Manager Avaya – Proprietary. Use pursuant to Avaya policy. 32

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 From the Server’s screen you can Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 From the Server’s screen you can provision new servers into the model 4 Server’s screen also shows: – The servers that have been provisioned in the model – How many IP addresses will be required for each server Avaya – Proprietary. Use pursuant to Avaya policy. 33

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 You then can use the Conferencing Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 You then can use the Conferencing Element Manager to configure the model 4 Wire up each of the servers using their pseudo-IP addresses 4 Make any necessary changes to the configuration. 4 You can apply changes to the model as you go along – provides a layer of undo 4 Shows the potential impact of your changes on a real system Avaya – Proprietary. Use pursuant to Avaya policy. 34

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 When the model is ready, you Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 When the model is ready, you export the configuration from the Conferencing Element Manager 4 Note: – Solution modeller works with two types of files: • Conferencing Models – contains details of the provisioned servers and their configuration – Can Only Be Read by Solution Modeller • Exported Configurations – contains details of the configuration of conferencing servers – Can be read and written by Both Solution Modeller and System Manager – Used to copy configurations between System Manager installations (e. g. useful for replicating a deployment, e. g. test lab, etc) – Does not contain details of the SAP codes of the provisioned servers as System Manager does not know this information. Avaya – Proprietary. Use pursuant to Avaya policy. 35

Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 When the servers arrive on site, Avaya Aura™ Conferencing 6. 0 Solution Modeller 4 When the servers arrive on site, you import the configuration into System Manager: 4 Then you need to resolve the IP addresses from the model against the IP addresses of the servers you actually have deployed 4 Once you complete the import wizard you will be directed to the standard Apply changes screen showing all the changes to be applied and the impact of these changes Avaya – Proprietary. Use pursuant to Avaya policy. 36

AURA CONFERENCING TM Logging and Alarming for Conferencing Avaya – Proprietary. Use pursuant to AURA CONFERENCING TM Logging and Alarming for Conferencing Avaya – Proprietary. Use pursuant to Avaya policy. 37

Logging and Alarming for Conferencing 4 All conferencing logging components log to SMGR (via Logging and Alarming for Conferencing 4 All conferencing logging components log to SMGR (via rsyslog/bridge/sal-agent) 4 Logs and Alarms are viewable on SMGR interface 4 SMGR Alarming Service can be configured to send received alarms as SNMP traps to a specified NMS location and port Avaya – Proprietary. Use pursuant to Avaya policy. 38

Log lifecycle Logging Component (Bridge, CRS, AWC, WP) creates log rsyslog process on bridge Log lifecycle Logging Component (Bridge, CRS, AWC, WP) creates log rsyslog process on bridge writes to sal-agent process on bridge read by /var/log/avaya/spirit. log alarm log trap SMGR NMS Location Avaya – Proprietary. Use pursuant to Avaya policy. 39

sal-agent 4 sal-agent process runs on the bridge 4 sal-agent process receives conferencing logs sal-agent 4 sal-agent process runs on the bridge 4 sal-agent process receives conferencing logs from rsyslog and: 1. Sends logs to SMGR Logging Service 2. Sends alarms to SMGR Alarming Service 4 sal-agent must be manually configured from SMGR Element Manager. Need to provide: 4 Alarming ID (unique per install) and; 4 Managed Element ID (product specific) Avaya – Proprietary. Use pursuant to Avaya policy. 40

debugging – files on bridge: 4/var/log/avaya/spirit. config. log – sal-agent initialization log – Check debugging – files on bridge: 4/var/log/avaya/spirit. config. log – sal-agent initialization log – Check for ‘[Error]’ entries 4/opt/spirit/logging/spirit. log – sal-agent runtime log – Check for communications issues with SMGR 4/var/log/avaya/spirit. log – Conferencing components logs to this file (via rsyslog) – Lines in this file should be in the correct Avaya Common Logging Format (CLF) – All CLF lines should be forwarded to SMGR as a log and as an alarm Avaya – Proprietary. Use pursuant to Avaya policy. 41

AURA Conferencing Upgrading Standard Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. AURA Conferencing Upgrading Standard Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. 42

Upgrading Standard Using PLDS Back up of the configuration relevant data via System Manager Upgrading Standard Using PLDS Back up of the configuration relevant data via System Manager Console. Use System Platform to upgrade the template with the new version: Delete the currently active template Download the new template from PLDs Install the new template same as for a new installation Restore the configuration using System Manager Console. Avaya – Proprietary. Use pursuant to Avaya policy. 43

Upgrading Standard Edition Customer running existing MXEE which is less than 300 ports will Upgrading Standard Edition Customer running existing MXEE which is less than 300 ports will have an upgrade path to Standard Edition. The upgrade will be forklift so development will provide the instructions and scripts required to port data from each platform. In all cases new hardware will be required. Customer that are running 6. 0 Standard that plan to upgrade to the Enterprise Edition or future release will have the option to do so. The Existing license will continue to be valid. Avaya – Proprietary. Use pursuant to Avaya policy. 44

AURA Conferencing Enterprise Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. 45 AURA Conferencing Enterprise Edition TM Avaya – Proprietary. Use pursuant to Avaya policy. 45

Enterprise Solution Standard IBM 3550 M 2 / Avaya 8800 Conferencing applications installed on Enterprise Solution Standard IBM 3550 M 2 / Avaya 8800 Conferencing applications installed on separate servers. CRS, Web Portal, AWC Web Conferencing Servers require System Platform. Bridges software installed via standard ISO on dedicated hardware. All other applications installed via standard installers. All configuration handle through System Manager web interface. Avaya – Proprietary. Use pursuant to Avaya policy. 46

System Platform Templates for Enterprise Edition Enterprise uses template only for the following applications. System Platform Templates for Enterprise Edition Enterprise uses template only for the following applications. CRS Template containing the CRS contains: MS Windows 2008 Server , SQL 2008, Client Registration Server, Schapi Manager, CDRLoader, Sbill, Reports, Import Utility, DCSA, CRS Front End. Template containing the Web Portal and Audio Console contains: Web Portal / Audio Console Template Web Conferencing Template Linux, Web Scheduling, Web Administration / Configuration, Runtime Conference Roster for conference Monitoring and Control Template Containing the Web Conferencing contains: MS Windows 2008 Server, Web Collaboration Avaya – Proprietary. Use pursuant to Avaya policy. 47

ISO/Installers/Templates for Enterprise ISO OS Conferencing Enterprise Edition Bridge and Media Server Linux RHEL ISO/Installers/Templates for Enterprise ISO OS Conferencing Enterprise Edition Bridge and Media Server Linux RHEL 5 INSTALLERS OS Conferencing Enterprise Edition Web Conferencing Recording Server Conferencing Enterprise Edition Web Conferencing Playback Server Conferencing Enterprise Edition Conference Viewer Conferencing Microsoft Integration Server Conferencing Microsoft Outlook Integration Conferencing IBM Lotus Sametime Integration Conferencing IBM Lotus Notes Integration Conferencing Bridge Talk Conferencing Client Registration Server Front End Conferencing Application Programmer Interfaces Windows Templates OS Conferencing Enterprise Edition Client Registration Server Conferencing Enterprise Edition Web Portal with Audio Console Conferencing Enterprise Edition Web Conferencing Server Windows Windows Windows Linux RHEL 5 Windows Avaya – Proprietary. Use pursuant to Avaya policy. 48

Enterprise Edition Example Active Pyramid Stack, 2 media servers Standby Pyramid Stack, 2 media Enterprise Edition Example Active Pyramid Stack, 2 media servers Standby Pyramid Stack, 2 media servers System Manager Server Primary CRS Server Standby CRS Server Web Portal and Audio Console Server Avaya Web Conferencing (AWC) Server Conference Viewer Server Avaya – Proprietary. Use pursuant to Avaya policy. 49 49

Enterprise Edition Installation Avaya – Proprietary. Use pursuant to Avaya policy. 50 Enterprise Edition Installation Avaya – Proprietary. Use pursuant to Avaya policy. 50

Installing Enterprise Edition System Platform Templates 4 The installation of SP templates is done Installing Enterprise Edition System Platform Templates 4 The installation of SP templates is done exactly the same way as for Standard Edition 4 CRS template 4 Web Portal and Audio Console Template 4 AWC template 4 Templates for these machines will be available in PLDS 4 After doing the install, the Windows machine licenses will have to be activated ISO installer for the 6200 and Media Server ISO installation of MX Application and Media Server. Available in PLDS for download or available on CDs Single ISO will install the components required in the bridge Avaya – Proprietary. Use pursuant to Avaya policy. 51

Enterprise Edition Licensing Configuration Management Logging and Alarming Identical to Standard Edition Avaya – Enterprise Edition Licensing Configuration Management Logging and Alarming Identical to Standard Edition Avaya – Proprietary. Use pursuant to Avaya policy. 52

Enterprise Edition Upgrades Avaya – Proprietary. Use pursuant to Avaya policy. 53 Enterprise Edition Upgrades Avaya – Proprietary. Use pursuant to Avaya policy. 53

Upgrades from an Older release to MX 6. 0 Considerations 4 In a Pyramid Upgrades from an Older release to MX 6. 0 Considerations 4 In a Pyramid configuration, media servers can be upgraded first one at a time to eliminate the downtime, since calls will be automatically reallocated 4 If app server fail over is available the standby can be upgraded first, then fail over while the active is being upgraded, to reduce downtime to a maximum of 3 minutes 4 For Avaya Plug-ins, Outlook, MS, IBM…, the configurations are not copied across in an upgrade so they will have to be done manually 4 Upgrading from MX 5. 2 the hard disk will be formatted by the upgrade, so to roll back MX 5. 2 will have to be reinstalled, and the backed configuration applied. 4 Prior to Upgrading, a System Manager machine should be made available, the System Manager is required for the systems to get the license Avaya – Proprietary. Use pursuant to Avaya policy. 54

Upgrades from an Older release to 6. 0 Bridge Upgrade from 5. 2 4 Upgrades from an Older release to 6. 0 Bridge Upgrade from 5. 2 4 An IBM 3550 M 2 machine is required for Conferencing 6. 0 4 A script bridge-backup 52. sh will be provided to back up all the information from the 5. 2 bridge, which will be generated in some specific files 4 After 5. 2 is backed up, Install Aura Conferencing 6. 0 in the IBM 3550 M 2 TM 4 A script bridge-restore 52. sh will be provided to restore the specific backup files created by bridge-backup 52. sh into a 6. 0 installation 4 Start Conference 6. 0 from System Manager, it will take approximately 1 minute for all the processes to start 4 Certain configurations will not be restored automatically and will require manual intervention to apply them, the files required are backed by the bridge-backup 52. sh script 4 A roll back procedure will also be provided Avaya – Proprietary. Use pursuant to Avaya policy. 55

Upgrades from an Older release to MX 6. 0 CRS Upgrades from 5. 2 Upgrades from an Older release to MX 6. 0 CRS Upgrades from 5. 2 4 CRS in Conferencing 6. 0 runs in the system platform, it is also installed in new hardware, so the IBM 3550 M 2 should be available 4 System platform and the CRS template should be installed like it was a new installation 4 The MX 5. 2 SQL database would have to be moved from the Windows 2005 server to the Windows 2008 Server in 6. 0 4 Stop all applications in the CRS 4 Executing the command “Migrate. To. SQL 2008 export . MSSQLServer” in the MX 5. 3 machine will run a script that backs the database in the MX 5. 2 machine 4 Executing the command “Migrate. To. SQL 2008 import . SQLExpress” in the VM Avaya Conferencing 6. 0 machine will restore the database in the Virtual machine 4 Roll back is possible since we haven’t changed anything in the MX 5. 2 machine Other Apps Upgrades 4 The rest of the APPs won’t require any configuration back up, just remove the 5. 2 version and install the 6. 0 version 4 No data from the other applications need to be backed up Avaya – Proprietary. Use pursuant to Avaya policy. 56

Upgrading Enterprise Edition MX 6. 0 (Bridge) 4 To upgrade the Enterprise Edition system Upgrading Enterprise Edition MX 6. 0 (Bridge) 4 To upgrade the Enterprise Edition system there will be an upgrade RPM that will manage the binaries and configuration files to be replaced or merged. 4 The followings steps will be required to upgrade a Bare Metal Bridge: – Backup the bridge using the System Manager Console – Copy the Aura Conferencing Upgrade RPM to the bridge and run TM upgrade. sh – The script creates a backup copy of the changes so there is a script to roll back rollback. sh – After the upgrade is done, the configuration can be restore using the System Manger Console Avaya – Proprietary. Use pursuant to Avaya policy. 57

Upgrading Enterprise Edition Template Upgrades in Aura Conferencing 6. 0 TM 4 Using system Upgrading Enterprise Edition Template Upgrades in Aura Conferencing 6. 0 TM 4 Using system manager just back up the configuration of the template that we want to upgrade (CRS, WEB Portal, AWC) 4 Replace the older Aura. TM Conferencing template with the newer one using System Platform 4 Restore the configuration for that template Upgrading The CRS SQL Express Edition to Standard 4 The CRS template will be loaded with SQL 2008 Express Edition by default 4 If the Customer wants to upgrade the database to Standard Edition then new Microsoft licenses will have to be purchased 4 There will be a batch file based procedure to upgrade the database to the Standard Edition Upgrading System Platform and System Manager 4 There will be an upgrade procedure for the system manager server 4 It will be provided by the System Manager Team 4 It should be possible to upgrade System Platform without upgrading the Templates, although it is recommended to keep both SP, Templates, System Manager up to the same release for compatibility Avaya – Proprietary. Use pursuant to Avaya policy. 58

Upgrades from an Older release to MX 6. 0 Supported Upgrade Paths Upgrade Path Upgrades from an Older release to MX 6. 0 Supported Upgrade Paths Upgrade Path Upgrade Type Covered by Meeting Exchange 5. 2 Enterprise Edition GA Aura. TM Conferencing 6. 0 Enterprise Edition GA manual forklift upgrade Meeting Exchange Express Edition 2. 0 GA Aura. TM Conferencing 6. 0 Standard Edition GA manual forklift upgrade Aura. TM Conferencing 6. 0 Standard Edition GA Aura. TM Conferencing 6. 0 Enterprise Edition GA achieved via backup/restore from the System Manager Installer FS (CID 144495) Aura. TM Conferencing 6. 0 Enterprise Edition Beta Aura. TM Conferencing 6. 0 Enterprise Edition GA seamless upgrade via System Manager Installer FS (CID 144495) Aura. TM Conferencing 6. 0 Standard Edition Beta Aura. TM Conferencing 6. 0 Standard Edition GA seamless upgrade via System Manager Installer FS (CID 144495) Avaya – Proprietary. Use pursuant to Avaya policy. 59

thank you Ignacio Miranda igonzales@avaya. com +35312075614 Avaya – Proprietary. Use pursuant to Avaya thank you Ignacio Miranda [email protected] com +35312075614 Avaya – Proprietary. Use pursuant to Avaya policy. 60