Avaya Collaboration Pod Release Notes

Transcription

1 Avaya Collaboration Pod Release Notes Release NN Issue September 2015

2 , Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, 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: or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, pre-installed on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Instance means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ( VM ) or similar deployment. Licence types Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A Unit means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Units may be linked to a specific, identified Server or an Instance of the Software. Database License (DL). End User may install and use each copy or an Instance of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicates with no more than one Instance of the same database. CPU License (CP). End User may install and use each copy or Instance of the Software on a number of Servers up to the number indicated in the order provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya s prior consent and payment of an upgrade fee. Named User License (NU). You may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya s sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). You may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickthrough license accompanying or applicable to the Software ( Shrinkwrap License ). Heritage Nortel Software Heritage Nortel Software means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Business in December The Heritage Nortel Software currently available for license from Avaya is the software contained within the list of Heritage Nortel Products located at LicenseInfo under the link Heritage Nortel Products or such successor site as designated by Avaya. For Heritage Nortel Software, Avaya grants You a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage

3 Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Virtualization Each virtual appliance has its own ordering code. Note that each instance of a virtual appliance must be ordered separately. If the enduser customer or Business Partner wants to install two of the same type of virtual appliances, then two virtual appliances of that type must be ordered. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: support.avaya.com/copyright or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks Avaya Aura is a registered trademark of Avaya Inc. The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. 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.

4 Contents Chapter 1: Introduction... 6 Purpose... 6 Intended audience... 6 Support... 7 Product Registration... 8 Searching a documentation collection... 8 Subscribing to e-notifications... 9 Warranty Chapter 2: New in Release Features Avaya Collaboration Pod infrastructure HP compute servers Pod Orchestration Suite Avaya Diagnostic Server Avaya Aura Conferencing Avaya Session Border Controller for Enterprise Virtualized Environment Avaya Scopia Other Changes Chapter 3: New in Release New in Release Features Chapter 4: Important notices Collaboration Pod component list Scaling capabilities Avaya Collaboration Pod for Enterprise Communications release list Avaya Collaboration Pod for Unified Communications as a Service release list Avaya Collaboration Pod for Contact Center as a Service release list Software and Virtual Appliances Avaya Collaboration Pod software files Supported browsers VMware Snapshot considerations VMware considerations Chapter 5: Known issues and limitations AES issues COM issues IPFM issues SAL issues SMGR issues POS Issues Avaya Collaboration Pod Release Notes September 2015

5 Contents VPFM issues PVM Issues PUM Issues SBC Issues Switch issues EMC storage issues vcenter database issues Chapter 6: Resolved Issues Resolved Issues PVM issues PUM Issues Appendix A: Related resources Documentation reference Training Avaya Mentor videos September 2015 Avaya Collaboration Pod Release Notes 5

6 Chapter 1: Introduction Purpose This document provides important notices and describes known issues for Avaya Collaboration Pod Release Avaya Collaboration Pod infrastructure provides a new and convenient deployment model for virtualized services and solutions. There are three supported Avaya Collaboration Pod 4200 solutions: Avaya Collaboration Pod for Enterprise Communications Avaya Collaboration Pod for Unified Communications as a Service Avaya Collaboration Pod for Contact Center as a Service A Collaboration Pod 4200 is a secure enclosed 42U rack that contains the power, compute, storage, and networking hardware and software components required to support a converged solution. For release information on specific components in the Collaboration Pod 4200, refer to the release notes for the individual components; for example: Avaya Virtual Services Platform 7000 Series. Intended audience The intended audience for this document can include: system administrators data center personnel Avaya Sales Engineers Avaya Systems Engineers certified repair and maintenance personnel 6 Avaya Collaboration Pod Release Notes September 2015

7 Support Support The Avaya Collaboration Pod is an integrated solution with integrated support. Integrated support means that Avaya support personnel can isolate and resolve any issues with hardware and software applications packaged within the Collaboration Pod. Avaya is responsible only for support of the Avaya and third-party hardware and software within the Collaboration Pod that has been purchased through Avaya as part of the Collaboration Pod, or that has been explicitly approved in writing by the Avaya Collaboration Pod product management team. Documentation for specific Avaya products is available on the Avaya website. Important: If you deviate from a Collaboration Pod release software baseline, change physical equipment or virtual machines, modify network configurations, or add custom applications to a Collaboration Pod in any way, without express consent from Avaya, you will void warranty and service contracts for the Collaboration Pod. Avaya is not responsible for any unapproved third-party applications or hardware, or the direct or indirect impact of same, if installed by the customer. To ensure the integrity of a Collaboration Pod solution and product warranties, any changes must be approved in writing by the Avaya Collaboration Pod product management team (podsupport@avaya.com). Important: Do not install patches, software, or hardware for Collaboration Pod components without the express consent of Avaya support personnel trained and certified in support for the specialized combinations of hardware and software that make up each Collaboration Pod. You must ensure that automatic software updates are disabled for applications. Avaya tests updates to determine compatibility and Avaya will advise you about updates as they are verified and approved for use. You can install important Windows updates on the Windows Virtual Machines running on a Collaboration Pod, see and follow your corporation security policies regarding Windows updates. About this task Avaya Support includes: Products Downloads and documents Service requests Parts replacement September 2015 Avaya Collaboration Pod Release Notes 7

8 Introduction Tools Community support forum and DevConnect Training Help and policies Alerts and reports Procedure 1. Go to the Avaya Support home page, Site registration is required to access Self Service Tools and Downloads. Registration instructions are available on the Support home page. 2. From the Support home page: Enter a keyword in the Avaya Support search dialog box. Click any of the topic-based links on the page. Related Links Product Registration on page 8 Product Registration To prevent service interruption, you must register your Collaboration Pod products. The following are the available methods for Collaboration Pod product Registration: Implementation as a service - If Avaya Professional Services (APS) provided implementation Services onsite, APS 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 at (Document ID: ). Product registration is a required element for effective Avaya customer support. You must follow the Partner and Customer Registration Guidance in the Avaya Global Registration Process to help ensure the seamless support you have come to expect from Avaya. Searching a documentation collection On the Avaya Support website, you can download the documentation library for a specific product and software release to perform searches across an entire document collection. For example, you 8 Avaya Collaboration Pod Release Notes September 2015

9 Subscribing to e-notifications can perform a single, simultaneous search across the collection to quickly find all occurrences of a particular feature. Use this procedure to perform an index search of your documentation collection. Before you begin Download the documentation collection zip file to your local computer. You must have Adobe Acrobat or Adobe Reader installed on your computer. Procedure 1. Extract the document collection zip file into a folder. 2. Navigate to the folder that contains the extracted files and open the file named <product_name_release>.pdx. 3. In the Search dialog box, select the option In the index named <product_name_release>.pdx. 4. Enter a search word or phrase. 5. Select any of the following to narrow your search: Whole Words Only Case-Sensitive Include Bookmarks Include Comments 6. Click Search. The search results show the number of documents and instances found. You can sort the search results by Relevance Ranking, Date Modified, Filename, or Location. The default is Relevance Ranking. Subscribing to e-notifications Subscribe to e-notifications to receive an notification when documents are added to or changed on the Avaya Support website. About this task You can subscribe to different types of general notifications, for example, Product Correction Notices (PCN), which apply to any product or a specific product. You can also subscribe to specific types of documentation for a specific product, for example, Application & Technical Notes for Ethernet Routing Switch Procedure 1. In an Internet browser, go to 2. Type your username and password, and then click Login. 3. Click MY PROFILE. September 2015 Avaya Collaboration Pod Release Notes 9

10 Introduction 4. On the site toolbar, click your name, and then click E Notifications. 5. In the GENERAL NOTIFICATIONS area, select the required documentation types, and then click UPDATE. 6. Click OK. 7. In the PRODUCT NOTIFICATIONS area, click Add More Products. 8. Scroll through the list, and then select the product name. 10 Avaya Collaboration Pod Release Notes September 2015

11 Warranty 9. Select a release version. 10. Select the check box next to the required documentation types. 11. Click Submit. Warranty Avaya provides a limited warranty on its Hardware and Software ( Product(s) ). For more information on the Collaboration Pod warranty, see Support on page 7. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this Product while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: 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 2015 Avaya Collaboration Pod Release Notes 11

12 Chapter 2: New in Release The following sections detail what is new in Avaya Collaboration Pod Release Avaya Collaboration Pod Release supports the following solutions: Avaya Collaboration Pod for Enterprise Communications Release 1.1 Avaya Collaboration Pod for Unified Communications as a Service Release 1.2 Avaya Collaboration Pod for Contact Center as a Service Release 1.0 Features See the following sections for information about feature changes. Avaya Collaboration Pod infrastructure Avaya Collaboration Pod Release infrastructure updates include: HP compute servers. VSP 4850GTS aggregation switches updated to Release VSP 7024XLS network switches updated to Release EMC VNX 5300 storage array updated to Release Avaya Pod Orchestration Suite (POS) updated to Release Collaboration Pod Release provides additional software updates to include important or critical security patches for various applications. For more information, see Software and Virtual Appliances on page 34 and Avaya Collaboration Pod software files on page 37. HP compute servers Collaboration Pod Release introduces support for HP ProLiant DL360p and DL360e Generation 8 compute servers. Collaboration Pod supports configurations using the supported HP compute servers, Lenovo compute servers, or a mix of HP and Lenovo compute servers. 12 Avaya Collaboration Pod Release Notes September 2015

13 Features Pod Orchestration Suite Collaboration Pod Release introduces Pod Orchestration Suite (POS) Release POS contains all of the visualization and management applications required to configure, orchestrate, manage, and monitor your Collaboration Pod. POS Release includes the following enhancements: Support for HP ProLiant DL360p and DL360e Generation 8 compute servers. Support for upgraded infrastructure firmware. Patches for security issues, including Shellshock. For Collaboration Pod Release 2.0.1, the following POS applications have been updated to the following releases: Pod Visualization Manager (PVM) Release Configuration and Orchestration Manager (COM) Release and Virtual Provisioning System (VPS) Release Visualization Performance and Fault Monitoring (VPFM) Release IP Flow Manager (IPFM) Release Management Server Console (MSC) Release including Pod Utility Module (PUM) Release Identity Engines (IDE) Release Secure Remote Access (SRA) Release Where required, all POS applications listed have been updated to include support for HP ProLiant DL360p and DL360e Generation 8 compute servers and patches for important security issues. For more software release information, see Software and Virtual Appliances on page 34. Avaya Diagnostic Server Collaboration Pod Release introduces an option for Avaya Diagnostic Server(ADS) Release 2.0 as a post-delivery add-on available for all Collaboration Pod solutions. ADS is an Avaya serviceability solution for advanced diagnostic services and remote support to Avaya products. ADS includes Secure Access Link (SAL) 2.3 Gateway and SLAMon Server including Endpoint Diagnostics and Network Monitoring. Avaya Aura Conferencing Collaboration Pod Release introduces an option for Avaya Aura Conferencing Release 8.0 as a post-delivery add-on available for Avaya Collaboration Pod for Enterprise Communications solutions. September 2015 Avaya Collaboration Pod Release Notes 13

14 New in Release Avaya Aura Conferencing (AAC) is a next generation unified multimodal collaboration application. AAC is an on-premise collaboration solution that can provide audio, video, and web conferencing capabilities. Avaya Session Border Controller for Enterprise Virtualized Environment Collaboration Pod Release introduces an option for Avaya Session Border Controller for EnterpriseVirtualized Environment (SBCE VE) Release 6.3 as a post-delivery add-on available for Avaya Collaboration Pod for Enterprise Communications solutions. Avaya Session Border Controller for Enterprise dedicated hardware servers are available and supported for all Collaboration Pod solutions. Avaya Session Border Controller for Enterprisesecures SIP and VOIP connectivity, and provide a secure interface for SIP trunking and remote worker connectivity. Avaya Scopia Collaboration Pod Release introduces an option for Avaya Scopia Release 8.3 as a postdelivery add-on available for Avaya Collaboration Pod for Enterprise Communications solutions. Avaya Collaboration Pod for Enterprise Communications with Avaya Scopia requires Elite 6140 (MCU) hardware for videoconferencing. Avaya Scopia also requires Scopia Management Server and Scopia Desktop virtualized applications running on the Collaboration Pod. Other Changes This document now provides the release notes for all supported solutions available for the Avaya Collaboration Pod. The document title has changed to Avaya Collaboration Pod Release Notes (NN ). Therefore, as of Release the following documents are retired: Avaya Collaboration Pod for Unified Communications as a Service Release Notes (NN ) Avaya Collaboration Pod for Contact Center as a Service Release Notes (NN ) 14 Avaya Collaboration Pod Release Notes September 2015

15 Chapter 3: New in Release 2.0 New in Release 2.0 The following sections detail what is new in Avaya Collaboration Pod Release 2.0. Avaya Collaboration Pod Release 2.0 supports the following solutions: Avaya Collaboration Pod for Enterprise Communications Release 1.1 Avaya Collaboration Pod for Unified Communications as a Service Release 1.2 Avaya Collaboration Pod for Contact Center as a Service Release 1.0 For more information, see Features on page 15. Features See the following sections for information about feature changes. Avaya Collaboration Pod infrastructure Avaya Collaboration Pod Release 2.0 infrastructure updates include: Lenovo compute servers. VSP 4850GTS aggregation switches replace the ERS 4826 switches that were used in Release 1.0. The VSP 4000 series switches are configured for static routing. VSP 7024XLS network switches. The VSP 7000 series switches are configured for Fabric Connect. The VSP 7000 switches are clustered and the VSP 4000 switches are standalone. Switched Power Distribution Units. 20 A and 30 A are available. Extension Pods. For more information, see Collaboration Pod component list on page 21. The software and applications included in Collaboration Pod Release 2.0 have been updated to the latest versions available. September 2015 Avaya Collaboration Pod Release Notes 15

16 New in Release 2.0 Pod orchestration suite Pod Orchestration Suite (POS) contains all of the visualization and management applications required to configure, orchestrate, manage, and monitor your Pod. For Collaboration Pod Release 2.0, POS has been updated to Release 2.0. For more information, see Pod orchestration on Scaling capabilities on page 25. Avaya Aura Virtualized Environment Release 6.2, Feature Pack 3 Avaya Aura Virtualized Environment 6.2 FP3 provides a hardware-efficient simplified solution for adding the latest Avaya Aura capabilities. Avaya Aura Virtualized Environment 6.2, Feature Pack 3 includes the following updates: Communication Manager Session Manager System Manager Presence Services Application Enablement Services For more information, see Collaboration Pod component list on page 21. Avaya VSP 7000 Series switches In the Avaya Collaboration Pod two VSP 7024XLS switches are provided, including one VSP 7008XT Media Dependent Adapter in each VSP 7000 series switch. For Collaboration Pod Release 2.0, the VSP 7000 series switch software is upgraded to Release The ability to use SPB and Fabric Connect has also been added to the VSP 7000 series switches. For more information, see Collaboration Pod component list on page 21. Avaya VSP 4000 Series switches For Collaboration Pod Release 2.0, two Avaya Virtual Services Platform 4850s are provided in each base Pod. Extension Pods also support VSP 4850s to provide additional ports, scalability, and aggregation. The Release 3.1 VSP 4000 series switches replace the ERS 4826 switches that were used in Collaboration Pod Release 1.0. The VSP 4000 series switches are equipped with a carrier-grade operating system two AC power supplies that increase network agility. With a simplified infrastructure, the 4000 series provides comprehensive array of network services, including Layer 2 and Layer 3 virtualization with optimized routing and IP multicast support across the entire enterprise. For more information, see Collaboration Pod component list on page Avaya Collaboration Pod Release Notes September 2015

17 New in Release 2.0 Networking and routing configuration All Collaboration Pods use VSP 7024XLS and VSP 4850GTS switches, enhancing the networking capabilities with the following new features: VSP 4850GTS aggregation switches provide additional ports for scalability and link aggregation. VSP 4850GTS aggregation switches configured with static routes for your Data Center s routing environment. VSP 7024XLS network switches provide a Fabric Connect multi-terabit Top-of-Rack configuration to interconnect multiple Collaboration Pods. Fabric Connect, leveraging Shortest Path Bridging (SPB) on networking platforms increases bandwidth, fail over, and scalability of Collaboration Pod networks. For more information, see Collaboration Pod component list on page 21. Acme Packet Net Net Session Border Controller The Acme Packet Net-Net SBC 4500 is a scalable Session Border Controller. It offers the following features: High-performance dedicated multi-processors High-availability redundant components Segments end users so that all end users have their own VLAN Provides emergency calling services to end users For more information, see Collaboration Pod component list on page 21. Avaya Secure Remote Access Avaya Secure Remote Access (SRA) is an optional security feature that runs as a VM appliance on the Avaya Collaboration Pod. For more information, see Scaling capabilities on page 25. Avaya Aura Experience Portal 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 via AAEP. It includes the following components: Experience Portal Manager (EPM) a Web interface that enables users to perform administrative, configuration and maintenance tasks on the Experience Portal system. Application Execution Environment. One or more Media Processing Platform (MPP) servers, which process all incoming and outgoing calls. and the following external systems: Private Branch Exchange (PBX) servers September 2015 Avaya Collaboration Pod Release Notes 17

18 New in Release 2.0 ASR and TTS speech servers Application Servers Single server and multiple server configurations are available for the Experience Portal dependent on the number of Collaboration Pod telephony ports. For more information, see Collaboration Pod component list on page 21. Avaya Call Management System Avaya Call Management System (CMS) is a software product for businesses and organizations that receive a large volume of telephone calls processed through the Automatic Call Distribution (ACD) feature of the Avaya Aura Communication Manager. Avaya Call Management System also includes the Avaya CMS Supervisor client that provides a graphical user interface and comprehensive administration and reporting capabilities using a familiar Microsoft Windows interface. CMS provides real-time, historical, and integrated reporting to track all activities in the contact center. Using CMS reports, you can make decisions regarding entities like agents, split/skills, vectors, vector directory numbers (VDN), and trunks. Geographic Redundancy For geographic redundancy configurations, two Collaboration Pods (one for each data center) are provided. The Collaboration Pod must use Avaya Aura Enterprise Survivable Core to establish redundancy between data centers. The applications on the Collaboration Pod are configured as required for failover and redundancy support, including Communication Manager (ESS Mode Simplex/Duplex), System Manager Geographic Redundancy, Supplementary Session Managers, and Supplementary G450 Media Gateways. For redundancy between data centers, the existing features of Avaya Aura are utilized. The VMware features for multi-data center (Site Recovery Manager) are not used. In this configuration the Mains are a pair of Communication Managers in the primary Pod or Data Center connected to the ESS pair of Communication Managers in the secondary Pod or Data center. The ESS pair is in standby mode ready to take over in the event that the Mains are disabled for any reason. Each Collaboration Pod runs a separate high availability instance of Pod Orchestration Suite (POS). If a server fails, POS will migrate to the next available compute server within the Collaboration Pod. Geographic Redundant POS management is not available. The following figure shows a two Data Center deployment that is representative of an Enterprise or UCaaS solution with supporting networking and other optional hardware components. 18 Avaya Collaboration Pod Release Notes September 2015

19 New in Release 2.0 Figure 1: Example Avaya Core Survivability with Networking and Hardware Components The following figure shows physical and logical arrangement of equipment and Virtual Machines across two Data Centers. Figure 2: Conceptual Enterprise Solution September 2015 Avaya Collaboration Pod Release Notes 19

20 New in Release 2.0 Multiple instance deployments Multiple instance Avaya Aura deployments for the Avaya Collaboration Pod is defined as multiple Avaya Aura Session Manager and Avaya Aura Communication Manager applications running on the Collaboration Pod. After server requirements exceed the current capabilities, you can add extra servers to increase the overall capacity and provide additional memory for more applications. You can also add any combination of single application or solution instances if your system resources can support the deployment. You can add servers, storage, media gateways, networking components, and extension pods to add system resources. For me information, see Avaya Collaboration Pod Solution Description (NN ). Management server console The management server console is used to deploy, upgrade, and maintain Avaya Collaboration Pod software and components. A management server console is available in Avaya Collaboration Pod R2.0 solutions. The management server console provides maintenance and utility software to maintain or upgrade Collaboration Pod software and components. Certified professionals install and use the server to deploy additional VMs or multiple instances of software components using VMware. Extension pods Some Avaya Collaboration Pod solutions might require additional servers or appliances placed into utility racks, called Extension Pods. Each Extension Pod is a 42 Rack Mount Unit (RMU) enclosure that contains at least one compute server, networking switches, and power distribution units. The compute server provides the Pod Orchestration Suite (POS) and Serviceability Agent to monitor and manage the Extension Pod components. Extension pods can provide Media Gateways, Session Border Controllers, additional storage, or compute servers as additional hardware. Extension Pods are available in two basic configurations, each can be configured with various additional equipment: Gateway Extension Pod (two VSP 4850GTS) 1/10 GB Extension Pod (two VSP 4850GTS and two VSP 7024XLS) For more information, see Collaboration Pod component list on page Avaya Collaboration Pod Release Notes September 2015

21 Chapter 4: Important notices This section provides a component list for this release and additional important information. Collaboration Pod component list The following table summarizes the hardware and software components that can form the Avaya Collaboration Pod. Component quantities and specific details depend on the Bill of Materials (BOM) generated from the specific Collaboration Pod order. For information regarding Avaya and third-party hardware and software release versions available for your Collaboration Pod, refer to the Release Notes document for your Collaboration Pod solution, or refer to Avaya Collaboration Pod Baseline (NN ). Not all Avaya Collaboration Pod configurations require all the components shown in the following table. Table 1: Default and optional components Component Enclosure and rack assembly Description One 24 wide x 51 deep 42 rack mount unit (RMU) high enclosure with rack assembly, front door with lock, split rear door with lock, (depth includes front and rear doors) Fully assembled Collaboration Pods ship with the doors unlocked. Keys are zip-tied to the inside of the front door. Power Extension Pods are utility racks that contain additional servers or appliances that are necessary for some Avaya Collaboration Pod solutions. Extension Pods are available in Gateway, and 1/10GB configurations. Up to three pairs of 20 A switched power distribution units (PDU) delivering a total of 9,900 Watts. Table continues September 2015 Avaya Collaboration Pod Release Notes 21

22 Important notices Component Description Gateway Extension Pods can support one pair of 20 A switched horizontal PDUs, delivering a total of 3,300 Watts. OR Up to three pairs of 30 A switched PDUs, delivering a total of 15,000 Watts. Cooling Gateway Extension Pods can support one pair of 30 A switched horizontal PDUs, delivering a total of 5,000 Watts. The Collaboration Pod is designed for front to back cooling. Rear facing components such as the networking switches use back to front airflow which provides consistent front to back airflow within the Collaboration Pod enclosure. 12 cooling fans mounted on the rear doors provide 2400 CFM of airflow, blowing air out of the enclosure. Networking Gateway Extension Pods or Extension Pods with horizontal PDUs are configured with six active cooling fans mounted on the rear doors which provides 1200 CFM of airflow. Two Avaya VSP 7024XLS (Top of Rack networking switches), rack mounting hardware, power supplies, Media Dependent Adapter (MDA), and Fabric Interconnect cables. Each switch provides: 24 SFP+ ports supporting 10 Gbps or 1 Gbps Ethernet transceivers Eight 10GBASE-T ports on 7008XT MDA Multi-Terabit Fabric Connect, using Shortest Path Bridging (SPB) Two Avaya VSP 4850 GTS (Gigabit Ethernet aggregation and routing switches), rack mounting hardware, power cord, main power supply and redundant power supply. Each switch provides: BASE-T ports, two shared SFP ports, two SFP+ ports Routing support SPB support Gateway Extension Pods or Extension Pods with horizontal PDUs are typically configured with two Avaya VSP 4850GTS switches only. Table continues 22 Avaya Collaboration Pod Release Notes September 2015

23 Collaboration Pod component list Component Compute servers Storage Gateways Session Border Controllers Virtualization Description Networking switches are installed facing the rear of the Collaboration Pod enclosure. Compute servers are physical servers; the ESXi hosts for virtualization. Base Pods: A minimum of two compute servers Extension Pods: A minimum of one compute server You can add additional compute servers to Base Pods and Extension Pods. The maximum amount of compute servers is dependent upon RMU slots, power limits, and thermal limits for your specific configuration. EMC storage platform supporting high availability and redundancy. Additional Disk Array Enclosures (DAE) are available and can provide additional application or recording storage. A maximum of seven DAE are supported in each Collaboration Pod. You may require Avaya G450 Media Gateways depending on your Collaboration Pod solution and requirements. Gateways are 3U form factor devices, each Gateway can provide a maximum of eight supplemental media modules for external interfaces. Gateways are installed facing the rear of the enclosure. You may require Avaya Session Border Controllers depending on your Collaboration Pod solution and requirements. You can install more than one SBCE unit to work in conjunction with the SBC Administration server. Avaya Session Border Controller for Enterprise You can install Acme Packet Session Border Controllers in Extension Pods. VMware vsphere ESXi 5.1 U2 and important security patches Collaboration Pod component applications are virtualized and run on compute servers. Compute servers are physical ESXi host servers. Additional virtual appliances are optional. Avaya verified third party virtual Network Load Balancers: - Riverbed 9.4 OVF 64 bit Avaya verified third party virtual Firewalls: - Palo Alto Networks VM 300 version Table continues September 2015 Avaya Collaboration Pod Release Notes 23

24 Important notices Component Management Description - Fortinet FortiGate-VM VM01 build 0234 Avaya Pod Orchestration Suite VMware vcenter Server Oracle SQL SE1 11g database for vcenter (optional) EMC Unisphere Manager HP Integrated Lights-Out or Lenovo ThinkServer Management Module Avaya and Avaya Aura software licenses Management Server console (Windows 2008 R2) including Avaya Pod Utility Module Avaya Aura Collaboration Suite, up to maximum capacities supported by Avaya Aura products. Avaya Aura Communication Manager for the Virtualized Environment Avaya Aura Messaging (AAM) Virtual Environment Avaya Aura Session Manager for the Virtualized Environment Avaya Aura System Manager for the Virtualized Environment Avaya WebLM for the Virtualized Environment Avaya Secure Access Link 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 base license Configuration and Orchestration Manager (COM) for 50 devices plus an additional 200 device upgrade base license Virtualization Provisioning Service (VPS), for 20 devices base license Visualization Performance and Fault Monitoring (VPFM), for 500 devices plus an additional 2000 device increment. base license IP Flow Manager (IPFM), for four devices (200,000 flows per minute) Avaya Pod Orchestration Suite, includes Pod Visualization Manager (PVM) Identity Engines Ignition Server base license, starter kit includes 5 Authenticators Table continues 24 Avaya Collaboration Pod Release Notes September 2015

25 Scaling capabilities Component Software licenses (other) Description Identity Engines Ignition Guest Manager license base license Avaya Secure Remote Access, for 50 users (expandable up to 5,000 users for each SRA VM) Avaya Session Border Controller for Enterprise R6.2 (optional) Avaya Call Management System (CMS) (optional) Avaya Aura Experience Portal (optional) Agile Communication Environment (optional) Avaya Control Manager Server and SQL Server (with Billing) (optional) Application Enablement Services (optional) ANAV (optional) Avaya Elite Multichannel (optional) Avaya Aura Workforce Optimization (optional) VMware ESXi Enterprise EMC base license Unisphere Block and VNX Operating Environment (OE) VMware ESXi Enterprise Plus (optional) Scaling capabilities Avaya installs, connects, configures and tests each Collaboration Pod solution for the end user. However, as your needs grow, you can upgrade your Avaya Collaboration Pod to include more compute servers, storage enclosures, networking, and other equipment. Depending on your system capacity, you purchase more licenses per seat to provide applications to more users. Important: Changes to your Collaboration Pod must be performed by Avaya certified personnel. For more information, see the Support section of this document. You can upgrade Collaboration Pods without affecting call traffic. All components are completely redundant and hot swappable. The following tables show the maximum users for a single instance of a supported Collaboration Pod solution. September 2015 Avaya Collaboration Pod Release Notes 25

26 Important notices Table 2: Capacities for Avaya Collaboration Pod for Enterprise Communications Release 1.1. Max # of UC users Single Instance: 36,000 SIP 18,000 H.323 Refer to Avaya Aura Virtualized Environment 6.2, FP3 offer definition for capacity combinations. Max # of CC users Single Instance: 5,000 SIP 10,000 H.323 Refer to Avaya Aura Virtualized Environment 6.2, FP3 offer definition for capacity combinations. Table 3: Capacities for Avaya Collaboration Pod for Unified Communications as a Service Release 1.2 Max # of UC users Single Instance: 10,000 SIP 250 Tenants Max # of CC users n/a Table 4: Capacities for Avaya Collaboration Pod for Contact Center as a Service Release 1.0 Max # of UC users Single Instance: 5,000 SIP (UC and CC combined) 125 Tenants Max # of CC users Single Instance: 2,500 SIP 125 Tenants UC for Back Office, Telephony only. You can add resources such as G450 Media Gateways, Session Border Controllers and Avaya Aura Messaging servers. Collaboration Pod provides the same trunk limits as Avaya Aura Session Manager and Avaya Aura Communication Manager Release 6.2, FP3. Avaya Collaboration Pod for Enterprise Communications release list The following table shows the hardware and software component release versions supported for Avaya Collaboration Pod for Enterprise Communications solutions. Quantities and specific details depend on the Bill of Materials (BOM) generated from the specific Collaboration Pod order. 26 Avaya Collaboration Pod Release Notes September 2015

27 Avaya Collaboration Pod for Enterprise Communications release list Required and optional components Important: The following specific software release versions have been tested and qualified in the Avaya Collaboration Pod. Do not upgrade or apply additional patches to the components without authorization from the Avaya Collaboration Pod support team. For more information, contact Component Included in Avaya Pod Orchestration Suite (POS) Release Service Pack Patch Pod Visualization Manager (PVM) Avaya Configuration and Orchestration Manager (COM) (includes Virtualization Provisioning Service (VPS) Release 1.0.3) Avaya IP Flow Manager (IPFM) Avaya Visualization Performance and Fault Manager (VPFM) Management Server Console (Windows 2008 R2) Pod Utility Module vsphere Desktop Client Unisphere Service Manager WinSCP SolarWinds TFTP Server PuTTY Notepad ++ Firefox Management Server console also provides a software and firmware repository. Avaya Identity Engines (IDE): (optional) Release Avaya Aura Utility Services 6.3 Secure Access Link 2.2 Avaya Diagnostic Server (optional) Avaya Secure Remote Access (optional) Avaya Aura Communication Manager Simplex and Duplex Table continues September 2015 Avaya Collaboration Pod Release Notes 27