1 / 60

LINK TO RECORDED PRESENTATION uconnect.demoavaya/p23768869/

LINK TO RECORDED PRESENTATION http://uconnect.demoavaya.com/p23768869/. CONFIDENTIAL& NOT TO BE DISCLOSED BEFORE JUNE 8TH. Avaya Aura TM Conferencing. Presenter: Ignacio Miranda. CONFIDENTIAL & NOT TO BE DISCLOSED BEFORE JUNE 8TH. Overview New Release Offering

osman
Download Presentation

LINK TO RECORDED PRESENTATION uconnect.demoavaya/p23768869/

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Avaya AuraTMConferencing Presenter: Ignacio Miranda CONFIDENTIAL & NOT TO BE DISCLOSED BEFORE JUNE 8TH

  3. Overview • New Release Offering • Enterprise Edition and Standard Edition • AuraTM Conferencing Standard Edition • Solution • Installation • Licensing • System Configuration Management • Solution Modeller • Logging and Alarming • Upgrades • AuraTM Conferencing Enterprise Edition • Solution • Installation • Licensing System Configuration Management • Solution Modeller • Logging and Alarming • Upgrades

  4. New Release Offering • Extends Avaya AuraTM integration through platform adoption – foundation application for enterprise communications • Simplifies administration and lowers cost of serviceability (Avaya AuraTM System manager, Avaya AuraTMSystem 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 web-based 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 4

  5. Standard VS Enterprise

  6. Standard VS Enterprise

  7. Standard VS Enterprise

  8. AuraTM Conferencing Standard Edition

  9. Standard Solution • Single server solution • Standard IBM 3550 M2 aka. Avaya S8800 • MX 6.0 S8800 Comcode is 700500427 • The orderable code is 229568 • Requires installation of System Platform ISO, provided via CD • System Platform ISO installs the CentOS, 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. 9

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

  11. Server Specification 11

  12. Avaya Aura™ Conferencing Standard Edition Installation Conferencing R&D

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

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

  15. AURATM Conferencing Licensing

  16. Licensing • Licensed Attributes

  17. Licensing • 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 • The Grace period will allow all components to operate as normal up to their maximum default value • Once the Grace Period expires the system will stop functioning • Once a valid license is retrieved from WebLM the components are configured as per the licensed and started • A valid license will never expire • The license is cached in the local system and will be updated only if new licenses are installed or de-installed in the WebLM server • In the case of a license failure an alarm and log statement will be raised • 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

  18. Licensing CRS Licensing • Pulls the Edition from the license, to know whether it is Enterprise or Standard • 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. • 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. • It manages how many users get a license internally • When the grace period finishes, the Users are still allowed to complete their session but no new sessions will be allowed WEB Portal Licensing • Query for VALUE_ACC_EDITION, to know if it is enterprise or standard • The distinction is just a formality, the software behaves the same way in standard and enterprise • During Grace Period Enterprise will be assumed • 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.

  19. Licensing Bridge Licensing • The Licence Proxy will retrieve the VALUE_ACC_AUDIO_PORTS and the VALUE_ACC_EDITION properties from the license server • The numChannels value in system.cfg will be populated with the VALUE_ACC_AUDIO_PORTS count prior to the processes start up • If the server edition is standard, only G.711 codecs will be allowed • 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 • 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

  20. Configuring system • View license details or installing a new license file • https://135.64.26.160/SMGR - admin/admin123 • 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

  21. Licensing License Installation GUI • Interface to install the license for the product • One single license for the product per site, with all the properties acquired by the customer

  22. AURATM Conferencing System Configuration Management

  23. Configuration Management • AuraTM Conferencing Element Manager will provide configuration pages to be able to setup the Bridge. • The configuration Manager will GET the configuration data for all the components • It Queries the bridge regularly and caches the information in the System Manager • Each component (Bridge, CRS, Web Portal….) continues to use their specific configuration files and databases, with their current specific formats. • The new configuration changes are verified before they are SET back to the components. • 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. • 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 • Manual changes could be made to the original configuration files (this is strongly discouraged) • Any changes made to the files will be picked by the Configuration Manager and displayed next time someone access the web pages

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

  25. Configuring system Adding Conferencing nodes bridge/crs/wp and AWC to the SMGR https://135.64.26.160/SMGR - admin/admin123 Navigate to Elements => Inventory => Manage Elements Add the 4 entities selecting Type Conferencing 6.0, committing changes each time 25

  26. Configuring system Useful information Accounts/passwords BRIDGE craft/craft01 – sroot/sroot01 CRS administrator/gatekeeper WP craft/craft01 – sroot/sroot01 AWC administrator/gatekeeper System Manager – root/root01 (shell) admin/admin123 (web) System Platform admin/admin01 Dom0 root/root01 26

  27. Avaya Aura™ Conferencing 6.0 Solution Modeller The replacement for EPW

  28. Avaya Aura™ Conferencing 6.0Solution Modeler Supports configuration of Bridge, CRS, AWC and Web Supports backward compatibility within a Major.Minori.e. within 6.0.?.?.? 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. 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 ModelerWe take the same Conferencing Element manager and package it in both Avaya Aura™ System Manager and Avaya Aura™ Conferencing 6.0 Solution Modeler 28

  29. Avaya Aura™ Conferencing 6.0Solution Modeller Solution Modeller takes the Conferencing EM and embeds it in a standalone web server that runs from a laptop. It is the same EM as bundled in System Manager therefore no issues with synchronization. Will provide some default models reflecting common configuration scenarios. Models can then be exported for subsequent import into the Conferencing Element Manager running in System Manager Importing a configuration exported from the Solution Modeller into System Manager will behave the same as importing a configuration from another System Manager. 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 Architecture Conferencing Element Manager System Manager IPTCM Element Manager Session Manager Element Manager Conferencing 6.0 Solution Modeller Conferencing Element Manager Conferencing Element Manager Solution Modeller UI SFS Element Manager Default Models Presence Element Manager 29

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

  31. Avaya Aura™ Conferencing 6.0Solution Modeller On start up it shows an application window with buttons to exit and to launch a browser (as it listens on a random port) The application can only be accessed from the computer on which it is running. Avaya AuraTM Conferencing 6.0 Solution Modeller Avaya Aura™ Conferencing 6.0 Solution Modeller 31

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

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

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

  35. Avaya Aura™ Conferencing 6.0Solution Modeller When the model is ready, you export the configuration from the Conferencing Element Manager 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. 35

  36. Avaya Aura™ Conferencing 6.0Solution Modeller When the servers arrive on site, you import the configuration into System Manager: Then you need to resolve the IP addresses from the model against the IP addresses of the servers you actually have deployed • 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 36

  37. AURATM CONFERENCING Logging and Alarming for Conferencing

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

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

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

  41. debugging – files on bridge: • /var/log/avaya/spirit.config.log • sal-agent initialization log • Check for ‘[Error]’ entries • /opt/spirit/logging/spirit.log • sal-agent runtime log • Check for communications issues with SMGR • /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

  42. AURATM Conferencing Upgrading Standard Edition

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

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

  45. AURATM Conferencing Enterprise Edition

  46. Enterprise Solution • Standard IBM 3550 M2 / 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. 46

  47. System Platform Templates for Enterprise Edition • Enterprise uses template only for the following applications. CRS Template 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: Linux, Web Scheduling, Web Administration / Configuration, Runtime Conference Roster for conference Monitoring and Control Web Portal / Audio Console Template Web Conferencing Template Template Containing the Web Conferencing contains: MS Windows 2008 Server, Web Collaboration 47

  48. ISO/Installers/Templates for Enterprise 48

  49. Enterprise Edition Example Active Pyramid Stack, 2 media servers Single Management Point 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 49

  50. Enterprise Edition Installation

More Related