Avaya Solutions Platform 4200 Series Solution Description
Release 4.1.0.1 Issue 1 September 2020 © 2019-2020, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED Notice SERVICE. While reasonable efforts have been made to ensure that the Licenses information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED “Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (“AVAYA”). necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order pages. documentation does not expressly identify a license type, the Warranty applicable license will be a Designated System License as set forth below in the Designated System(s) License (DS) section as Avaya provides a limited warranty on Avaya hardware and software. applicable. The applicable number of licenses and units of capacity Refer to your sales agreement to establish the terms of the limited for which the license is granted will be one (1), unless a different warranty. In addition, Avaya’s standard warranty language, as well as number of licenses or units of capacity is specified in the information regarding support for this product while under warranty is documentation or other materials available to You. “Software” means available to Avaya customers and other parties through the Avaya computer programs in object code, provided by Avaya or an Avaya Support website: https://support.avaya.com/helpcenter/ Channel Partner, whether as stand-alone products, pre-installed on getGenericDetails?detailId=C20091120112456651010 under the link hardware products, and any upgrades, updates, patches, bug fixes, “Warranty & Product Lifecycle” or such successor site as designated or modified versions thereto. “Designated Processor” means a single by Avaya. Please note that if You acquired the product(s) from an stand-alone computing device. “Server” means a set of Designated authorized Avaya Channel Partner outside of the United States and Processors that hosts (physically or virtually) a software application Canada, the warranty is provided to You by said Avaya Channel to be accessed by multiple users. “Instance” means a single copy of Partner and not by Avaya. the Software executing at a particular time: (i) on one physical “Hosted Service” means an Avaya hosted service subscription that machine; or (ii) on one deployed software virtual machine (“VM”) or You acquire from either Avaya or an authorized Avaya Channel similar deployment. Partner (as applicable) and which is described further in Hosted SAS License types or other service description documentation regarding the applicable hosted service. If You purchase a Hosted Service subscription, the Designated System(s) License (DS). End User may install and use foregoing limited warranty may not apply but You may be entitled to each copy or an Instance of the Software only: 1) on a number of support services in connection with the Hosted Service as described Designated Processors up to the number indicated in the order; or 2) further in your service description documents for the applicable up to the number of Instances of the Software as indicated in the Hosted Service. Contact Avaya or Avaya Channel Partner (as order, Documentation, or as authorized by Avaya in writing. Avaya applicable) for more information. may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other Hosted Service specific designation, or to be provided by End User to Avaya through THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA electronic means established by Avaya specifically for this purpose. HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA Heritage Nortel Software CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA “Heritage Nortel Software” means the software that was acquired by WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER Avaya as part of its purchase of the Nortel Enterprise Solutions THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH Business in December 2009. The Heritage Nortel Software is the SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE software contained within the list of Heritage Nortel Products located APPLICABLE TO ANYONE WHO ACCESSES OR USES THE at https://support.avaya.com/LicenseInfo under the link “Heritage HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED Nortel Products” or such successor site as designated by Avaya. For SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON Heritage Nortel Software, Avaya grants Customer a license to use BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Heritage Nortel Software provided hereunder solely to the extent of DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY the authorized activation or authorized usage level, solely for the AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF purpose specified in the Documentation, and solely as embedded in, YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A for execution on, or for communication with Avaya equipment. COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT Charges for Heritage Nortel Software may be based on extent of YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE activation or use authorized as specified in an order or invoice. TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF Copyright PARTNER ACKNOWLEDGES AND AGREES THE AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL Except where expressly stated otherwise, no use should be made of RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC materials on this site, the Documentation, Software, Hosted Service, IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE or hardware provided by Avaya. All content on this site, the FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES documentation, Hosted Service, and the product provided by Avaya IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I) including the selection, arrangement and design of the content is ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD owned either by Avaya or its licensors and is protected by copyright (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS and other intellectual property laws including the sui generis rights ENCODED BY A CONSUMER ENGAGED IN A PERSONAL relating to the protection of databases. You may not modify, copy, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER reproduce, republish, upload, post, transmit or distribute in any way LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED any content, in whole or in part, including any code and software OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL unless expressly authorized by Avaya. Unauthorized reproduction, INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS transmission, dissemination, storage, and or use without the express MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP:// written consent of Avaya can be a criminal, as well as a civil offense WWW.MPEGLA.COM. under the applicable law. Compliance with Laws Virtualization You acknowledge and agree that it is Your responsibility for The following applies if the product is deployed on a virtual machine. complying with any applicable laws and regulations, including, but not Each product has its own ordering code and license types. Unless limited to laws and regulations related to call recording, data privacy, otherwise stated, each Instance of a product must be separately intellectual property, trade secret, fraud, and music performance licensed and ordered. For example, if the end user customer or rights, in the country or territory where the Avaya product is used. Avaya Channel Partner would like to install two Instances of the same type of products, then two products of that type must be Preventing Toll Fraud ordered. “Toll Fraud” is the unauthorized use of your telecommunications Third Party Components system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your “Third Party Components” mean certain software programs or company's behalf). Be aware that there can be a risk of Toll Fraud portions thereof included in the Software or Hosted Service may associated with your system and that, if Toll Fraud occurs, it can contain software (including open source software) distributed under result in substantial additional charges for your telecommunications third party agreements (“Third Party Components”), which contain services. terms regarding the rights to use certain portions of the Software (“Third Party Terms”). As required, information regarding distributed Avaya Toll Fraud intervention Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third If You suspect that You are being victimized by Toll Fraud and You Party Components and the Third Party Terms that apply is available need technical assistance or support, call Technical Service Center in the products, Documentation or on Avaya’s website at: https:// Toll Fraud Intervention Hotline at +1-800-643-2353 for the United support.avaya.com/Copyright or such successor site as designated States and Canada. For additional support telephone numbers, see by Avaya. The open source software license terms provided as Third the Avaya Support website: https://support.avaya.com or such Party Terms are consistent with the license rights granted in these successor site as designated by Avaya. Software License Terms, and may contain additional rights benefiting Security Vulnerabilities You, such as modification and distribution of the open source software. The Third Party Terms shall take precedence over these Information about Avaya’s security support policies can be found in Software License Terms, solely with respect to the applicable Third the Security Policies and Support section of https:// Party Components to the extent that these Software License Terms support.avaya.com/security. impose greater restrictions on You than the applicable Third Party Suspected Avaya product security vulnerabilities are handled per the Terms. Avaya Product Security Support Flow (https:// The following applies only if the H.264 (AVC) codec is distributed with support.avaya.com/css/P8/documents/100161515). the product. THIS PRODUCT IS LICENSED UNDER THE AVC Downloading Documentation PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE For the most current versions of Documentation, see the Avaya REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH Support website: https://support.avaya.com, or such successor site THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC as designated by Avaya. VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A Contact Avaya Support PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS See the Avaya Support website: https://support.avaya.com for GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. product or Hosted Service notices and articles, or to report a problem ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, with your Avaya product or Hosted Service. For a list of support L.L.C. SEE HTTP://WWW.MPEGLA.COM. telephone numbers and contact addresses, go to the Avaya Support website: https://support.avaya.com (or such successor site as Service Provider designated by Avaya), scroll to the bottom of the page, and select THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S Contact Avaya Support. HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT Trademarks OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE The trademarks, logos and service marks (“Marks”) displayed in this PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM site, the Documentation, Hosted Service(s), and product(s) provided THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S by Avaya are the registered or unregistered Marks of Avaya, its HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN affiliates, its licensors, its suppliers, or other third parties. Users are WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE not permitted to use such Marks without prior written consent from OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING Avaya or such third party which may own the Mark. Nothing BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, contained in this site, the Documentation, Hosted Service(s) and THE AVAYA CHANNEL PARTNER IS REQUIRED TO product(s) should be construed as granting, by implication, estoppel, INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE or otherwise, any license or right in and to the Marks without the AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, express written permission of Avaya or the applicable third party. DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. Avaya is a registered trademark of Avaya Inc. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL All non-Avaya trademarks are the property of their respective owners. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Contents
Chapter 1: Introduction...... 7 Purpose...... 7 Product registration...... 7 Warranty...... 7 Chapter 2: New in this Release...... 9 New in this release...... 9 Chapter 3: Avaya Solutions Platform 4200 Overview...... 11 Solution purpose...... 11 Solution benefits...... 11 Avaya Solutions Platform 4200 series platform infrastructure...... 12 Physical and virtual Avaya Solutions Platform 4200 series infrastructure...... 13 Avaya Solutions Platform 4200 series deployment options...... 16 Avaya Solutions Platform 4200 series High Availability...... 16 Chapter 4: Avaya Solutions Platform 4200 Components...... 19 Physical specifications and environmental requirements...... 19 Avaya Solutions Platform 4200 series component list...... 23 Phone firmware versions...... 28 Chapter 5: Hardware Component Description...... 29 Avaya Solutions Platform 4200 series hardware components...... 29 Networking switches...... 29 Compute servers...... 31 Storage...... 31 Power Distribution Units and AC plugs...... 31 Fan cooling...... 33 Avaya Media Gateway...... 34 Optional hardware components...... 34 Chapter 6: Software Component Description...... 36 Application component descriptions...... 36 Software and virtual appliances...... 36 Virtualization applications...... 39 Management applications...... 39 Avaya Aura® Virtualized Environment applications...... 41 Contact Center applications...... 45 Additional appliances...... 48 Chapter 7: Avaya Solutions Platform 4200 Common Network Architecture...... 49 Avaya Solutions Platform 4200 series common network architecture...... 49 Avaya Fabric Connect...... 49 Routing...... 49 Connectivity and VLANs...... 49
September 2020 Avaya Solutions Platform 4200 Series Solution Description 5 Comments on this document? [email protected] Contents
External network...... 53 Multiple rack configuration...... 56 Single instance and multiple instance Avaya Solutions Platform 4200 series...... 56 Multiple Data Center network...... 59 Supported interconnection options...... 64 Storage array expansion...... 66 Chapter 8: Best Practices...... 68 Networking best practices...... 68 Link to a regular customer router...... 68 SPBm to the customer router...... 70 VMware best practices...... 71 VMware networking best practices...... 71 Thin vs. thick deployments...... 72 VMware Tools...... 73 VMware Snapshots...... 73 Resource reservation...... 74 Chapter 9: Resources...... 76 Documentation...... 76 Finding documents on the Avaya Support website...... 77 Avaya Documentation Center navigation...... 78 Training...... 79 Avaya Mentor videos...... 79 Support...... 80 Using the Avaya InSite Knowledge Base...... 80
September 2020 Avaya Solutions Platform 4200 Series Solution Description 6 Comments on this document? [email protected] Chapter 1: Introduction
Purpose This document describes an overview, components, architecture, and best practices for Avaya Solutions Platform 4200 series. Avaya Solutions Platform 4200 series was formerly called Avaya Converged Platform 4200, Avaya Pod Fx, and Avaya Collaboration Pod. This document is intended for professionals who requires an overview of Avaya Solutions Platform 4200 series features and specifications.
Product registration To prevent service interruption, you must register your Avaya Solutions Platform products. Following are the available methods for product registration: • Implementation as a service: If Avaya Professional Services provided implementation services on site, Avaya Professional Services also performs product registration on your behalf. • Avaya Partner and Customer implementation: For information about the step-by-step registration process, see the Avaya Classic Global Registration Process Help Document on the Avaya Product Support Registration page. The document ID is 100162279. Product registration is a required element for effective Avaya customer support. You must follow the Partner and Customer Guidance in the Avaya Global Registration Process to help ensure the seamless support you have come to expect from Avaya.
Warranty Avaya provides a limited warranty on its hardware and software (“Product(s)”). Refer to your sales agreement to establish the terms of the limited warranty.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 7 Comments on this document? [email protected] Introduction
In addition, Avaya standard warranty, as well as information regarding support for this Product while under warranty, is available to Avaya customers and other parties through the Avaya Support website: www.avaya.com/support. Simply type your search into the Search Avaya Support dialog box. Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Example In the Search Avaya Support dialog box, type warranty. Then select the appropriate topic from the drop-down list.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 8 Comments on this document? [email protected] Chapter 2: New in this Release
New in this release The section describes what is new in the Avaya Solutions Platform 4200 series Release 4.1.0.1. Support for HPE ProLiant DL360 Gen 10 V2 compute server Avaya Solutions Platform 4200 series Release 4.1.0.1 utilizes the HPE ProLiant DL360 Gen 10 V2 compute servers with Dual Intel(R) Xeon(R) Gold 6226R CPU @2.90GHz, providing 32 Cores/64 threads/server using Cascade Lake architecture. HPE Gen 10 v2 Servers do not come with the HPE Ethernet 1Gb 4-port 331i Network Adapter. All servers are pre-installed with VMware Hypervisor ESXi 6.5 P05- Build 16576891. Support for Solution Deployment Manager Avaya Solutions Platform 4200 series Release 4.1.0.1 continues to support integration with Solution Deployment Manager and System Manager. Vulnerability fixes The Avaya Solutions Platform 4200 series Release 4.1.0.1 provides applicable patches from our vendors that includes vulnerability fixes for BIOS and firmware updates for HPE ProLiant DL360 Gen 8, HPE ProLiant DL360 Gen 9, HPE ProLiant DL360 Gen 10 servers, VMware vCenter, vSphere hypervisor, and Avaya Aura applications. Support for Avaya Orchestrator The Avaya Orchestrator Release 1.5 build 45 is a visualization and management application which is used to monitor Avaya Solutions Platform 4200 series Release 4.1.0.1. Starting with Avaya Converged Platform 4200 series Release 4.0 and later, Avaya Orchestrator replaces the POD Orchestration Suite that is end-of-sale with Avaya Pod Fx Release 3.1. Avaya Orchestrator performs the following operations: • Works in conjunction with the SAL Gateway to monitor and escalate product alarms and notifications across all the Avaya Solutions Platform 4200 series infrastructure hardware. • Produces real-time and historical reporting tools for customized means to review solution state of health. • Provides a single dashboard view for monitoring state of health of all Avaya Solutions Platform 4200 series racks, components, and services. • Sends email notifications for product alarm escalations. • Provides consistent proactive monitoring of all administered components.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 9 Comments on this document? [email protected] New in this Release
• For the Avaya Orchestrator. Release 1.5, software applications will continue to have alarms supported through the SAL gateway. Software alarm support will be available in a later release. For more information on Avaya Orchestrator, see Configuring and using Avaya Orchestrator. Filler panels The Avaya Solutions Platform 4200 series Release 4.1.0.1 provides 3 unit perforated metal branded filler panel for branded enclosure models.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 10 Comments on this document? [email protected] Chapter 3: Avaya Solutions Platform 4200 Overview
Solution purpose Avaya Solutions Platform 4200 series is a cloud-ready, turnkey solution designed to simplify installation and operations of real-time applications as cloud services. Avaya Solutions Platform 4200 series is a secure enclosed rack that contains the basic hardware and software components required to support a converged solution and is available in several packaged configurations to support a range of business needs. The Avaya Solutions Platform 4200 series infrastructure provides a convenient deployment model for virtualized services and solutions. Many Avaya Solutions Platform 4200 series configurations meet customers needs and the infrastructure is pre-built and pre-tested before delivery to the customer site to simplify the design and implementation for the customer. Avaya Solutions Platform 4200 series is targeted at large enterprises and service providers.
Solution benefits Avaya Solutions Platform 4200 series infrastructure and converged solutions can reduce time spent by your technicians integrating and maintaining unrelated components, so you can recognize the benefits of new technologies more rapidly. These time savings allow your IT department to focus on other priorities to further improve your business. The Avaya Solutions Platform 4200 series infrastructure can greatly reduce the cost and complexity of creating a converged solution. An Avaya System Integrator can deploy additional applications to create a supported converged solution. Avaya Solutions Platform 4200 series is more flexible than other converged solutions, in part because of the Network Management System, virtualized applications, Avaya Virtual Services Platform networking components, and expansion options. When server capacity requirements exceed the current capabilities in the Avaya Solutions Platform 4200 series, you can add extra servers. Adding extra servers increases the overall capacity and provides additional compute power for more applications to be served. The Avaya Solutions Platform 4200 series supports from two to five servers.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 11 Comments on this document? [email protected] Avaya Solutions Platform 4200 Overview
Storage arrays can be expanded to provide additional application and recording storage. Avaya Solutions Platform 4200 series • Enables virtualization. Virtualization reduces the number of servers and thereby reduces capital equipment costs, physical space, power consumption and cooling needs. • Provides management tools. The Network Management System allows easy configuration and monitoring of the solution components. • Accelerates deployment. Avaya Solutions Platform 4200 series is pre-configured with all components integrated and infrastructure applications pre-deployed. • Reduces cost by reducing complexity. Some site preparation might be all that is required at your site. • Includes industry-leading technology. Avaya technology and third party vendors converge in a purpose-built Avaya Solutions Platform 4200 series fully tested for compatibility.
Avaya Solutions Platform 4200 series platform infrastructure The following table identifies some of the hardware differences between the platforms. Avaya Solutions Platform 4200 series Extension rack Yes Maximum RMU Avaya enclosure–42 RMU Maximum compute servers Up to power capacity Maximum storage array expansion Supports expansion using up to 2 ES2-H expansion shelves. Enclosure types Avaya-branded enclosures (42 RMU): • 42” deep enclosure • 48” deep enclosure
Note: The measurement does not include front and back doors. Delivery frame option No Switch and Gateway direction Rear facing
Note: Avaya Solutions Platform 4200 series Release 4.1.0.1 supports preexisting hardware infrastructure for: • Release 2.x with the exception of Lenovo servers.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 12 Comments on this document? [email protected] Physical and virtual Avaya Solutions Platform 4200 series infrastructure
For the supported hardware of the Release 2.x, refer to the interoperability table available at https://downloads.avaya.com/css/P8/documents/101070354. • Release 3.x and later. Component software can be upgraded to the Release 4.1.0.1 baseline. Avaya Solutions Platform 4200 series Release 4.1.0.1 new system builds provide the following infrastructure components: Avaya Solutions Platform 4200 series infrastructure: • Compute - HPE ProLiant DL360 G10 V2 –Dual Intel(R) Xeon(R) Gold 6226R CPU @2.90GHz, providing 32 Cores/64 threads/server with 2 x 10–gigabit Ethernet (GbE) ports, Model description HPE FlexFabric 10Gb 2-port, SFP+ 534FLR Adaptor - VMware 6.5 P05- Build 16576891 ESXi host virtualization platform Operating System (on all compute servers) • Networking - Extreme VSP 7254XSQ network aggregation switches (2 switches) • Storage - HPE Nimble CS1000 storage array • Optional hardware - Avaya G450 Media Gateways - Avaya Session Border Controllers - Avaya Scopia MCU • Enclosure, power, cooling - Avaya-branded 42” or 48” deep enclosure option - Switched Power Distribution Units (1 to 3 PDU pairs in an enclosure) - 12 cooling fan assemblies on rear enclosure doors (24 fans) • Infrastructure Applications - VMware vCenter 6.5 Update 3k - Build 16613358 - Avaya Orchestrator Release 1.5 Build 45 - Avaya Aura® Release 8.1.x For more information, see Avaya Solutions Platform 4200 series component list on page 23.
Physical and virtual Avaya Solutions Platform 4200 series infrastructure
September 2020 Avaya Solutions Platform 4200 Series Solution Description 13 Comments on this document? [email protected] Avaya Solutions Platform 4200 Overview
The following diagrams depict the physical and virtual nature of Avaya Solutions Platform 4200 series. These diagrams are examples only.
Figure 1: Physical infrastructure
September 2020 Avaya Solutions Platform 4200 Series Solution Description 14 Comments on this document? [email protected] Physical and virtual Avaya Solutions Platform 4200 series infrastructure
Figure 2: Virtual environment infrastructure
Depending on the configuration of your Avaya Solutions Platform 4200 series, additional VMs may be required. For more information on the software available for Avaya Solutions Platform 4200 series, refer to Software and Virtual Appliances on page 36.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 15 Comments on this document? [email protected] Avaya Solutions Platform 4200 Overview
Avaya Solutions Platform 4200 series deployment options Avaya Solutions Platform 4200 series deployment options Avaya Solutions Platform 4200 series arrives at the customer site completely assembled and loaded with software. The Avaya-branded enclosure is a 42 Rack Mount Unit (RMU) with all Avaya Solutions Platform 4200 series components placed in a way that allows for future expansion or for the customer to install their own equipment within the same rack. Avaya Solutions Platform 4200 series includes active cooling and power distribution units (when ordered with Avaya-branded enclosure). The Avaya-branded enclosure is available in two sizes, 42” depth and 48” depth (excluding doors), each size having a different power capacity. When a customer orders Avaya Solutions Platform 4200 series with the Avaya-branded enclosure, all components, including cooling and power supplies, are assembled within the enclosure at the Avaya manufacturing facility then shipped directly to the customer site.
Avaya Solutions Platform 4200 series High Availability The Avaya Solutions Platform 4200 series High Availability (HA) architecture provides both software resiliency and hardware redundancy features to ensure continuous operation with the elimination of scheduled downtime. Scheduled downtime is usually the result of some management-initiated event which can include patches to system software that require a reboot, or system configuration changes that only take effect upon a reboot. Unscheduled downtime is generally caused by some physical event, such as a hardware or software failure, or environmental anomalies including power outages. To minimize any sort of downtime the Avaya Solutions Platform 4200 series core infrastructure, core applications, and management software can provide 99.999% platform availability. The High Availability architecture allows for a redundant component failover within milliseconds. Avaya Solutions Platform 4200 series core infrastructure availability includes hardware, VMware ESXi, Storage Area Network, and networking services. Avaya Solutions Platform 4200 series core infrastructure availability does not include the following: • Application software such as CM, SM, SMGR, ACM, US, PS, ACR and WFO — many applications are not considered core and the network can operate without them (for example, calls may continue, or new calls may be established without call recording or without Presence Services). • Access portion — includes phones, line side, G450s, AAMS, SBCs. Avaya Solutions Platform 4200 series provides the following multiple layers of redundancy to ensure High Availability:
September 2020 Avaya Solutions Platform 4200 Series Solution Description 16 Comments on this document? [email protected] Avaya Solutions Platform 4200 series High Availability
Hardware redundancy Avaya Solutions Platform 4200 series provides redundant Power Distribution Units (PDU), compute servers, network switches, and storage architecture that allows for continued operation if a component fails. Compute servers, network switches, and storage systems are also configured with redundant power supplies, connected to redundant PDUs to provide separation of power sources. Any single component failure has no effect on the operating Avaya Solutions Platform 4200 series. Avaya highly recommends to replace the failed unit as soon as possible. The act of replacing the unit has no effect on Avaya Solutions Platform 4200 series operation. The following table shows the Mean Time to Failure (MTTF) and Mean Time to Repair (MTTR) of individual hardware components.
Table 1: MTTF and MTTR of hardware components
Single failure MTTF MTTR Compute Servers 216,557 h <1ms VSP 7200 Series switches 162,857 h <1ms PDU 100.000 h <1ms
For information about the storage area network MTTF and MTTR, see www.nimblestorage.com.
Avaya Solutions Platform 4200 series can be configured with additional redundant components, such as G450 Media Gateways and Session Border Controllers. Network redundancy Avaya Solutions Platform 4200 series provides a redundant networking switch architecture. Multiple standalone switches provide redundant internal and external network connections. For more information, see Networking switches on page 29. VMware redundancy Avaya Solutions Platform 4200 series provides VMware redundancy with multiple compute server ESXi hosts in a High Availability cluster configuration. VMware High Availability cluster can provide vMotion, and Dynamic Resource Scheduler (DRS) resiliency features within Avaya Solutions Platform 4200 series. For more information, see Multiple Data Centers, Multiple Avaya Solutions Platform 4200 series systems, and VMware clusters on page 61. Avaya Aura® platform redundancy Avaya Solutions Platform 4200 series combines existing Avaya Aura® platform High Availability functionality and VMware High Availability functionality to deliver increased reliability and resiliency for redundant local server configurations and geographic redundant configurations. The survivability options in Avaya Aura® combined with the system resource management features in VMware ensure High Availability on the Avaya Aura® platform. Avaya Aura® platform redundancy provides Communication Manager software duplication and Session Manager active-active redundancy (CM1/CM2 and SM1/SM2). For example, in the event of a compute server ESXi host failure, the secondary Communication Manager becomes the active Communication Manager and the secondary instance of Session
September 2020 Avaya Solutions Platform 4200 Series Solution Description 17 Comments on this document? [email protected] Avaya Solutions Platform 4200 Overview
Manager takes over call processing and routing. The VMware DRS rules are used to create backup instances of Communication Manager and Session Manager whenever a failover to a secondary compute server occurs. To maintain reliability and redundancy, VMware vMotion migrates the Communication Manager instances and Session Manager instances to a separate host. Geographic redundancy The Avaya Solutions Platform 4200 series architecture supports multiple Avaya Solutions Platform 4200 series units in geographic redundant architectures, which also includes multiple data center configurations. To support multisite geographic redundancy, you can enable Enterprise Survivable Server (ESS) mode on Communication Manager, System Manager Geographic Redundancy, supplementary Session Managers, supplementary Media Gateways, and the Avaya Fabric Connect technology for a complete Avaya Aura® redundant system.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 18 Comments on this document? [email protected] Chapter 4: Avaya Solutions Platform 4200 Components
Physical specifications and environmental requirements This section describes basic specifications and environmental requirements for Avaya Solutions Platform 4200 series. Use the specifications to help determine if your site requires additional preparation or equipment to physically accommodate and safely operate the Avaya Solutions Platform 4200 series. The Avaya Solutions Platform 4200 series purchasing process involves a detailed assessment checklist. The following checklist helps to identify any additional site preparation necessary for the installation of Avaya Solutions Platform 4200 series. Specifications for Avaya Solutions Platform 4200 series The following table describes the physical specifications and environmental requirements for Avaya Solutions Platform 4200 series.
Table 2: Environmental requirements
Parameter Value Input voltage Range: 208 – 240 VAC For example: • 210 VAC in North America • 240 VAC in Europe Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 19 Comments on this document? [email protected] Avaya Solutions Platform 4200 Components
Parameter Value Power input cords – supply power from Single phase PDUs. your power supply to the power PDUs are 208 – 240 VAC. distribution units (PDU) PDUs have 15 ft (5 m) power input cords, the cable and plug varies depending on PDU and geographic requirements. PDU Description 30 Ampere (A) The AC input cords are hard-wired on the PDU with the following plug: • NEMA L6-30P, Twistlock 32 A The AC input cords are hard-wired on the PDU with the following plug: • IEC 60309 (CEE 17 / BS 4343) Blue (32 A rated) PDUs for an Avaya-branded enclosure PDUs are combined in matching pairs: one primary and one redundant. Three pairs of PDUs are available depending on customer options. Although the PDUs are fused, they do not have ON/OFF features.
Important: You must supply an ON/OFF breaker at your site. Current rating System current rating is determined by the model of PDUs ordered. Each Avaya Solutions Platform 4200 series is typically equipped with multiple pairs of 30 A, or 32 A PDUs (not mixed). Electrical connections from your power Up to six approved wall receptacles with a single phase 208 – supply for the power input cords 240 voltage, with capacity to support the required amperage, with an outlet compatible with the PDUs and your electrical jurisdiction. The number and type of receptacles you need is equal to the number and type of PDUs equipped. Ensure the outlet is compatible with the PDU input plug. Power input cords can be routed to exit above or below the enclosure. Maximum safe power delivery using 6 15,000 W for a 30 A or 32 A system. power distribution units (three primary, three standby) Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 20 Comments on this document? [email protected] Physical specifications and environmental requirements
Parameter Value Ground connections for the Avaya Each Avaya Solutions Platform 4200 series enclosure has one Solutions Platform 4200 series ground lug connection available on the rear. The enclosure to site ground wire must be provided by an electrical contractor or telecommunications technician. • See ANSI/TIA-607–B Standard and your local building and wiring laws and codes for your region. • Follow local, UL, and FCC codes when selecting ground wire gauge. • Ground resistance of 2 ohm or less for the enclosure ground lug to site ground connection. • Minimum 6 AWG single core ground wire. Always consult local building wiring and codes for your required ground specifications.
Note: Each G450 Media Gateway in Avaya Solutions Platform 4200 series must be individually grounded using the provided gateway ground connector if the G450 Media Gateway is equipped with any additional cards other than T1/E1 cards. Enclosure airflow Front-to-back airflow direction. Operating temperature range (ambient Avaya-branded enclosure –10 °C to 35 °C inlet temperature) Customer-provided enclosure –10 °C to 30 °C Thermal output Maximum 21,500 BTU Relative humidity range 20% to 80% non condensing Storage temperature –5 °C to 60 °C Avaya-branded enclosure: Maximum weight ~2,000 pounds (909 kg) Unit weight with all required and optional Enclosure weight capacity ~2,200 pounds (1,000 kg) hardware components Note: Weight of 42U shipping crate with pallet: ~400 pounds (181 kg) Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 21 Comments on this document? [email protected] Avaya Solutions Platform 4200 Components
Parameter Value Avaya-branded enclosure: Avaya-branded 48” deep Gray enclosure: Overall dimensions • Height: 42 RMU – 81 in. (206 cm) with casters • Width: 24 in. (61 cm) • Depth: 52 in. (133 cm) (includes additional space afforded by convex front door panel) Avaya-branded 48” deep Black enclosure: • Height: 81 in. (206 cm) • Width: 24 in. (61 cm) • Depth: 48 in.
Note: Dimensions of 42U shipping crate with pallet: 88 5/8 in. (225 cm) x 43 4/8 in. (110.5 cm) x 62 7/8 in. (158 cm). Avaya-branded enclosure: • Front: 48 in. (122 cm) minimum Clearance required • Rear: 36 in. (92 cm) minimum • Sides: 0 in. (0 cm) minimum • Top: 12 in. (31 cm) minimum Avaya-branded enclosure: Danger: Casters – rolling type You must ensure that you install your Avaya Solutions Adjustable leveling legs, threaded Platform 4200 series on a flat, level surface. Adjustable leveling legs – To prevent sudden, unplanned movement of Avaya Solutions Platform 4200 series after it is in place, you must ensure that the leveling legs properly engage (wound all the way down so that the Avaya Solutions Platform 4200 series is not resting on the casters and cannot roll).
The following diagram provides dimensions for the bottom base of the 48 inch Avaya-branded enclosure.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 22 Comments on this document? [email protected] Avaya Solutions Platform 4200 series component list
Figure 3: Avaya-branded 48” enclosure base dimensions
The following diagram provides dimensions for the bottom base of the 42 inch Avaya-branded enclosure.
Figure 4: Avaya-branded 42” enclosure base dimensions
Note: Avaya Solutions Platform 4200 series enclosures have four casters. Two fixed casters in the front (on the left in the diagrams above) that move forward and backward only and two casters in the rear (on the right in the diagrams above) that freely swivel in any direction.
Avaya Solutions Platform 4200 series component list The following table summarizes the hardware and software components that can form the Avaya Solutions Platform 4200 series for the current release.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 23 Comments on this document? [email protected] Avaya Solutions Platform 4200 Components
Note: If your Avaya Solutions Platform 4200 series was upgraded from a prior release, check the Bill of Materials (BOM) from your order to verify the hardware and software on your system. Component quantities and specific details depend on the Bill of Materials (BOM) generated from a specific Avaya Solutions Platform 4200 series order. For information about Avaya and third-party hardware and software release versions supported on Avaya Solutions Platform 4200 series, see Avaya Solutions Platform 4200 series Baseline.
Table 3: Default and optional components
Component Description Avaya-branded enclosure 42-inch Avaya-branded enclosure: 48-inch Gray Avaya-branded types for Avaya Solutions enclosure: • 24” width x 42” depth x 81” height Platform 4200 series: • 24” width x 51.6” depth x 81” • Depth measurement does not • 42-inch (107 cm) deep height include handles enclosure • Depth measurement includes front • Color: black • 48-inch (122 cm) deep and rear doors, and handles enclosure • Avaya-branded flat front door with • Color: gray lock Note: • Avaya-branded curved front door Fully assembled Avaya with lock Solutions Platform • Split rear door with lock 4200 series enclosures ship with the doors 48-inch Black Avaya-branded unlocked. Keys are enclosure: zip-tied to the inside of • 24” width x 48” depth x 81” height the front door. • Depth measurement does not include doors and handles. • Color: Black • Avaya-branded flat front door with lock Maximum total Rack Mount Avaya Solutions Platform 4200 series: Unit (RMU) • 42- or 48- inch Avaya-branded enclosure: 42 RMU • Extension rack: 42 RMU Extension racks provide additional resources and physical space for devices or appliances, which are necessary for some Avaya Solutions Platform 4200 series solutions. Component placement Avaya Solutions Platform 4200 series: (device direction) • Avaya-branded enclosure—front or rear • Customer-provided enclosure—front or rear Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 24 Comments on this document? [email protected] Avaya Solutions Platform 4200 series component list
Component Description Power: 42-inch deep Avaya-branded 48-inch deep Avaya-branded enclosure: enclosure: Power Distribution Units (PDU): • Main rack: • Main rack: • Vertical PDUs for: - Up to four (two pairs) 30 A or 32 - Up to six (three pairs) 30 A or 32 A PDUs, delivering a total of A PDUs, delivering a total of - Main racks 10,000 Watts for two PDU pairs. 15,000 Watts. - Vertical Extension racks - Up to four (two pairs) 30 A or 32 - Up to six (three pairs) 30 A or 32 (30 A and 32 A) A PDUs, delivering a total of A PDUs, delivering a total of 10,000 Watts for two PDU pair. 15,000 Watts. Note: Note: Each 30 or 32 A PDU pair Each 30 or 32 A PDU pair delivers 5,000 Watts. delivers 5,000 Watts. Cooling Avaya Solutions Platform 4200 series: Avaya Solutions Platform • Configured for rear facing networking components. 4200 series is designed for • VSP 7254XSQ switches are configured with back-to-front fans to provide front-to-back cooling. a front-to-back airflow within the Avaya Solutions Platform 4200 series enclosure. Avaya Solutions Platform 4200 series cooling fan assemblies. • Main and Extension rack with vertical PDUs: - 12 fan assemblies (each fan assembly consists of 2 x 105 CFM cooling fans), which provides 2,520 CFM of airflow. Networking Avaya Solutions Platform 4200 series provides two Avaya VSP 7254XSQ (Distributed Top-of-Rack networking switches), rack mounting hardware, power supplies, and Fabric Interconnect cables. Each switch provides: • 48 SFP+ ports supporting 1/10 gigabit Ethernet (GbE) transceivers • 6 QSFP+ ports supporting 40 GbE • Multiterabit Fabric Connect, using Shortest Path Bridging (SPB)
Compute servers Avaya Solutions Platform 4200 series: Compute servers are • Main racks: A minimum of three compute servers. physical servers (the ESXi • Extension racks: No minimum required. hosts are for virtualization). • The maximum amount of compute servers is dependent upon RMU slots, power limits, and thermal limits for your specific configuration. • HPE ProLiant DL360 G10 v2 for Main rack: - Dual Intel(R) Xeon(R) Gold 6226R CPU @2.90GHz, providing 32 Cores/64 threads/server:: 10 gigabit, 2–port SFP+ adapter—for Main rack compute server traffic and HPE iLO host management. Storage HPE Nimble storage platform supports high availability and redundancy. Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 25 Comments on this document? [email protected] Avaya Solutions Platform 4200 Components
Component Description Avaya Solutions Platform 4200 series: • HPE Nimble CS1000 storage array can be expanded up to 99TB. Gateways (Optional) G450 Media Gateways: Component requirement is based on the specific customer Avaya Solutions Platform 4200 series solution. • G450 Media Gateways are 3U form factor devices, each Gateway can provide a maximum of eight supplemental media modules for external interfaces. Note: In Avaya Solutions Platform 4200 series, the G450 Media Gateways are installed facing the rear of the enclosure. Session Border Controllers (Optional) Avaya Session Border Controller for Enterprise: Component requirement is based on the specific customer Avaya Solutions Platform 4200 series solution. SBCE supports the following: • Dedicated hardware appliances—Dell R640 servers. • Virtual environment (VE)—In new system builds, SBCE Enterprise Management Server (EMS) is deployed as VE only. Avaya Solutions Platform 4200 series supports the following SBCE configurations: • High Availability (HA) configuration options: - EMS (VE) + SBC 1 (appliance 1) + SBC 2 (appliance 2) - EMS (VE) + SBC 1 (VE) + SBC 2 (VE) • Stand-Alone (SA) configuration: - EMS (VE) + SBC 1 (VE) Virtualization VMware vSphere ESXi 6.5 P05- Build 16576891 and vCenter u3k - Build 16613358. Avaya Solutions Platform 4200 series component applications are virtualized and run on compute servers. Compute servers are physical ESXi host servers. Verified third-party virtual Avaya has verified the following third-party virtualized networking equipment appliances (optional) for Avaya Solutions Platform 4200 series solutions. • Third-party virtual Firewalls (Avaya verified): - Palo Alto Networks VM-300 - Fortinet FortiGate-VM01 Management • Avaya Orchestrator • VMware vCenter Server Appliance • HPE Integrated Lights-Out (iLO) management (on HPE compute servers) • Management Server Console Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 26 Comments on this document? [email protected] Avaya Solutions Platform 4200 series component list
Component Description Avaya and Avaya Aura® • Avaya Aura® Collaboration Suite, up to maximum capacities supported by software licenses Avaya Aura® products • Avaya Aura® Communication Manager for the Virtualized Environment • Avaya Aura® Messaging (AAM) Virtualized Environment • Avaya Aura® Session Manager for the Virtualized Environment • Avaya Aura® System Manager for the Virtualized Environment • Avaya WebLM for the Virtualized Environment • Avaya Diagnostic Server with SLA Mon™ and SAL Gateway for the Virtualized Environment • Avaya Aura® Utility Services for the Virtualized Environment • Avaya Aura® Application Enablement Services for the Virtualized Environment Avaya Aura® Presence Services for the Virtualized Environment • Avaya Agile Communication Environment™ for the Virtualized Environment • Avaya Orchestrator • Avaya Session Border Controller for Enterprise (optional) • Avaya Call Management System (CMS) (optional) • Avaya Aura® Experience Portal (optional) • Agile Communication Environment™ (optional) • ANAV (optional) • Avaya Aura® Call Center Elite Multichannel (optional) • Avaya Aura® Workforce Optimization (optional) • Avaya Multimedia Messaging (optional) • Avaya Aura® Media Server (optional) • Avaya Breeze® platform (optional) • Avaya Aura® Conferencing (optional) • Avaya Aura® Contact Center (optional) • Avaya Workplace Client Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 27 Comments on this document? [email protected] Avaya Solutions Platform 4200 Components
Component Description Software licenses (other) • VMware vSphere 6 Enterprise Plus • VMware vCenter Server 6 Standard • HPE Integrated Lights-Out (iLO) Advanced Pack license — required to mount .iso images and use Integrate Remote Console (IRC)/Virtual KVM, support text, and graphics. Uses a shared network port with one of the 10–gigabit ports. • Premier License–available to customers with dual data centers and to those who have equipment that supports MACsec, large ASPs and Carriers with multi-instance. This license is installed on all switches for all customers. • Extreme Virtual Services Platform 7200 Series Premium license. • Management Server Console: Microsoft Windows Server 2016 Standard Edition.
Phone firmware versions Phone firmware is available as part of the Avaya Solutions Platform 4200 series Management Server Console. Files can be loaded on demand on Avaya Aura® Virtualized Environment Utility Services. The following table lists the available phone firmware versions.
Table 4: Phone firmware versions
96XX IP Series Deskphones H323 96x1-IPT-H323-R6_7_1_04-112718.zip (9608/9608G/9611G/9621G/9641G) 96x1-IPT-H323- R6_7_1_04U-112718.zip(Encrypted) 96xx-IPT-H323-R3_2_8-091517.zip (9620L/9620C/9630G/9640/9640G/ 9650/9650C/9670G) SIP 96x1-IPT-SIP-R7_1_10_0-062220.zip (9601/9608/9608G/9611G/9621G/9641G) 96xx-IPT-SIP-R2_6_17-172303.zip (9620L/9620C/9630G/9640/9640G/ 9650/9650C)
September 2020 Avaya Solutions Platform 4200 Series Solution Description 28 Comments on this document? [email protected] Chapter 5: Hardware Component Description
Avaya Solutions Platform 4200 series hardware components The following sections describe the major hardware components typically contained within an Avaya Solutions Platform 4200 series enclosure.
Networking switches Avaya Solutions Platform 4200 series uses Extreme Virtual Services Platform 7200 Series (VSP 7254XSQ) for distributed top-of-rack networking. Extreme Virtual Services Platform 7200 Series switch The Extreme Virtual Services Platform 7200 Series switch provides high density, high capacity and a high performance forwarding engine for data centers, aggregation, and small-to-medium core switches. The Avaya Solutions Platform 4200 series provides two VSP 7254XSQ switches, which includes one VSP 7008XT Media Dependent Adapter in each VSP 7200 Series switch, to provide double the ports and uplinks. Some of the VSP 7200 Series switch features are: • Data center grade hardware that supports back-to-front cooling — the switches are installed in the Avaya Solutions Platform 4200 series in reverse, so the air flow is actually front-to-back from an Avaya Solutions Platform 4200 series perspective. • Layer 2 Virtualized Services that extend VLANs across the Fabric (including across subnets and long distances). • IEEE 802.1 aq Shortest Path Bridging with sub second recoveries for all services. • Layer 3 Virtualized Services that interconnect and extend VRFs across the Fabric. • Native Routing between Layer 2 and Layer 3 Virtualized Services for access to shared services. • Can be converted to routers by enabling routing. • IP Shortcut Routing that enables direct Layer 3 connectivity between individual end points without requiring deployment of additional IGPs.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 29 Comments on this document? [email protected] Hardware Component Description
• Avaya VENA Fabric Connect services, such as multicast shortcuts and IP multicast virtualization • Dual, hot-swappable AC power supplies. Caution: The VSP 7200 Series switches feature hot-swappable cooling fan trays. Cooling fan tray swaps should be performed only by Avaya-trained and certified personnel. • 48 SFP+ ports supporting 1 GbE and 10 GbE. • 6 QSFP+ ports supporting 40GbE • RJ45 10 Gigabit Ethernet ports that support 1G or 10G • Support for network-wide fabric-based Virtualized Services and Lossless environments. • Support for east-west traffic flow (not required for Avaya Solutions Platform 4200 series). For more information, see Extreme Virtual Services Platform 7200 Series documentation at: https://www.extremenetworks.com/support/documentation/vsp-7200-series-hardware-documents/. Extreme Virtual Services Platform 4000 Series switch (Legacy) The Extreme Virtual Services Platform 4000 Series switche are 1/10 Gigabit, fabric-enabled multiservice Ethernet switches with network virtualization capabilities that extend the benefits of Avaya VENA Fabric Connect to the edge of the network. The VSP 4000 Series switches are equipped with a carrier-grade operating system, and AC and DC power options that increase network agility. With a simplified infrastructure, the 4000 series, is a comprehensive array of network services, including Layer 2 and Layer 3 virtualization with optimized routing and IP multicast support across the entire enterprise. Some of the VSP 4000 Series switch features are: • Layer 2 Virtualized Services that extend VLANs across the Fabric (including across subnets and long distances). • IEEE 802.1 aq Shortest Path Bridging with sub second recoveries for all services. • Layer 3 Virtualized Services that interconnect and extend VRFs across the Fabric. • Native Routing between Layer 2 and Layer 3 Virtualized Services for access to shared services. • Can be converted to routers by enabling routing. • IP Shortcut Routing that enables direct Layer 3 connectivity between individual end points without requiring deployment of additional IGPs. • Avaya VENA Fabric Connect services, such as multicast shortcuts and IP multicast virtualization. For more information, see Extreme Virtual Services Platform 4000 Series documentation at: https://www.extremenetworks.com/support/documentation/vsp-4000-series-hardware-documents/.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 30 Comments on this document? [email protected] Avaya Solutions Platform 4200 series hardware components
Compute servers Avaya Solutions Platform 4200 series includes compute servers for applications and management. For redundancy purposes, the servers operate in a high availability (HA) cluster. In hot standby mode, you can replace or add servers to the cluster without downtime. Avaya Solutions Platform 4200 series uses HPE DL360 G10 V2 compute servers with the following high level specifications: • Dual Intel(R) Xeon(R) Gold 6226R CPU @ 2.90GHz, providing 32 Cores/64 threads/server using Cascade Lake architecture • 1 x HPE FlexFabric 10Gb 2-port 534FLR-SFP+ Adapter • Dual redundant power supply • iLO network port feature enabled by default Avaya Solutions Platform 4200 series can support configurations or growth with a mix of the supported compute server types and generations. The VMware software and the software license are included on the servers.
Storage The Avaya Solutions Platform 4200 series includes a HPE Nimble CS1000 storage array with a combination of Serial Attached SCSI (SAS) and Solid State (SSD) drives. The disk array automates administration, configuration, and maintenance of storage, such as raid, failover or recovery, block sizes, and read/write optimization to allow for reduced maintenance, administration, and greater flexibility. This configuration supports LUN changes for expansion, migration, and creation of new data stores, and allows for simplified expansion that can support various drive sizes.
Power Distribution Units and AC plugs The maximum number of servers or physical components that can operate in one Avaya Solutions Platform 4200 series rack enclosure is calculated for each build type based on the output power, number of available AC outlets of the Power Distribution Units (PDUs), and the fan cooled thermal management for all operating components in the rack. Base ASP 4200 racks use up to three primary and three secondary vertical PDUs to provide power and redundant pairs for the Avaya Solutions Platform 4200 series components. If Avaya Solutions Platform 4200 series is ordered without an enclosure, the customer must provide sufficient PDUs to power the Avaya Solutions Platform 4200 series.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 31 Comments on this document? [email protected] Hardware Component Description
Other Extension racks such as Gateway Extension racks use one primary and one secondary horizontal PDU to provide power and a redundant pair. • Avaya Solutions Platform 4200 series and components powered by the PDU operate in the single phase 208 – 240V AC range. • Avaya Solutions Platform 4200 series is configured with redundant pairs of 30 A or 32 A PDUs. • Each PDU provides 16 AC outlets, divided into two individually fused sectors of eight AC outlets. • Switched PDUs have the ability to monitor power states and control equipment and power usage. The AC in feed source plug and cable on the PDU can vary depending on system amperage and geographic location requirements. The following table shows the typical AC source power plug options for Avaya Solutions Platform 4200 series. If your site requires a different power plug than the following options, a certified electrician might be required. You can contact Avaya Professional Services (APS) or your System Integrator (SI) for assistance.
Table 5: Power plug options
30 A or 32 A PDU hardwired power cord – 24 A usable after Safety Agency derating NEMA L6 – 30P IEC 60309 (Blue 32 A rating)
Hardwired AC source plug on 32 A PDUs. Hardwired AC source plug on 30 A PDUs.
Table 6: Power plug options
20 A PDU replaceable power cord — 16 A usable 30 A or 32 A PDU hardwired power cord – 24 A after Safety Agency derating usable after Safety Agency derating NEMA L6 – 20P NEMA L6 – 30P
Hardwired AC source plug on 30 A PDUs. Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 32 Comments on this document? [email protected] Avaya Solutions Platform 4200 series hardware components
20 A PDU replaceable power cord — 16 A usable 30 A or 32 A PDU hardwired power cord – 24 A after Safety Agency derating usable after Safety Agency derating IEC 60309 (Blue 16 A rating) IEC 60309 (Blue 32 A rating)
Hardwired AC source plug on 32 A PDUs. Schuko
Fan cooling Avaya Solutions Platform 4200 series is designed for front to back fan cooling, which provides a consistent front to back airflow in the Avaya Solutions Platform 4200 series enclosure. The hardware is arranged for optimal thermal configuration and cabling considerations. Cooling fan assemblies mounted to the rear doors blow air out of the enclosure. Fan cooling of Avaya Solutions Platform 4200 series components is engineered for a maximum ambient operating temperature of 35° C at the front door (cold aisle) of the enclosure. Important: Do not exceed the 35° C (95° F) maximum ambient operating temperature at the front door (cold aisle) of the enclosure. Additional site cooling infrastructure might be required, such as air conditioning, or hot and cold aisle separation, to ensure that the front inlet (cold aisle) of Avaya Solutions Platform 4200 series is maintained at 35° C or less for Avaya Solutions Platform 4200 series in an Avaya branded enclosure. The Avaya Solutions Platform 4200 series enclosure contains 12 rear door fans (six fan assemblies on the left door and six fan assemblies on the right door) that provide 2400 CFM for thermal management. The Horizontal Extension rack enclosure typically contains six rear door fans (three fan assemblies on the left door and three fan assemblies on the right door) that provide 1200 CFM for thermal management. 1G/10GB Extension rack (six vertical PDUs) enclosures typically contain 12 rear door fans (six fan assemblies on the left door and six fan assemblies on the right door) that provide 2400 CFM for thermal management.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 33 Comments on this document? [email protected] Hardware Component Description
The fan assemblies, plus specific placement of the components in the rack, filler panels, special wiring constraints, and special baffling within the enclosure, make up the cooling strategy for Avaya Solutions Platform 4200 series enclosures.
Avaya Media Gateway The Avaya G450 Media Gateway provides a secure, reliable, and scalable platform for the delivery of Avaya Aura® Communication Manager-based IP telephony applications. The Media Gateway supports field-replaceable modules and high resiliency features. For redundancy, you can install multiple Media Gateways. Also included are basic routing capabilities, enhanced Quality of Service, and advanced security. In the Avaya Solutions Platform 4200 series implementation, Avaya Media Gateway provides SSL/TLS and IPSEC remote access. Also, non-SIP endpoints register to the Media Gateway.
Optional hardware components Avaya Session Border Controller Avaya Session Border Controller for Enterprise (SBCE) controls and delivers voice, video, and multimedia communications between separate IP networks. Avaya Session Border Controller for Enterprise is supported as a hardware device or as a virtual appliance. SBCE for the Virtualized Environment is available as an add-on that can be installed either pre-delivery or post-delivery. For redundancy, you can install more than one SBCE unit to work in conjunction with the SBC Administration server. Note: If your existing Avaya Solutions Platform 4200 series currently has Acme Packet Session Border Controller installed, Avaya encourages you to move to Avaya Session Border Controller for Enterprise as this will be the only supported Session Border Controller in future releases. For more information on Avaya SBCE hardware, see Avaya Session Border Controller for Enterprise Overview and Specification. For more information on Avaya SBCE for the Virtualized Environment, see Deploying Avaya Session Border Controller in Virtualized Environment. Avaya Scopia® Avaya Solutions Platform 4200 series supports Avaya Scopia® Elite 6140 (MCU) hardware for videoconferencing, as an optional add-on that is deployed post-delivery.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 34 Comments on this document? [email protected] Avaya Solutions Platform 4200 series hardware components
Avaya Scopia®Elite 6140 (MCU) The Scopia® Elite MCU is Scopia® Solution’s flagship platform for high definition multiparty videoconferencing. An MCU, or Multipoint Control Unit, connects several endpoints to a single videoconference. It manages the audio mixing and creates the video layouts, adjusting the output to suit each endpoint's capabilities. The MCU harnesses revolutionary processing power for the most demanding videoconferencing applications using the latest DSP technologies. For an uncompromised videoconferencing experience, the MCU supports dual channels of Full HD 1080p at 60 frames per second for video and content, H.264 High Profile for bandwidth efficiency, H.264 Scalable Video Coding (SVC) for high network error resiliency, and full support for many telepresence systems. With the MCU, each videoconference participant receives a quality experience optimized to their individual capabilities, from wireless mobile devices to HD room systems and immersive telepresence systems. The MCU leads in video interoperability, working with the broadest range of video systems on the market from leading UC clients to mobile devices and telepresence systems. The MCU also features a patented, distributed architecture approach known as the Virtual MCU or cascaded videoconferences, which brings unparalleled scalability to its superb videoconferencing experience. For more information, see User Guide for Avaya Scopia® Elite 6000 Series MCU. Avaya Scopia® Management Avaya Scopia® Management is an application to control your video network devices and schedule videoconferences. You can access Avaya Scopia® Management either from the administrator portal or the user portal. Service providers and organization administrators access the administrator portal to perform network-wide management, while customers of service providers access the administrator portal to perform similar tasks that are relevant only for their organization. Meeting operators and regular users access the user portal to perform scheduling and management relevant to them. For more information, see User Guide for Avaya Scopia® Management. Avaya Scopia® Desktop Avaya Scopia® Desktop is a desktop videoconferencing system turning Windows PCs, Apple Macintosh computers and mobile devices into videoconferencing endpoints. It includes the latest in video technology including support for HD video, NetSense for video quality optimization, Scalable Video Coding (SVC) for unsurpassed error resiliency and H.264 when viewing both meeting participants and data collaboration. Its audio system provides echo cancellation, background noise suppression, and is highly resilient to network errors common on the Internet. Avaya Scopia® Desktop is comprised of the Scopia® Desktop server and a lightweight Scopia® Desktop Client which turns a PC or Mac into a videoconferencing endpoint. Scopia® Mobile users can also access the Scopia® Desktop server from their iOS and Android devices. For more information on Scopia® Mobile, see the User Guide for Scopia® Mobile. For more information, see Administrator Guide for Avaya Scopia® Desktop Server.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 35 Comments on this document? [email protected] Chapter 6: Software Component Description
Application component descriptions This section provides an overview of the software that may be installed on your Avaya Solutions Platform 4200 series. For information on where to locate documentation for these components, see the Documentation Reference for Avaya Solutions Platform 4200 series.
Software and virtual appliances The following tables show a complete list of software and virtual appliances supported in Avaya Solutions Platform 4200 series. Note: The following tables show the default and optional applications based on the default Avaya Solutions Platform 4200 series configuration. Customer requirements and final configuration determine the actual software deployed on each Avaya Solutions Platform 4200 series. Avaya Solutions Platform 4200 series software and virtual appliances Note: The Management Server Console (MSC) is a Microsoft Windows 2016 Standard VM installed by the manufacturer in new Release 4.1.0.1 builds. The Windows license sticker is on the chassis lid of Compute Server 1. A request must be sent to [email protected] when upgrading to Release 4.1.0.1 software. The request must ask for the Avaya Solutions Platform 4200 series MSC Upgrade Media Kit, Material Code 700513602. This kit contains the media and licenses necessary for upgrading the MSC to Windows Server 2016. The customer must purchase and license additional copies of the Red Hat Enterprise Linux VMs required to install all other Linux-based applications.
Table 7: Infrastructure applications
September 2020 Avaya Solutions Platform 4200 Series Solution Description 36 Comments on this document? [email protected] Application component descriptions
Product OS Deployment Version Avaya Orchestrator Red Hat Enterprise Linux Predelivery 7.7 (Maipo) Management Server Console Windows Server Predelivery 2016 (MSC) VMware vCenter Server VMware Photon OS Predelivery 1.0
Table 8: Avaya Aura® Virtualized Environment applications (8.1.x)
Product OS Deployment Version Communication Manager (with Call Red Hat Enterprise Linux Predelivery Check with Center Elite) Application documentation for OS version. Session Manager (SM) Red Hat Enterprise Linux Predelivery Check with Application documentation for OS version. System Manager (SMGR) Red Hat Enterprise Linux Predelivery Check with Application documentation for OS version. Utility Services Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. WebLM Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Avaya Aura® Messaging Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Application Enablement Services Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Avaya Media Server (AMS) VE Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Avaya Diagnostic Server CentOS Predelivery Check with Application documentation for OS version.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 37 Comments on this document? [email protected] Software Component Description
Table 9: Contact Center applications
Product OS Deployment Version Call Management System (CMS) Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Avaya Workplace Client Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. Avaya Aura® Call Center Elite Windows Server Postdelivery Check with Multichannel Application documentation for OS version. Avaya IX™ Workforce Engagement Windows Server/RHEL Postdelivery Check with Select Application documentation for OS version. Avaya Navigator (ANAV) Windows Server Postdelivery Check with Application documentation for OS version. Avaya Multimedia Messaging Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version.
Table 10: Additional appliances
Product OS Deployment Version Avaya Session Border Controller for Red Hat Enterprise Linux Predelivery Check with Enterprise (SBCE) Appliance Application documentation for OS version. Avaya Session Border Controller for Red Hat Enterprise Linux Predelivery Check with Enterprise (SBCE) VE Application documentation for OS version. Avaya Aura® Conferencing (AAC) Red Hat Enterprise Linux Postdelivery Check with Application documentation for OS version. G450 Media Gateway — Predelivery Check with Application documentation for OS version.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 38 Comments on this document? [email protected] Application component descriptions
Virtualization applications vSphere ESXi Hypervisor VMware vSphere with ESXi hypervisor architecture provides hypervisor management for security, deployment and configuration, and routine administration. vSphere installs directly on the physical server. Use vSphere to partition the server into multiple virtual machines (VM) that can run simultaneously and share the same physical resources. In a VMware vSphere high availability (HA) configuration, if a physical server fails, all affected VMs automatically restart on other servers with available capacity. This ensures high availability for all applications running on VMs. You can use remote management tools to remotely manage all vSphere functions. For more information about vSphere ESXi Hypervisor, go to the VMware website at www.vmware.com. vCenter vCenter is a VMware tool that provides the automation and control needed to manage highly virtualized and private cloud environments. vCenter provides performance, capacity, and configuration management in converged infrastructures. vCenter can help simplify and automate Operations Management to ensure service levels, reduce risk and downtime, and optimize your environment. For more information about vCenter, see www.vmware.com.
Management applications Management Server Console The Management Server Console (MSC) provides access to software for managing the operations of the Avaya Solutions Platform 4200 series. The MSC is a Windows 2016 Standard Edition server virtual machine. You can also deploy additional VMs or multiple instances of software components using the installed VMware vSphere Client. Important: Ensure that the Avaya Solutions Platform 4200 series has sufficient resources before deploying additional virtual machines or additional software components. Consult with the Solution Engineer to use the Avaya Configurator Tool (CTOOL) to calculate resource availability for the customer’s solution.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 39 Comments on this document? [email protected] Software Component Description
The following table shows the software that is installed on the MSC. Along with this software, all of the OVAs and patches required for Avaya Solutions Platform 4200 series are stored on the E partition with MSC.
Software Purpose VMware tools Used by VMs as the interface for VMware control software. VMware vSphere Client Thick Manages VMware infrastructure. client (Legacy) Mozilla Firefox Access web-based management tools. Notepad++ For text and configuration file editor. Wireshark Troubleshoot applications and devices. PuTTY Access device command line interfaces through SSH. WinSCP Transferring files. TFTP server and SFTP File transfer. Unisphere client EMC storage device access. DNS server The service comes pre-installed, but not configured by default. Customers can configure DNS server as needed to have the Management Server Console VM acting as a DNS server. iLO remote console thick client Access to compute server console remotely. Avaya SDM Automate Avaya Aura Applications upgrade.
Note: Additional utility software may also be included. For more information about performing Avaya Solutions Platform 4200 series infrastructure upgrades, see Upgrading Avaya Solutions Platform 4200 series using the Management Server Console. HP Integrated Lights-Out (iLO) HP Integrated Lights-Out (iLO) is a management interface which manages and monitors local or network hosts. Avaya POS applications connect with the HP iLO interface to manage and monitor hosts. An HP iLO Advanced Pack license is required to mount .iso images and use Integrated Remote Console (IRC/Virtual KVM, support text, and graphics). iLO connectivity HP iLO uses one of two network connection methods to access all functionality: Dedicated Connection or Shared Network Port. Avaya Solutions Platform 4200 series uses Shared Network Port. This eliminates the need for a separate network connection for each host by sharing the same port for production data and iLO management.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 40 Comments on this document? [email protected] Application component descriptions
Avaya Aura® Virtualized Environment applications Avaya Aura® Communication Manager Avaya Aura® Communication Manager (CM) for the Virtualized Environment delivers all PBX features, voice and video capabilities, advanced mobility features, contact center applications, E911 capabilities, and high reliability and scalability. In addition, the Avaya Aura® Communication Manager provides user and system management functionality, intelligent call routing, application integration and extensibility through multi-protocol support, and enterprise communications networking. By providing an enterprise communications network for analog, digital, and IP based communication devices, voice and data signals can be transmitted from a corporate or public telephone system to another public or private telephone network, Ethernet LAN, or the internet. Avaya Aura® Communication Manager provides telephony features to all users in the architecture. Communication Manager is deployed for the CCaaS service as an evolution server (CM-ES) for the following reasons: • CM-ES is required for Call Center Elite functionality and AES support; • CM-ES provides significantly better performance and SIP trunk session scaling. CM-ES tenant partitioning is at the core of the ability to share CM with multiple customers. Tenant Partitioning can be used at run time to prevent an agent within one end-customer population from directly calling a VDN in another end customer, if blocking of these calls is desired. The multi- tenancy solution within Communications Manager can also be leveraged to assign dedicated announcements per tenant. CM-ES supports up to 100 tenants, but that number can be increased to 250 through a Special Application called Increase Tenant Partitions (SA8993). This number includes partitions that are system reserved, hence the overall total available for end customers is a smaller number (240). Avaya Aura® Call Center Elite Avaya Aura® Call Center Elite (CC Elite) for the Virtualized Environment is an Automatic Call Distribution application that provides powerful call routing and resource selection capabilities designed to help agents handle calls more effectively and boost their overall productivity. Avaya Aura® Call Center Elite can integrate with traditional circuit switched, H.323, and SIP networks as well as hybrid environments. As part of Avaya Aura® Communication Manager, CC Elite offers features such as conditional call routing, which uses context-based inputs and versatile selection capabilities. For example, the application offers managers routing choices about whether inbound calls connect with the least busy agent, the first available agent, or the one with skills that best match the customer’s needs. Avaya Aura® Session Manager Avaya Aura® Session Manager (SM) for the Virtualized Environment provides centralized SIP routing and management of multi-vendor communications systems. Features and capabilities of the Avaya Aura® Session Manager include centralized dial plans and user profiles, centralized SIP trunking, on-net call routing, and enhanced scalability and security.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 41 Comments on this document? [email protected] Software Component Description
Avaya Aura® Session Manager (SM) handles all SIP call signaling/routing for the solution. It takes on URE (User Relation Element) and SRE (SIP Routing Element) functionalities. This means that it provides SIP trunking as well as SIP endpoint registrations. Session Manager only uses SIP protocol to communicate to other entities within the enterprise. SIP entities are defined as: • CM Evolution Servers • Messaging, Conferencing, etc. • SIP Gateways • Session Border Controllers • SIP PSTN Service Providers • SIP-enabled adjuncts. Avaya Aura® System Manager Avaya Aura® System Manager for the virtualized environment is a browser-based console that provides a common management platform for Avaya Aura®. A central management system, it provides frameworks that internal services and external applications use. In addition, external applications include the authentication framework that provides authentication across System Manager and its components, so you do not require separate authentication for product-specific consoles. System Manager – Common Services and Avaya Orchestrator are deployed in conjunction with ACM to provide management functions. From a Roles Based Access perspective, ACM only allows the service provider administrators to make changes through System Manager. System Manager Role Based Access Control (RBAC) is also used by Avaya Orchestrator to grant access permissions to service provider administrators to change and view the ASP 4200 network. As System Manager is used to only administer core element/functions, ACM is the singular end customer portal integration (end users/administrators do not have any interface to SMGR). System Manager and Avaya Orchestrator provide a central management framework for the supported Avaya products. With the SMGR Common Services framework, the following central management functions are provided: • Authentication, authorization, and registration • Central authentication, including Single Sign‐On (SSO) • Central authorization, including Role Based Access Control (RBAC) • Element/application registration and Public‐Key Infrastructure (PKI), including trust management • Logging, alarming, and SNMP traps with VPFM which is Avaya Orchestrator. • Central logging and log harvesting • Central alarm handling
September 2020 Avaya Solutions Platform 4200 Series Solution Description 42 Comments on this document? [email protected] Application component descriptions
• SNMP management, enabling discovery and inventory of the ASP 4200 hardware and virtualized components. • User management • Central licensing using WebLM • Managing device credentials for auto discovery. • Administering security policies. In addition to being a centralized management tool for Avaya applications and systems, System Manager and Avaya Orchestrator are also the element manager for administering and monitoring the Session Manager. Avaya Orchestrator applications leverage System Manager as SSO infrastructure and landing page. Start using Avaya Orchestrator through the System Manager administration user menu. Avaya Aura® Utility Services Avaya Aura Utility Services for the virtualized environment provides the tools to analyze, configure, optimize and maintain Avaya Aura applications on a single server. A user can download and manage IP telephone or branch gateway firmware and telephone file settings. Avaya Aura® Presence Services Avaya Aura® Presence Services for the virtualized environment collects and distributes presence information between Avaya and third-party endpoints. Presence information indicates user availability with a status from the following list: • Available • Busy • Away • Do not disturb • On a call Avaya Aura® Messaging Avaya Aura® Messaging (AAM) is a unified messaging solution that combines new and existing technology with industry standards to provide a unified messaging platform. AAM also provides tenant partitioning in CCaaS, specifically the ability to block tenants from leaving messages directly to each other, and support for tenant specific broadcasts. The approach is based on AAM's existing "site-ID" parameters. Each tenant can be placed into a separate AAM site-ID, and the different site-IDs are blocked from accessing each other. AAM provides voicemail functionality. A High Availability AAM solution is deployed on a per end customer basis to provide voicemail capabilities for up to 2500 UC and 2500 CC users. The solution comprises three servers — one server is designated as the Storage Server, which contains the overall messaging database and manages topology and end user configuration. The
September 2020 Avaya Solutions Platform 4200 Series Solution Description 43 Comments on this document? [email protected] Software Component Description
other two servers are Application Servers whose primary function is to manage calls and media from the Communication manager through the Session Manager. Avaya Aura® Application Enablement Services Avaya Aura® Application Enablement Services (AES) for the Virtualized Environment is a set of enhanced telephony APIs, protocols, and Web services available to developers. Developers can access powerful call processing, media, and administrative features available in Avaya Aura® Communication Manager. These features enable off-the-shelf and custom integration with communications and business applications as well as a broad range of call center, call recording, and click-to-dial applications. Avaya Aura® Application Enablement Services (AES) is a software solution that provides an enhanced set of telephony application programming interfaces (APIs), protocols, Web services, and direct IP access to media. It also supports standards such as Computer Supported Telecommunications Applications (CSTA), Java Telephony API (JTAPI) and Telephony Server API (TSAPI) that utilize CM-ES features. AES is deployed in support of: • Avaya Call Center Elite Multichannel integration. • Workforce Optimization (WFO) Contact Recording or third party Contact Recording solution. Avaya Media Server Avaya Media Server (AMS) is a software based media server that provides soft DSP and media channel resources. AMS is run as a virtual machine on Avaya Solutions Platform 4200 series and can replace G450 DSP resources in order to reduce the hardware footprint. However, G450 is still needed for TDM, T.38 fax and V.150.1 interfaces. AMS and G450 can both be deployed on one Avaya Solutions Platform 4200 series. The AMS VM supports 550 channels, which is equivalent to 1.5 G450s. A separate AMS VM is required for EDP and for AACC. Avaya Diagnostic Server
Avaya Diagnostic Server (ADS) is an Avaya serviceability solution for advanced diagnostic services and remote support to Avaya products. ADS includes Secure Access Link (SAL) Gateway and SLAMon Server including Endpoint Diagnostics and Network Monitoring. ADS includes customer-controllable troubleshooting and diagnostic tools that improve problem verification and resolution times. ADS leverages remote access, alarm transfer, remote phone control, remote phone event monitoring, and network monitoring capabilities to reduce onsite dispatches and customer engagement requirements . Secure Access Link (SAL) SAL is an Avaya standardized IP-based on-demand, high speed, secure SSL VPN session creation solution. With advanced policy and audit capabilities, SAL integrates client and Avaya systems at the application layer. The SAL Gateway runs on a virtual machine and has simple network integration over port 443.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 44 Comments on this document? [email protected] Application component descriptions
SAL includes detailed logging and audits and customer control mechanisms and policy capabilities.
Contact Center applications Avaya Call Management System Avaya Call Management System (CMS) provides the information and management tools to monitor and analyze the performance of the contact center operations, showing where improvements are needed and where to take fast effective action. The HA CMS servers connect to Communication Manager System to receive call data. This data is summarized by contact center components such as agent, skill and VDN, and is made available to ANAV. The Communication Manager connection comprises an 'ACD' on the CMS and data is stored in a single Informix database. User access to CMS data is through ANAV. ANAV accesses the CMS Informix Database as needed using the ODBC client. Avaya Aura® Experience Portal The Avaya Aura Experience Portal (AAEP) for the Virtualized Environment serves as a SIP based IVR in front of the switch. Speech applications and outbound campaign managers like Proactive Outreach Manager (POM) and Call Back Assist (CBA) are also supported through AAEP. A complete Experience Portal solution comprises the following core elements: • EPM - The EP Manager which controls the Experience Portal system. It provides roles-based configuration, administration, and reporting capabilities for the system. It routes outgoing calls made with the Application Interface web service to an available MPP server. Additionally, it monitors the heartbeat of the MPP servers and redistributes telephony ports when an MPP fails • Aux EPM - An auxiliary EPM server that handles outgoing calls if the primary EPM server is unavailable • MPP - provides SIP signaling and media endpoint, interprets CCXML & VXML, and provides soft DSP resources • Web application server - dynamically generates CCXML & VXML documents, using data from multiple sources • External Database for reporting. Avaya Elite Multichannel The Avaya Elite Multichannel solution provides Avaya hosted Contact Center customers with the ability to add multichannel capabilities to their new or existing Avaya hosted call center deployment. Elite Multichannel utilizes the same routing and reporting applications as CC Elite, allowing businesses to add email, web chat, or SMS/text channels to their environment simply and without disruption. Extending customer service options to include non-voice channels allow businesses to serve customers through their preferred communication channels and further enhance the
September 2020 Avaya Solutions Platform 4200 Series Solution Description 45 Comments on this document? [email protected] Software Component Description
customer experience. CC Elite Multichannel contains multimedia technology which uses the phantom call feature functionality, with the software of the highly reliable Avaya Aura CM-ES to deliver non-voice work items to contact center agents. Phantom calls equate to virtual calls that are generated by a CTI application that has no physical station as the originating point. The standard CC Elite contact center, with the features of Elite Multichannel, simply blends e-mail and web-based customer inquiries with inbound telephone calls. It also distributes internally held customer records to staffed and logged-in agents, prompting them to initiate contact with customers by phone (preview outbound). The staffed agent who is working on an email through CC Elite Multichannel can, if the CC Elite feature of Multiple Call Handling (MCH) is active, opt to immediately respond to a potentially higher priority contact; for instance an arriving voice call (through One-X agent or the 9608 SIP Phone). The CC Elite Multimedia contact center customer database also provides the ability to give queuing priority to inquiries from special customers and to reject messages from specific customers. Avaya Aura® Workforce Optimization Avaya Aura® Workforce Optimization (WFO) is supported on Avaya Solutions Platform 4200 series as a virtual application. Additional resiliency is provided through VMware functionality like vSwitches, vMotion, Distributed resource Scheduler (DRS), and High Availability (HA). This functionality is supported only in the Avaya Solutions Platform 4200 series environment. When recording calls made on Communication Manager, WFO uses the Device, Media and Call Control (DMCC) interface exposed by AES to provide multiple recording modes. WFO uses three recording modes which are decided upon during the Low Level Design phase: On Demand Recording, Meeting Recording, or Bulk Recording. The WFO application is not natively a multi-tenant solution. However, it can be configured in a way that the system can be partitioned into owners, where each owner maps to a tenant. All recording targets (VDNs, agents, stations) can be defined within an owner. Additionally, users can be defined with replay rights or admin rights under a specific owner. Hence, these users are only able to replay recording files for calls associated with the targets defined under the specific owner. Master Recorder Each group is controlled by its Master Recorder. The primary job of the Master Recorder is to centralize management and control the other elements within the group. The Master Recorder connects through an Avaya Enablement Services (AES) server to the Avaya Communications Manager. There are two connections to the AES server: • CTI through the Telephone Services Application Programming Interface (TSAPI) to allow it to receive real time information about the telephones it needs to record. • The Device and Media Call Control (DMCC) connection allows the Master Recorder to register its own bank of softphones used to record calls. The solution is designed with High Availability which allows one, or in some cases more, components to fail without significant degradation to the system performance. The Master Recorder communicates only to the Main Standby.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 46 Comments on this document? [email protected] Application component descriptions
Main Standby In normal operation the Master Recorder connects to the Main Standby primarily to share its recording load. However, the Main Standby also has its own connections to a separate AES server for both TSAPI and DMCC (the same as the Master). There is a heartbeat between the Master and Standby servers so they can pass information about their current status and ability to record. In the event the Master Recorder is unable to function fully (for example its TSAPI link fails) the Master instructs the Main Standby server to take over the control of the group of recording servers, ensuring the system continues to operate as expected. If the Standby misses several Heartbeats it will assume the Master Server itself has failed and automatically assume the role of Master. Slave Recorder The Slave Recorders are connected to both the Main and Main Standby servers. This is to ensure the system has the recording concurrency capacity required to operate in the event of a failure. Central Search and Replay The design also comprises a search and replay server. Users can log-in to the Search and Replay server to get the results from searches. Tenants do NOT access ACM to perform Search and Replay functions. They access the Search and Replay server through a web browser client. For more information see, Avaya Contact Recorder. Avaya Contact Recorder Avaya Contact Recorder (ACR) is supported on Avaya Solutions Platform 4200 series as a virtual application. It provides call recording functions and is capable of capturing audio from Avaya Aura Communication Manager. Distributed Resource Scheduler (DRS) is utilized across ESXi host clusters for Avaya Solutions Platform 4200 series deployments to help to distribute workloads and ensure ACR virtual applications provide high availability. A DRS rule must be added to help keep virtual applications separated to ensure contact recorders are distributed across multiple hosts. Target Stations Target stations are the stations ACR monitors for call recording. Any calls that occur on the stations are recorded by ACR. Proactive Contact and TSAPI events trigger ACR to record the calls. A Single Step Conference request is sent via TSAPI to conference in one of the target station virtual IP softphones in order to capture the media. Central Search and Replay The design also comprises a search and replay server. Users can log-in to the Search and Replay server to get the results from searches. Tenants do NOT access ACM to perform Search and Replay functions. They access the Search and Replay server through a web browser client. These users are configured on the ACR server with an assigned recording owner. The recording owner maps to the recording owner of the recording files that the users have access to. Based on this recording owner assignment, the user ONLY has access to the appropriate recording files. The user is not able to access any other recording files. Insert content for the first section.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 47 Comments on this document? [email protected] Software Component Description
Avaya Navigator Avaya Navigator (ANAV) provides all the real-time reporting capabilities for CC Elite and Elite Multichannel, as well as historical reporting for Elite Multichannel. ANAV uses the CMS reporting database to provide historical reporting for all CC Elite voice related resources. Real-Time reports for CC Elite are provided by a combination of CTI monitoring of CC Elite resources (Skills, VDNs, and Agents) and by querying CM for Agent State information through the CTI link. Historical and real-time reporting for Elite Multichannel are provided by running direct queries to the MS SQL database from ANAV. All CMS standard reports are available through the ANAV interface. Additionally, custom reporting is available through the ANAV custom report designer. ANAV is used as it inherits the roles based access capabilities from ACM to appropriately restrict the data access for the reports based on the role restrictions defined for the user. The only database for ANAV is the VCA DB. ANAV Real Time, ANAV Historical, and ANAV VCA also use the ACM database for configuration and roles and permissions checking for reporting user authentication as they login. Other databases used by ANAV are the CMS, AAEP, and EMC databases to run historical reports from, and these are read-only for ANAV.
Additional appliances Avaya Aura® Conferencing
Avaya Aura® Conferencing (AAC) is available for Avaya Solutions Platform 4200 series. AAC is available as a post-delivery add-on and is available in the following solutions: • AAC 8.1 GA Medium Simplex. • AAC 8.1 GA Medium Redundant Primary. • AAC 8.1 GA Medium Redundant Secondary. • AAC 8.1 GA Small Platform. • AAC 8.1 GA Large Platform. Network Load Balancer The Avaya Solutions Platform 4200 series is verified for use with Riverbed Load Balancer to distribute web service traffic. Firewalls The Avaya Solutions Platform 4200 series uses verified virtual firewalls by third-party vendors, specifically Palo Alto Networks L3-L7 and Fortinet.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 48 Comments on this document? [email protected] Chapter 7: Avaya Solutions Platform 4200 Common Network Architecture
Avaya Solutions Platform 4200 series common network architecture This chapter provides an overview of Avaya Solutions Platform 4200 series network architecture.
Avaya Fabric Connect
The Avaya Fabric Connect solution is based on Shortest Path Bridging (SPB) IEEE802.1aq protocol and has a range of features that can greatly simplify network operations and at the same time enhance the network’s ability to provide the appropriate level of service for business critical applications.
Routing Avaya Solutions Platform 4200 series can route over the VSP 4000 Series and VSP 7200 Series switches. Static routes on uplinks allow Avaya Solutions Platform 4200 series to become an integral part of a customer’s Data Center network. Routing on the VSP 4000 Series and VSP 7200 Series switches enables network traffic between compute servers to be routed within an Avaya Solutions Platform 4200 series system, to another Avaya Solutions Platform 4200 series, or through Data Center MPLS Label Edge Routers (LER).
Connectivity and VLANs Connectivity Within Avaya Solutions Platform 4200 series, Virtual Machines are connected to the following Virtual LANs (VLANs): • Management VLAN (used by management applications) • Application 1 VLAN (used by Avaya Aura® applications)
September 2020 Avaya Solutions Platform 4200 Series Solution Description 49 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
• Application 2 VLAN (used by Media Gateways G450s) • Intermediate VLAN (used to connect VLANs together for network continuity and in-service additions) • iSCSI VLAN (used by VMware HA/DRS for vMotion) The following figure shows the Virtual Machine connections (IP addresses and VLANs) in one Avaya Solutions Platform 4200 series. In this example, SAL and Utility Services are connected to the Management VLAN only. The Intermediate VLAN is connected to the VRF, the default Virtual Routing Facility instance. The iSCSI VLAN is configured for the whole hosted solution and all VMs are associated with it. The iSCSI VLAN is not visible outside of Avaya Solutions Platform 4200 series.
Figure 5: Common and application-specific VLAN connections Single Avaya Solutions Platform 4200 series In a single Avaya Solutions Platform 4200 series, all other Virtual Machines and Media Gateways are added to the three existing VLANs. The following figure shows how all VMs connect to their VLANs.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 50 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Figure 6: Configuration of VMs and VLANs on a single Avaya Solutions Platform 4200 series VLAN ID numbering
The VLAN header is defined by IEEE 802.1Q. The following figure shows the VLAN header and the VLAN ID.
Figure 7: VLAN header
The VLAN ID length is 12 bits, a maximum of 4096 VLAN IDs. On a Avaya Solutions Platform 4200 series, each instance requires multiple VLANs: In most instances, Management and iSCSI VLANs are shared between instances.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 51 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Avaya recommends you track VLAN usage, to conserve VLAN ID resources and to allow for maximum scalability of up to 1300 instances. The following table shows a VLAN usage example. Note: The following VLAN IDs are default or proposed. For the actual values and information on VLAN IDs, refer to the Customer Lifecycle Workbook.
Table 11: VLAN usage
Purpose VLAN ID Instance 1 Management 1010 Instance 1 App1 2011 Instance 1 App2 (G450) 2012 Instance 1 Intermediate 2013
Instance 2 Management reusing 1010 Instance 2 App1 2021 Instance 2 App2 (G450) 2022 Instance 2 Intermediate 2023
Instance 3 (Management) reusing 1010 Instance 3 App1 2031 Instance 3 App2 (G450) 2032 Instance 3 Intermediate 2033 Continue for Instances 4-1300 same as above n – 3910
Reserved for future non-traditional deployments 3911-4087
Internet Public VLAN (for SRA and SAL) 4088 iSCSI (one per host) 4089 Uplink 1 (combined customer and Dual Data Center traffic) 4090 Uplink 2 (combined customer and Dual Data Center traffic) 4091 Uplink 3 (separate customer traffic) 4092 Uplink 4 (separate customer) 4093 Uplink 5 (separate Dual Data Center traffic) 4094 Uplink 6 (separate Dual Data Center traffic) 4095
VLAN IDs 0000 and 4096 are reserved. Using three new VLANs for each instance, up to 1300 Instances (Enterprise, UCaaS, CCaaS) can be supported by a single Avaya Solutions Platform 4200 series (and its Extension racks).
September 2020 Avaya Solutions Platform 4200 Series Solution Description 52 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
External network Avaya Solutions Platform 4200 series can connect to a Data Center network in many ways. The configuration depends upon the available customer networking technologies, single or multiple Data Center configuration, the number of available interfaces, the available bandwidth, and the number of operation and security policy requirements. The following table shows supported configurations.
Table 12: Supported configurations
Technology Supported/Not supported Direct Ethernet Cable Supported Ethernet DWDM or CWDM Supported 802.1Q VLANs Supported if only 2 end-points are part of VLAN/ BVLANs Note: If VLACP is used, untagged traffic must be extended between end-points too 802.1ad Provider VLANs (QinQ) Supported if only two end-points are part of service connection Point-to-point Carrier Ethernet L2 Supported if MTU >= 1544; need to classify all service (Eline-PBB) traffic/VLANs transparently into service Point-to-point Ethernet L2 MPLS Supported if MTU >= 1544; need to classify all service (Pseudo Wire VPWS) traffic/VLANs transparently into service Multipoint Carrier Ethernet L2 service Supported if only two end-points are part of the (ELAN-PBB) service; MTU >= 1544 and need to classify all VLANs transparently into service or transport BVLANs explicitly over ELAN; or supported with Ethernet over IP Adaptor Multipoint MPLS L2 service (VPLS) Supported if only two end-points are part of the service; MTU >= 1544 and need to classify all VLANs transparently into service or transport BVLANs explicitly over VPLS IP Network Supported with Ethernet over IP adaptor and MTU >=1600 bytes
Depending on the type of Data Center switches, the Avaya Solutions Platform 4200 series external network is configured for SMLT or SPB. SMLT configuration If the Data Center uses traditional Layer 2 switches, the switches in the Avaya Solutions Platform 4200 series are configured for SMLT. The following figure shows an Avaya Solutions Platform 4200 series external network using SMLT.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 53 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Figure 8: External network SMLT to Data Center switches SPB configuration If the Data Center uses SPB capable switches, the switches in the Avaya Solutions Platform 4200 series are configured for SPB. The following figure shows an Avaya Solutions Platform 4200 series external network using SPB.
Figure 9: External network SPB to Data Center switches Post-deployment configuration options After initial configuration by the System Integrator, additional scenarios can be configured on Avaya Solutions Platform 4200 series, as follows: • If a customer has only one Data Center switch, the Avaya Solutions Platform is connected in a triangular configuration, as shown in the following figure.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 54 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Figure 10: Example triangular configuration to Non-Avaya Data Center switch • If a customer has security policies that prohibit sharing of internal production network connections with Internet VPN connections, a separate pair of 1 GB interfaces on the VSP 4850s must be configured, along with a VPN-dedicated public VLAN, as shown in the following figure.
Figure 11: Separate interfaces on VSP 4850 for VPN traffic • Avaya recommends configuring a separate Internet Access on the Avaya Solutions Platform 4200 series for use in situations such as monitoring, or for sales demonstrations. • If additional Management networks are required, separate from any of the above, the recommended configuration is entirely dependent upon the customer network, and can be configured with the addition of VM resources where required. • To directly access the management network (for example, switch management IPs, POS applications, vCenter), a support technician can use port 1/32 on any VSP 4000 Series switch. This port is reserved and configured in order to access the management subnet for debugging purposes.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 55 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Multiple rack configuration Some Avaya Solutions Platform 4200 series configurations require more than one rack in order to support additional servers and/or appliances. In addition to single Avaya Solutions Platform 4200 series installations, systems can be connected back-to-back, or multiple systems can be configured as hives. Avaya Solutions Platform 4200 series can also be combined with Extension racks. Note: Extension racks are installed and configured by the customer or Avaya Professional Services.
Single instance and multiple instance Avaya Solutions Platform 4200 series Single instance Avaya Solutions Platform 4200 series For single instance Avaya Solutions Platform 4200 series, all other Virtual Machines and Media Gateways are added to the three VLANs already created. The following figure shows how all VMs connect to their VLANs.
Figure 12: Single Instance configuration of VMs and VLANs
September 2020 Avaya Solutions Platform 4200 Series Solution Description 56 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Multiple instance Avaya Solutions Platform 4200 series For multiple instance Avaya Solutions Platform 4200 series, additional VLANs need to be configured as follows, for each new instance: • Management(n) • App1(n) • App2(n) • Intermediate(n) Where n stands for the number of the instance. Instance-specific Management and Intermediate VLANs are optional, and only required if the instance must be managed separately from other instances (for example, a VPFM is created for performance and fault management of this instance only). Migrating from single instance to multiple instance Avaya Solutions Platform 4200 series When migrating from a single instance Avaya Solutions Platform 4200 series, as shown in Single Instance configuration of VMs and VLANs on page 56, to a multiple instance Avaya Solutions Platform 4200 series, all per-instance VMs will automatically be in the proper VLANs and you can then create all the required additional instance VLANs. Avaya Solutions Platform 4200 series can be configured to support up to 1300 instances. ACM is currently limited to 250 UCaaS and 125 CCaaS tenants. When that limit is reached, a new ACM pair must be deployed to the first Common instance of Avaya Solutions Platform 4200 series. The following figure shows an example of a three-instance deployment VLAN connections.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 57 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Figure 13: Three-instance deployment VLAN connections Separation and security To avoid routing conflicts, Network Address Translators (NATs) must be configured for any instance with overlapping or with duplicate IP addresses joining the Avaya Solutions Platform 4200 series Intranets. Each instance must have a separate NAT connected to the Intermediate VLAN and all instances must have access to the Common VLANs. Each instance can use a separate Firewall with its own set of security policies. Firewalls and NATs prevent traffic loops and potential inadvertent networking data leakages between instances and tenants. Avaya Solutions Platform 4200 series has been verified for use with Palo Alto and Fortinet virtual firewalls. Each instance can also contain a separate Identity Engines instance for Identity management. The final selection of VMs in any instance depends on the customer needs, scalability and security requirements.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 58 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Multiple Data Center network By default, Avaya Solutions Platform 4200 series is configured as a single Data Center solution. A customer can buy one system at a time, or several for multiple locations. All Multiple Data Center configurations are performed after the default configuration is prepared by the System Integrator. There are multiple reasons for Data Center expansion, such as geographic redundancy for High Availability, and proximity of customers to services. At infrastructure level, Avaya Solutions Platform 4200 series switches provide necessary connectivity between multiple data centers using traditional switching, routing over SPBm, or dedicated dark fiber. Geographic redundancy or load balancing for Avaya Aura® applications is achieved at application level. Dual Data Center configuration is possible between any two Avaya Solutions Platform 4200 series systems, as long as the Avaya Aura® applications are of same Avaya Aura® feature pack versions.
Distributed vRouting for multiple data center deployments The following section provides information about connecting two or more Avaya Solutions Platform 4200 series systems. Use enhanced IEEE82.1AQ to provide active/active default connectivity for the same Layer 2 VSN. Note: In order to configure distributed vRouting, the customer router must be SPB-capable. In a multiple data center deployment, you must configure Virtual Routing and Forwarding (VRF) with Virtual Router Redundancy Protocol (VRRP) on all switches, and use the same Gateway IP address, for example, 172.29.1.1. Ensure you configure all application IP addresses on the same subnet, for example, 172.29.1.0 and configure all four virtual routers to active/active mode. For example, if one of the switches in ASP 4200 rack 1 becomes disabled, the second switch in ASP 4200 rack 1 takes over. However, if both switches in ASP 4200 rack 1 becomes unavailable, the switch in ASP 4200 rack 2 takes over without interruption, and routes all the traffic intended for ASP 4200 rack 1. In a dual data center configuration, you must ensure that all four distributed Gateways use the same IP address. You can also configure more than two Avaya Solutions Platform 4200 series systems in a multiple geographically-distributed network, which provides instant active-active support for applications using the same Layer 2 Virtual Service Network (VSN). The three subnets on the Avaya Solutions Platform 4200 series must be configured on all sides of the network (Management, App1, and App2). For example, 172.29.1.0, 172.29.2.0 and 172.29.3.0. Each subnet must be associated with a specific VLAN and Layer 2 VSN. Note: The infrastructure can be a simple, Multiprotocol Label switching (MPLS) routed network; however, you can achieve the best results with IEEE802.1AQ SPBm.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 59 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Alternative networking solutions The following provides information about alternative solutions for connecting two or more Avaya Solutions Platform 4200 series systems using MPLS. Multiple Avaya Solutions Platform 4200 series systems are typically connected via SPBm. When a customer has an MPLS service provider, Avaya Solutions Platform 4200 series may be connected to the MPLS network through the Service Provider’s MPLS Label Edge Router that is not on the customer’s premises. Multiprotocol Label Switching (MPLS) is a mechanism in high-performance telecommunications networks that directs data from one network node to the next based on short path labels rather than long network addresses, avoiding complex lookups in a routing table. The labels identify virtual links (paths) between distant nodes rather than endpoints. MPLS can encapsulate packets of various network protocols. MPLS supports a range of access technologies, including T1/E1, ATM, Frame Relay, and DSL. When a Service Provider offers MPLS service, the ASP 4200 rack extends the 1 Gigabit Ethernet or 10 Gigabit Ethernet uplinks to the MPLS network. There is no need for any MPLS configuration on the Pod VSP 4000 Series or VSP 7200 Series. MPLS service providers may provide Layer 2 pseudo-wire or Virtual Private LAN Service (VPLS). VPLS provides Ethernet-based multipoint to multipoint communication over IP or MPLS networks. It allows geographically dispersed sites to share an Ethernet broadcast domain by connecting sites through pseudo-wires. The technologies that can be used as pseudo-wire can be Ethernet over MPLS, L2TPv3 or GRE. There are two IETF standards track RFCs (RFC 4761 and RFC 4762) which describe VPLS establishment. VPLS is a virtual private network (VPN) technology. In contrast to L2TPv3, which allows only point-to-point layer 2 tunnels, VPLS allows any-to-any (multipoint) connectivity. In a VPLS, the local area network (LAN) at each site is extended to the edge of the provider network. The provider network then emulates a switch or bridge to connect all of the customer LANs to create a single bridged LAN. VPLS is designed for applications that require multipoint or broadcast access. The following figure shows Avaya Solutions Platform 4200 series connected to an MPLS network. Note: The VSP 7200 Series switches shown in the following diagram are applicable to Avaya Solutions Platform 4200 series.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 60 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Figure 14: Avaya Solutions Platform 4200 series connected to MPLS network Multiple Data Centers, Multiple Avaya Solutions Platform 4200 series systems, and VMware clusters VMware supports vMotion, VMware HA and DRS within each Avaya Solutions Platform 4200 series. vMotion or vStorage across Avaya Solutions Platform 4200 series systems is not supported. Avaya Solutions Platform 4200 series does not support Stretched Clusters. The following table outlines the VMware vMotion support for single or multiple Avaya Solutions Platform 4200 series configurations.
Table 13: Supported VMware configurations
Avaya Solutions Platform 4200 Single vCenter Multiple vCenters series Single Data Center vMotion supported; multiple vMotion not supported; separate servers and racks, acting as one local controls Avaya Solutions Platform 4200 series Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 61 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Avaya Solutions Platform 4200 Single vCenter Multiple vCenters series Multiple Data Centers, if <100km, vMotion supported; acting as one vMotion not supported; separate <10msec latency Avaya Solutions Platform 4200 local controls series Multiple Data Centers, if >100km, vMotion not supported vMotion not supported; separate >10msec latency local controls
VMware ESX clusters provide the following benefits: • High availability • Load balancing • High performance computing. In a VMware ESX Cluster, two or more physical machines are defined to provide resources for the hosts (or resource pools) assigned to that cluster. By using ESX clusters, Avaya Solutions Platform 4200 series can achieve high availability (VM HA) and load balancing of virtual machines. ESXi hosts are configured into a single VMware Cluster providing them High Availability (HA) and Dynamic Resource Scheduling (DRS). vMotion is used to move a particular Virtual Machine (VM) from one ESXi host to another for maintenance or other operational reasons. When VMware HA and fully automated DRS are enabled, if any of the servers in the cluster fail, the other machines will automatically take over those virtual guests. Automated DRS ensures the virtual guests will be automatically migrated to obtain the best possible performance for all machines, according to the resource pool settings. When in Virtual Center, you can easily identify a VMware cluster by the icon, as shown in the following figure.
Figure 15: Example VMware cluster as visualized in Virtual Center When you click on Cluster, you see the current configuration status and options to change the configuration. As shown in the following figure, you are able to view the total CPU and memory
September 2020 Avaya Solutions Platform 4200 Series Solution Description 62 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
resources, number of hosts, total number of processors, total number of virtual machines, and any migrations that have been performed.
Figure 16: VMware cluster configuration status High Availability (HA) ensures there is an active component to replace a failed component almost instantaneously. Avaya Solutions Platform 4200 series is configured to recognize an outage within 10 seconds, and VMware HA will restart a failed Virtual Machine within less than five seconds. It may take several minutes for an Avaya Aura, UCaaS or CCaaS application to be completely restarted. In Avaya Solutions Platform 4200 series, a vMotion of a Virtual Machine creates an outage of less than 10 milliseconds. Dynamic Resource Scheduling is a feature included in the vSphere Enterprise and Enterprise Plus editions. Using DRS, you can: • Improve service levels by guaranteeing appropriate resources to virtual machines. • Deploy new capacity to a cluster without service disruption. • Automatically migrate virtual machines during maintenance without service disruption. • Monitor and manage more infrastructure per system administrator. When you power on a virtual machine in a cluster, DRS places it on an appropriate host or generates a recommendation, depending on the automation level you choose. DRS offers five automation levels, ranging from conservative to aggressive and are configured on a per cluster basis. DRS also uses your automation level to migrate virtual machines to other hosts within the cluster to maximize performance. DRS spreads the virtual machine workloads across vSphere hosts inside a cluster and monitors available resources.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 63 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
DRS speeds up the VMware vSphere® Update Manager™ remediation process by determining the optimum number of hosts that can enter maintenance mode simultaneously, based on current cluster conditions and demands. DRS redistributes virtual machines across vSphere cluster hosts to comply with user-defined affinity and anti-affinity rules following host failures or during maintenance operations. Avaya Solutions Platform 4200 series uses affinity rules to keep Duplex applications, such as CM or SM on separate ESXi hosts after a failure recovery. In a Multi- Instance environment, certain ESXi hosts may be off-limits to others users/instances, and separate clusters may be created.
Supported interconnection options This section contains information on the supported interconnection options between third party networks and the Avaya Solutions Platform 4200 series. Redundant Layer 2 Interconnect Option 1: Multi-Chassis LAG/vIST – vPC Avaya Virtual Services Platform switches are configured with static or dynamic link aggregation. Static link aggregation is recommended. Third party routers are configured with vPC. The intermediate VLAN is extended to the core routers.
Redundant Layer 2 Interconnect Option 2: Multi-Chassis LAG/vIST – VSS Avaya Virtual Services Platform switches are configured with static or dynamic link aggregation. Static link aggregation is recommended. Third party routers are configured with multi-chassis protocol VSS. The intermediate VLAN is extended to the core routers.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 64 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
Redundant Layer 3 Interconnect Option 3: Static Routes If a multi-chassis protocol is not an option, the VLAN extended to the core devices must not span over the physical link between the two devices. This prevents a loop. Network connectivity is provided by static routes to the VRRP interfaces configured on each switch pair.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 65 Comments on this document? [email protected] Avaya Solutions Platform 4200 Common Network Architecture
Storage array expansion Array expansion in Legacy Hardware solutions This is for Avaya Solutions Platform 4200 series operators with Legacy Hardware solutions. It will allow for the introduction of an HPE Nimble CS1000 storage array into the existing configuration. The new HPE Nimble array and expansion shelves will be rack mounted in the existing Avaya Solutions Platform 4200 series enclosure or one provided by the operator. The new HPE Nimble array will be connected to the existing Extreme Virtual Services Platform 7024 and 4058 switches. The following diagram outlines the topology of the expanded storage array.
This change in topology requires the following modifications to the existing solution. • Network - Configure a new VLAN and i-SID for the HPE Nimble storage array on both Extreme Virtual Services Platform 7024 switches. - Add two new ports on each Extreme Virtual Services Platform 7024 switch to the newly created VLAN. Configuration for these ports will be the same as for the ports on VLAN 1000. - Create a separate subnet for the EMC Storage device and the Nimble Storage device, that is, two separate private networks. This will remove the connection between the two storage devices, so they can not communicate and can work as individual SANs even
September 2020 Avaya Solutions Platform 4200 Series Solution Description 66 Comments on this document? [email protected] Avaya Solutions Platform 4200 series common network architecture
though on the same VLAN port (1000). If the EMC already has its own subnet, then there is no need to create a separate subnet. - Add the existing ESXi ports to the newly created VLAN. - Add two new ports on each Extreme Virtual Services Platform 4058 to the existing MGMT VLAN. • Switch wiring - Reserve two new ports on each Extreme Virtual Services Platform 7024 switch for connecting Controller A and B of the HPE Nimble storage array. - Reserve two new ports on each Extreme Virtual Services Platform 4058 switch for connecting the management interfaces of the HPE Nimble storage array. • VMware - Add new VMKernels on each ESXi host for the HPE Nimble storage array. - Add a new HPE Nimble datastore on each ESXi host.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 67 Comments on this document? [email protected] Chapter 8: Best Practices
Networking best practices There are a number of ways Avaya Solutions Platform 4200 series can be connected to a customer network. The following factors help to determine the number of subnets required to allow for optimal communications and should be considered prior to selecting an Avaya Solutions Platform 4200 series configuration: • Whether the Avaya Solutions Platform 4200 series is being configured in a single-tenant or a multiple-tenant environment • Whether the network core is capable of handling Shortest Path Bridging (SPB) • Whether egress or ingress traffic from the Avaya Solutions Platform 4200 series is encrypted The goal is to create a common scalable Avaya Solutions Platform 4200 series network configuration which easily integrates into any customer network. The preferred configuration for connecting to the network is either: • Routing to the regular Customer Premises Equipment (CPE) router, or • SPBm (IEEE802.1aq) to the customer router (if it is capable of SPBm). The following sections provide information and best practices for connecting and configuring Avaya Solutions Platform 4200 series to the customer network. Related links Link to a regular customer router on page 68 SPBm to the customer router on page 70
Link to a regular customer router The following example describes the best practices for linking the Avaya Solutions Platform 4200 series directly to your router. For one tenant Avaya Solutions Platform 4200 series, SPBm is used internally across the Avaya Solutions Platform 4200 series switches. The customer router can reach the subnets inside Avaya Solutions Platform 4200 series (Mgmt, App1, App2) through a VRRP IP defined in an intermediary subnet on the two VSP 4000s. Common applications (for example, Avaya Orchestrator) are configured in a different subnet to ease the addition of future multiple tenants.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 68 Comments on this document? [email protected] Networking best practices
Figure 17: Link to a regular customer router Multiple tenants (Avaya Solutions Platform 4200 series) Multiple tenants are separated by Virtual Routing and Forwarding (VRF) across intermediary subnets on the customer router and on the VSP 7200 switches. The common subnet is a separate VRF, accessible by the tenants through Firewalls. Since VRFs are used, L3 VSNs must be configured on the two VSP 4000s.
Figure 18: Link to a regular customer router — multiple tenants
September 2020 Avaya Solutions Platform 4200 Series Solution Description 69 Comments on this document? [email protected] Best Practices
Related links Networking best practices on page 68
SPBm to the customer router The following examples show best practices for using SPBm to connect Avaya Solutions Platform 4200 series to your router. Avaya recommends that you prepare your network as shown on the left side of the diagrams in order to accommodate the sample Avaya Solutions Platform 4200 series configurations shown. SPBm Single tenant In this example, C-VLANs can be transported into the customer network by SPB directly. Common applications are configured in a separate subnet or C-VLAN to ease the addition of future multiple tenants. The customer network is set up with one subnet in order to accommodate a single tenant but can support future multiple tenants with the addition of new subnets.
Figure 19: SPBm to customer router — SPBm single tenant SPBm multiple tenants (Avaya Solutions Platform 4200 series) Avaya recommends that multiple tenants are separated by different VRFs on the VSP 7200 switches. Since VRFs are used, L3 VSNs must be configured on the two VSP 7200s. In this example, the customer network is set up with two subnets in order to accommodate two tenants. On the VSP 7200 switches, each tenant has its own separate VRF, with one common VRF that is used for both common and management applications, accessible by the tenants through firewalls.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 70 Comments on this document? [email protected] VMware best practices
Figure 20: SPBm to customer router — SPBm multiple tenants
Related links Networking best practices on page 68
VMware best practices The following section outlines general information regarding VMware best practices. Related links VMware networking best practices on page 71 Thin vs. thick deployments on page 72 VMware Tools on page 73 VMware Snapshots on page 73 Resource reservation on page 74
VMware networking best practices You can administer networking in a VMware environment for many different configurations. Review the VMware networking best practices before deploying any applications on an ESXi host.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 71 Comments on this document? [email protected] Best Practices
The following are the suggested best practices for configuring a network that supports deployed applications on VMware Hosts: • Separate the network services to achieve greater security and performance by creating a vSphere standard or distributed switch with dedicated NICs for each service. If you cannot use separate switches, use port groups with different VLAN IDs. • Configure the vMotion connection on a separate network devoted to vMotion. • For protection, deploy firewalls in the virtual machines that route between virtual networks that have uplinks to physical networks and pure virtual networks without uplinks. • Specify virtual machine NIC hardware type vmxnet3 for best performance. • Connect all physical NICs that are connected to the same vSphere standard switch to the same physical network. • Connect all physical NICs that are connected to the same distributed switch to the same physical network. • Configure all VMkernal vNICs to be the same IP Maximum Transmission Unit (MTU). Related links VMware best practices on page 71
Thin vs. thick deployments VMware ESXi uses a thick virtual disk by default when it creates a virtual disk file.. The thick disk preallocates the entire amount of space specified during the creation of the disk. For example, if you create a 10 megabyte disk, all 10 megabytes are preallocated for that virtual disk. In contrast, a thin virtual disk does not preallocate disk space. Blocks in the VMDK file are not allocated and backed up by physical storage until they are written on the disk during the normal course of operation. A read instruction to an unallocated block returns zeroes, but the block is not backed by physical storage until it is written on the disk. . Consider the following details when implementing thin-provisioned disk in your VMware environment: • Thin-provisioned disks can grow to the full size as specified at the time of virtual disk creation, but they cannot shrink. Once you allocate the blocks, you cannot deallocate them. • Thin-provisioned disks run the risk of overallocating storage. If storage is over-allocated, thin virtual disks can grow to fill an entire datastore if left unchecked. • If a guest operating system needs to make use of a virtual disk, the guest operating system must first partition and format the disk to a file system it can recognize. Depending on the type of format selected within the guest operating system, the formatting process may cause the thin-provisioned disk to grow to full size. For example, if you present a thin-provisioned disk to a Microsoft Windows operating system and format the disk, unless you explicitly select the Quick Format option, the format tool in Microsoft Windows writes information to all sectors on the disk, which in turn inflates the thin-provisioned disk to full size. Thin-provisioned disks can overallocate storage. If the storage is overallocated, thin virtual disks can grow to fill an entire datastore if left unchecked. You can use thin-provisioned disks, but you must use strict control and monitoring to maintain adequate performance and ensure that storage
September 2020 Avaya Solutions Platform 4200 Series Solution Description 72 Comments on this document? [email protected] VMware best practices
is not consumed to its full capacity. If operational procedures are in place to mitigate the risk of performance and storage depletion, then thin-provisioned disks are a viable option. Messaging only supports thick provisioning. Communication Manager Messaging only supports thick provisioning. Related links VMware best practices on page 71
VMware Tools The VMware Tools utility suite is built into the application OVA. The tools enhance the performance of the guest operating system on the virtual machine and improve the management of the virtual machine. VMware tools provide: • VMware Network acceleration • Host to Guest time synchronization • Disk sizing For more information about VMware tools, see Overview of VMware Tools at http:// kb.vmware.com/kb/340. Important: Do not upgrade the VMware tools software that is packaged with each OVA unless instructed to do so by Avaya. The supplied version is the supported release and has been thoroughly tested. Related links VMware best practices on page 71
VMware Snapshots A snapshot preserves the state and data of a virtual machine at a specific point in time. You can create a snapshot before upgrading or installing a patch. The best time to take a snapshot is when no applications in the virtual machine are communicating with other computers. The potential for problems is greatest if the virtual machine is communicating with another computer. For example, if you take a snapshot while the virtual machine is downloading a file from a server on the network, the virtual machine continues downloading the file and communicating its progress to the server. If you revert to the snapshot, communications between the virtual machine and the server are confused and the file transfer fails.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 73 Comments on this document? [email protected] Best Practices
Snapshot considerations Keep in mind that Snapshots can: • Consume large amounts of data resources • Cause increased CPU loads on the host • Affect performance • Affect service Note: Only utilize snapshots at the direction of Avaya. Caution: • Snapshot operations can adversely affect service. Before performing a snapshot operation, you must stop the application that is running on the virtual machine or place the application out-of-service. When the snapshot operation is complete, start or bring the application back into service. • Do not keep snapshots for extended operation and do not use a single snapshot for more than 24 to 72 hours. Consolidate or remove the Snapshot after temporary maintenance operation is complete. For more information, go to VMware Knowledge Base and search for Best Practices for virtual machine snapshots in the VMware environment. Related links VMware best practices on page 71
Resource reservation About this task Resource reservation should be disabled in all virtual machines running on an Avaya Solutions Platform 4200 racks. Use the following procedure to confirm the status of resource reservation and disable it if necessary. Procedure 1. Connect to the Windows MSC. 2. Connect to vCenter using the VMware vSphere thick client. 3. Select Home > Inventory > Hosts and Clusters from the menu. 4. Select the Avaya Pod Fx cluster. 5. Select the Resource Allocation tab. 6. Click CPU next to View. 7. Select each deployed VM from the list and confirm it does not have CPU reservation configured in the Reservation —MHz column.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 74 Comments on this document? [email protected] VMware best practices
8. Perform the following steps if a VM has CPU reservation configured. a. Right-click the VM. b. Click Edit Resource Settings. c. Set the CPU reservation value to 0 MHz. d. Select the Unlimited check box under Reservation. e. Save the new settings. 9. Click Memory next to View. 10. Select each deployed VM from the list and confirm it does not have Memory reservation configured in the Reservation —MB column. 11. Perform the following steps if a VM has Memory reservation configured. a. Right-click the VM. b. Click Edit Resource Settings. c. Set the Memory reservation value to 0 MB. d. Select the Unlimited check box under Reservation. e. Save the new settings. Related links VMware best practices on page 71
September 2020 Avaya Solutions Platform 4200 Series Solution Description 75 Comments on this document? [email protected] Chapter 9: Resources
Documentation The following documents are available on the Avaya support site at http://support.avaya.com/:
Title Description Audience Avaya Solutions Platform 4200 series Avaya Solutions Platform 4200 series Describes the key features IT Management, sales and Solution Description of Avaya Solutions deployment engineers, solution Platform. architects, and support personnel. Avaya Solutions Platform 4200 series Describes Avaya Solutions IT Management, sales and Baseline Platform 4200 series deployment engineers, solution software and hardware architects, and support personnel. baseline components. Avaya Solutions Platform 4200 series Identifies Avaya Solutions IT Management, sales and Read Me First Platform 4200 series deployment engineers, solution media kit and refers to the architects, and support personnel. documentation reference for all Avaya Solutions Platform 4200 series components. Documentation Reference for Avaya Identifies Avaya Solutions IT Management, sales and Solutions Platform 4200 series Platform 4200 series deployment engineers, solution customer documentation architects, and support personnel. as well as the Avaya and non-Avaya products included in the Avaya Solutions Platform 4200 series solution, and lists the associated customer documentation. Installing and Maintaining the Avaya Describes how to install IT Management, sales and Solutions Platform 4200 series Avaya Solutions Platform deployment engineers, solution 4200 series. architects, and support personnel. Table continues…
September 2020 Avaya Solutions Platform 4200 Series Solution Description 76 Comments on this document? [email protected] Documentation
Title Description Audience Upgrading Avaya Solutions Platform Provides an overview of IT Management, sales and 4200 series using the Management Management Server deployment engineers, solution Server Console Console for Avaya architects, and support personnel. Solutions Platform 4200 series. This document also provides instructions to access and use applications in the Management Console. Configuring and Administering Avaya Provides an overview of IT Management, sales and Orchestrator Avaya Orchestrator and deployment engineers, solution instructions to access and architects, and support personnel. use Avaya Orchestrator. Avaya Solutions Platform 4200 series Contains advice, End users, Avaya certified Troubleshooting solutions, and procedures technicians, Avaya partners, for dealing with common Avaya Sales Engineers (SE), issues encountered while Avaya System Integrators (SI). using Avaya Solutions Platform 4200 series. Avaya Solutions Platform 4200 series Contains information on IT Management, sales and Interoperability Matrix the hardware and software deployment engineers, solution components supported in architects, and support personnel. each release. Avaya Solutions Platform 4200 series This document provides a IT Management, sales and Port Matrix list of interfaces, TCP and deployment engineers, solution UDP ports that hardware architects, and support personnel. components and applications use for intra- cluster connections and communication with external applications or devices.
Related links Finding documents on the Avaya Support website on page 77 Avaya Documentation Center navigation on page 78
Finding documents on the Avaya Support website Procedure 1. Navigate to http://support.avaya.com/. 2. At the top of the screen, type your username and password and click Login. 3. Click Support by Product > Documents.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 77 Comments on this document? [email protected] Resources
4. In Enter your Product Here, type the product name and then select the product from the list. 5. In Choose Release, select an appropriate release number. 6. In the Content Type filter, click a document type, or click Select All to see a list of all available documents. For example, for user guides, click User Guides in the Content Type filter. The list displays the documents only from the selected category. 7. Click Enter. Related links Documentation on page 76
Avaya Documentation Center navigation The latest customer documentation for some programs is now available on the Avaya Documentation Center website at https://documentation.avaya.com. Important: For documents that are not available on Avaya Documentation Center, click More Sites > Support on the top menu to open https://support.avaya.com. Using the Avaya Documentation Center, you can: • Search for content by doing one of the following: - Click Filters to select a product and then type key words in Search. - From Products & Solutions, select a solution category and product, and then select the appropriate document from the list. • Sort documents on the search results page.
• Click Languages ( ) to change the display language and view localized documents. • Publish a PDF of the current section in a document, the section and its subsections, or the entire document. • Add content to your collection by using My Docs ( ). Navigate to the Manage Content > My Docs menu, and do any of the following: - Create, rename, and delete a collection. - Add topics from various documents to a collection. - Save a PDF of selected content in a collection and download it to your computer. - Share content in a collection with others through email. - Receive collection that others have shared with you.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 78 Comments on this document? [email protected] Training
• Add yourself as a watcher using the Watch icon ( ). Navigate to the Manage Content > Watchlist menu, and do the following: - Enable Include in email notification to receive email alerts. - Unwatch selected content, all content in a document, or all content on the Watch list page. As a watcher, you are notified when content is updated or deleted from a document, or the document is removed from the website. • Share a section on social media platforms, such as Facebook, LinkedIn, and Twitter. • Send feedback on a section and rate the content. Note: Some functionality is only available when you log on to the website. The available functionality depends on the role with which you are logged in. Related links Documentation on page 76
Training Product training is available on the Avaya Learning website. For more information or to register, see http://avaya-learning.com.
Avaya Mentor videos Avaya Mentor videos are available on an Avaya-run Internet channel dedicated to technical content. Playlist categories include: • Unified Communications (tested on Internet Explorer and Firefox). • Contact Centers. • Networking. • Small and Midsize Business. • Uploaded videos. A composite of all available Avaya Mentor videos. Before you begin You must have a valid Internet browser installed and working on your device.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 79 Comments on this document? [email protected] Resources
About this task The Avaya Mentor videos include the following content categories: • How to install Avaya products. • How to configure Avaya products. • How to troubleshoot Avaya products. Procedure To go to Avaya Mentor videos, click the following link: http://www.youtube.com/avayamentor and perform one of the following actions: • Enter a keyword or words in the Search channel dialog box to search for a specific product or topic. • Click the name of a playlist to scroll through the available videos.
Support Go to the Avaya Support website at https://support.avaya.com for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes, downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise. Related links Using the Avaya InSite Knowledge Base on page 80
Using the Avaya InSite Knowledge Base The Avaya InSite Knowledge Base is a web-based search engine that provides: • Up-to-date troubleshooting procedures and technical tips • Information about service packs • Access to customer and technical documentation • Information about training and certification programs • Links to other pertinent information If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you can access the Knowledge Base without extra cost. You must have a login account and a valid Sold-To number.
September 2020 Avaya Solutions Platform 4200 Series Solution Description 80 Comments on this document? [email protected] Support
Use the Avaya InSite Knowledge Base for any potential solutions to problems. 1. Go to http://www.avaya.com/support. 2. Log on to the Avaya website with a valid Avaya user ID and password. The system displays the Avaya Support page. 3. Click Support by Product > Product-specific Support. 4. In Enter Product Name, enter the product, and press Enter. 5. Select the product from the list, and select a release. 6. Click the Technical Solutions tab to see articles. 7. Select relevant articles. Related links Support on page 80
September 2020 Avaya Solutions Platform 4200 Series Solution Description 81 Comments on this document? [email protected] Index
A S
Avaya support website ...... 80 searching for content ...... 78 sharing content ...... 78 sort documents by last updated ...... 78 C support ...... 80 collection Supported interconnection options ...... 64 delete ...... 78 edit name ...... 78 T generating PDF ...... 78 sharing content ...... 78 thick deployment ...... 72 content thin deployment ...... 72 publishing PDF output ...... 78 searching ...... 78 sharing ...... 78 V sort by last updated ...... 78 VMware Tools ...... 73 watching for updates ...... 78 W D watch list ...... 78 deployment thick ...... 72 thin ...... 72 documentation ...... 76 documentation center ...... 78 finding content ...... 78 navigation ...... 78 documentation portal ...... 78 finding content ...... 78 navigation ...... 78
F finding content on documentation center ...... 78
I
InSite Knowledge Base ...... 80
M
My Docs ...... 78
N new in this release ...... 9
P purpose ...... 7
September 2020 Avaya Solutions Platform 4200 Series Solution Description 82 Comments on this document? [email protected]