Avaya Collaboration Pod Release Notes

Release 2.0.1 NN47204-400 Issue 04.05 September 2015 © 2013-2015, Avaya Inc. applicable number of licenses and units of capacity for which the All Rights Reserved. license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other Notice materials available to You. “Software” means computer programs in While reasonable efforts have been made to ensure that the object code, provided by Avaya or an Avaya Channel Partner, information in this document is complete and accurate at the time of whether as stand-alone products, pre-installed on hardware products, printing, Avaya assumes no liability for any errors. Avaya reserves and any upgrades, updates, patches, bug fixes, or modified versions the right to make changes and corrections to the information in this thereto. “Designated Processor” means a single stand-alone document without the obligation to notify any person or organization computing device. “Server” means a Designated Processor that of such changes. hosts a software application to be accessed by multiple users. “Instance” means a single copy of the Software executing at a Documentation disclaimer particular time: (i) on one physical machine; or (ii) on one deployed “Documentation” means information published by Avaya in varying software virtual machine (“VM”) or similar deployment. mediums which may include product information, operating Licence types instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Designated System(s) License (DS). End User may install and use Documentation does not include marketing materials. Avaya shall not each copy or an Instance of the Software only on a number of be responsible for any modifications, additions, or deletions to the Designated Processors up to the number indicated in the order. original published version of documentation unless such Avaya may require the Designated Processor(s) to be identified in modifications, additions, or deletions were performed by Avaya. End the order by type, serial number, feature key, Instance, location or User agrees to indemnify and hold harmless Avaya, Avaya's agents, other specific designation, or to be provided by End User to Avaya servants and employees against all claims, lawsuits, demands and through electronic means established by Avaya specifically for this judgments arising out of, or in connection with, subsequent purpose. modifications, additions or deletions to this documentation, to the Concurrent User License (CU). End User may install and use the extent made by End User. Software on multiple Designated Processors or one or more Servers, Link disclaimer 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 is not responsible for the contents or reliability of any linked Avaya, at its sole discretion, bases the pricing of its licenses and can websites referenced within this site or documentation provided by be, without limitation, an agent, port or user, an e-mail or voice mail Avaya. Avaya is not responsible for the accuracy of any information, account in the name of a person or corporate function (e.g., statement or content provided on these sites and does not webmaster or helpdesk), or a directory entry in the administrative necessarily endorse the products, services, or information described database utilized by the Software that permits one user to interface or offered within them. Avaya does not guarantee that these links will with the Software. Units may be linked to a specific, identified Server work all the time and has no control over the availability of the linked or an Instance of the Software. pages. Database License (DL). End User may install and use each copy or Warranty an Instance of the Software on one Server or on multiple Servers Avaya provides a limited warranty on Avaya hardware and software. provided that each of the Servers on which the Software is installed Refer to your sales agreement to establish the terms of the limited communicates with no more than one Instance of the same warranty. In addition, Avaya’s standard warranty language, as well as database. information regarding support for this product while under warranty is CPU License (CP). End User may install and use each copy or available to Avaya customers and other parties through the Avaya Instance of the Software on a number of Servers up to the number Support website: http://support.avaya.com or such successor site as indicated in the order provided that the performance capacity of the designated by Avaya. Please note that if You acquired the product(s) Server(s) does not exceed the performance capacity specified for the from an authorized Avaya Channel Partner outside of the United Software. End User may not re-install or operate the Software on States and Canada, the warranty is provided to You by said Avaya Server(s) with a larger performance capacity without Avaya’s prior Channel Partner and not by Avaya. consent and payment of an upgrade fee. Licenses Named User License (NU). You may: (i) install and use the Software THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA on a single Designated Processor or Server per authorized Named WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR User (defined below); or (ii) install and use the Software on a Server SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE so long as only authorized Named Users access and use the APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR Software. “Named User”, means a user or device that has been INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., expressly authorized by Avaya to access and use the Software. At ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS Avaya’s sole discretion, a “Named User” may be, without limitation, APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH designated by name, corporate function (e.g., webmaster or AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS helpdesk), an e-mail or voice mail account in the name of a person or OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES corporate function, or a directory entry in the administrative database NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS utilized by the Software that permits one user to interface with the OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA Software. AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA Shrinkwrap License (SR). You may install and use the Software in RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU accordance with the terms and conditions of the applicable license AND ANYONE ELSE USING OR SELLING THE SOFTWARE agreements, such as “shrinkwrap” or “clickthrough” license WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR accompanying or applicable to the Software (“Shrinkwrap License”). USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM Heritage Nortel Software YOU ARE INSTALLING, DOWNLOADING OR USING THE “Heritage Nortel Software” means the software that was acquired by SOFTWARE (HEREINAFTER REFERRED TO Avaya as part of its purchase of the Nortel Enterprise Solutions INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO Business in December 2009. The Heritage Nortel Software currently THESE TERMS AND CONDITIONS AND CREATE A BINDING available for license from Avaya is the software contained within the CONTRACT BETWEEN YOU AND AVAYA INC. OR THE list of Heritage Nortel Products located at http://support.avaya.com/ APPLICABLE AVAYA AFFILIATE (“AVAYA”). LicenseInfo under the link “Heritage Nortel Products” or such Avaya grants You a license within the scope of the license types successor site as designated by Avaya. For Heritage Nortel described below, with the exception of Heritage Nortel Software, for Software, Avaya grants You a license to use Heritage Nortel which the scope of the license is detailed below. Where the order Software provided hereunder solely to the extent of the authorized documentation does not expressly identify a license type, the activation or authorized usage level, solely for the purpose specified applicable license will be a Designated System License. The in the Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Software may be based on extent of activation or use The trademarks, logos and service marks (“Marks”) displayed in this authorized as specified in an order or invoice. site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its Copyright affiliates, or other third parties. Users are not permitted to use such Except where expressly stated otherwise, no use should be made of Marks without prior written consent from Avaya or such third party materials on this site, the Documentation, Software, Hosted Service, which may own the Mark. Nothing contained in this site, the or hardware provided by Avaya. All content on this site, the Documentation, Hosted Service(s) and product(s) should be documentation, Hosted Service, and the product provided by Avaya construed as granting, by implication, estoppel, or otherwise, any including the selection, arrangement and design of the content is license or right in and to the Marks without the express written owned either by Avaya or its licensors and is protected by copyright permission of Avaya or the applicable third party. and other intellectual property laws including the sui generis rights Avaya is a registered trademark of Avaya Inc. relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way All non-Avaya trademarks are the property of their respective owners. any content, in whole or in part, including any code and software Linux® is the registered trademark of Linus Torvalds in the U.S. and unless expressly authorized by Avaya. Unauthorized reproduction, other countries. 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 end- user 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: http:// 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 +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected]. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: http://support.avaya.com 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: http://support.avaya.com (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. 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...... 11 Chapter 2: New in Release 2.0.1...... 12 Features...... 12 Avaya Collaboration Pod infrastructure...... 12 HP compute servers...... 12 Pod Orchestration Suite...... 13 Avaya Diagnostic Server...... 13 Avaya Aura® Conferencing...... 13 Avaya Session Border Controller for Enterprise Virtualized Environment...... 14 Avaya Scopia®...... 14 Other Changes...... 14 Chapter 3: New in Release 2.0...... 15 New in Release 2.0...... 15 Features...... 15 Chapter 4: Important notices...... 21 Collaboration Pod component list...... 21 Scaling capabilities...... 25 Avaya Collaboration Pod for Enterprise Communications release list...... 26 Avaya Collaboration Pod for Unified Communications as a Service release list...... 29 Avaya Collaboration Pod for Contact Center as a Service release list...... 31 Software and Virtual Appliances...... 34 Avaya Collaboration Pod software files...... 37 Supported browsers...... 42 VMware Snapshot considerations...... 42 VMware considerations...... 43 Chapter 5: Known issues and limitations...... 44 AES issues...... 44 COM issues...... 45 IPFM issues...... 45 SAL issues...... 46 SMGR issues...... 46 POS Issues...... 46

4 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Contents

VPFM issues...... 47 PVM Issues...... 47 PUM Issues...... 48 SBC Issues...... 48 Switch issues...... 49 EMC storage issues...... 49 vCenter database issues...... 50 Chapter 6: Resolved Issues...... 51 Resolved Issues...... 51 PVM issues...... 51 PUM Issues...... 52 Appendix A: Related resources...... 53 Documentation reference...... 53 Training...... 53 Avaya Mentor videos...... 53

September 2015 Avaya Collaboration Pod Release Notes 5 Comments on this document? [email protected] Chapter 1: Introduction

Purpose This document provides important notices and describes known issues for Avaya Collaboration Pod Release 2.0.1. 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. Note: 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 Comments on this document? [email protected] 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. Note: 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 ([email protected]) . 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. Note: 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 Comments on this document? [email protected] Introduction

• Tools • Community support forum and DevConnect • Training • Help and policies • Alerts and reports Procedure 1. Go to the Avaya Support home page, www.avaya.com/support Note: 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 https://support.avaya.com/grt (Document ID: 100162279). 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 Comments on this document? [email protected] 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 .pdx. 3. In the Search dialog box, select the option In the index named .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 email 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 8800. Procedure 1. In an Internet browser, go to https://support.avaya.com. 2. Type your username and password, and then click Login. 3. Click MY PROFILE.

September 2015 Avaya Collaboration Pod Release Notes 9 Comments on this document? [email protected] 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 Comments on this document? [email protected] 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: 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 2015 Avaya Collaboration Pod Release Notes 11 Comments on this document? [email protected] Chapter 2: New in Release 2.0.1

The following sections detail what is new in Avaya Collaboration Pod Release 2.0.1. Avaya Collaboration Pod Release 2.0.1 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 2.0.1 infrastructure updates include: • HP compute servers. • VSP 4850GTS aggregation switches updated to Release 4.0.0 • VSP 7024XLS network switches updated to Release 10.3.2 • EMC VNX 5300 storage array updated to Release 5.32.000.5.216 • Avaya Pod Orchestration Suite (POS) updated to Release 2.0.1 Collaboration Pod Release 2.0.1 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 2.0.1 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 Comments on this document? [email protected] Features

Pod Orchestration Suite Collaboration Pod Release 2.0.1 introduces Pod Orchestration Suite (POS) Release 2.0.1. POS contains all of the visualization and management applications required to configure, orchestrate, manage, and monitor your Collaboration Pod. POS Release 2.0.1 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 2.0.1. • Configuration and Orchestration Manager (COM) Release 3.0.2.1 and Virtual Provisioning System (VPS) Release 1.0.3.1. • Visualization Performance and Fault Monitoring (VPFM) Release 3.0.3.2. • IP Flow Manager (IPFM) Release 2.0.3.1. • Management Server Console (MSC) Release 2.0.1 including Pod Utility Module (PUM) Release 2.0.1. • Identity Engines (IDE) Release 9.0.2. • Secure Remote Access (SRA) Release 2.0.1.0 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 2.0.1 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 2.0.1 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 Comments on this document? [email protected] New in Release 2.0.1

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 2.0.1 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. Note: 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 2.0.1 introduces an option for Avaya Scopia® Release 8.3 as a post- delivery 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 (NN47204–400). Therefore, as of Release 2.0.1 the following documents are retired: • Avaya Collaboration Pod for Unified Communications as a Service Release Notes (NN47204– 401) • Avaya Collaboration Pod for Contact Center as a Service Release Notes (NN47204–402)

14 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] 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 Comments on this document? [email protected] 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 6.3.4 • Session Manager 6.3.6 • System Manager 6.3.6 • Presence Services 6.2.2 • Application Enablement Services 6.3.0 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 10.3.1. 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 21.

16 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] 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 Comments on this document? [email protected] 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 Comments on this document? [email protected] 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 Comments on this document? [email protected] 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 (NN47204–107). 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. Note: 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 21.

20 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] 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 (NN47204–104). Note: Not all Avaya Collaboration Pod configurations require all the components shown in the following table.

Table 1: Default and optional components

Component Description Enclosure and rack assembly 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)

Note: Fully assembled Collaboration Pods ship with the doors unlocked. Keys are zip-tied to the inside of the front door. 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. Power 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 Comments on this document? [email protected] Important notices

Component Description Note: 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. Note: Gateway Extension Pods can support one pair of 30 A switched horizontal PDUs, delivering a total of 5,000 Watts. Cooling 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. Note: 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. Networking 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: • 48 1000BASE-T ports, two shared SFP ports, two SFP+ ports • Routing support • SPB support

Note: 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 Comments on this document? [email protected] Collaboration Pod component list

Component Description Note: Networking switches are installed facing the rear of the Collaboration Pod enclosure. Compute servers 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. Storage 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. Gateways 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. Note: Gateways are installed facing the rear of the enclosure. Session Border Controllers 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. Virtualization 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 6.0.0 Table continues…

September 2015 Avaya Collaboration Pod Release Notes 23 Comments on this document? [email protected] Important notices

Component Description - Fortinet FortiGate-VM VM01 build 0234 Management • 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 • Management Server console (Windows 2008 R2) including Avaya Pod Utility Module Avaya and Avaya Aura® software • Avaya Aura® Collaboration Suite, up to maximum capacities licenses 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 Comments on this document? [email protected] Scaling capabilities

Component 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) Software licenses (other) • 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. Note: 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 Comments on this document? [email protected] Important notices

Table 2: Capacities for Avaya Collaboration Pod for Enterprise Communications Release 1.1.

Max # of UC users Max # of CC users Single Instance: Single Instance: 36,000 SIP 5,000 SIP 18,000 H.323 10,000 H.323 Refer to Avaya Aura® Virtualized Environment 6.2, Refer to Avaya Aura® Virtualized Environment 6.2, FP3 offer definition for capacity combinations. 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 Max # of CC users Single Instance: n/a 10,000 SIP 250 Tenants

Table 4: Capacities for Avaya Collaboration Pod for Contact Center as a Service Release 1.0

Max # of UC users Max # of CC users Single Instance: Single Instance: 5,000 SIP (UC and CC combined) 2,500 SIP 125 Tenants 125 Tenants Note: UC for Back Office, Telephony only.

You can add resources such as G450 Media Gateways, Session Border Controllers and Avaya Aura® Messaging servers. Note: 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 Comments on this document? [email protected] 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 [email protected].

Release Component Service Pack Patch Included in Avaya Pod Orchestration Suite (POS) Pod Visualization Manager (PVM) 2.0.1 Avaya Configuration and Orchestration Manager (COM) (includes 3.0.2 Virtualization Provisioning Service (VPS) Release 1.0.3) Avaya IP Flow Manager (IPFM) 2.0.3 Avaya Visualization Performance and Fault Manager (VPFM) 3.0.3 Management Server Console (Windows 2008 R2) Release 2.0.1 • Pod Utility Module • vSphere Desktop Client • Unisphere Service Manager • WinSCP • SolarWinds TFTP Server • PuTTY • Notepad ++ • Firefox Note: Management Server console also provides a software and firmware repository. Avaya Identity Engines (IDE): 9.0.2 (optional) Avaya Aura® Utility Services 6.3 Secure Access Link 2.2 Avaya Diagnostic Server 2.0.0 (optional) Avaya Secure Remote Access 2.0.1 (optional) Avaya Aura® Communication Manager Simplex and Duplex 6.3.4 Table continues…

September 2015 Avaya Collaboration Pod Release Notes 27 Comments on this document? [email protected] Important notices

Release Component Service Pack Patch Avaya Aura® Session Manager 6.3.7 Avaya Aura® System Manager 6.3.7 Avaya WebLM 6.3.7

Avaya Aura® Presence Services 6.2.2 Application Enablement Services 6.3.1 Agile Communication Environment™ 6.2.2 Application Enablement Services 6.3.1 Avaya Control Manager Application Server (optional) 7.218c Avaya Call Management System(optional) 17.0.2 Avaya Aura® Experience Portal (optional) 7 Avaya Aura® Call Center Elite Multichannel (optional) 6.3.1 Avaya Aura® Conferencing (optional) 8.0 Avaya Aura® Messaging (optional) 6.3 (virtual appliance) Avaya Aura® Session Border Controller(optional) 6.3 (virtual appliance) Avaya Scopia® (optional) 8.3 • Scopia Management Server • Scopia Desktop Server (iView)

Avaya Hardware Components Release Component Service Pack Patch VSP 4850GTS switches 4.0.0 VSP 7024XLS switches 10.3.2 Avaya Aura® Session Border Controller 6.3 Media Gateway G450 6.3 Avaya Aura® Messaging (optional) 6.3 (hardware appliance)

Avaya Scopia® Elite 6000 MCU (optional) 8.3

28 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod for Unified Communications as a Service release list

Third Party Components Component Release Service Pack Patch EMC VNX 5300 5.32.000.5.216 EMC Core 6.3 VMware vSphere: EXSi Hypervisor, ESXi, Client Release 5.1 Update 2 and important security patches VMware vCenter Release 5.1 Update 2 and important security patches Oracle SQL Server (optional) SE1 11g

Avaya Collaboration Pod for Unified Communications as a Service release list The following table shows the hardware and software component release versions supported for Avaya Collaboration Pod for Unified Communications as a Service solutions. Quantities and specific details depend on the Bill of Materials (BOM) generated from the specific Collaboration Pod order. Avaya Collaboration Pod Software 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 [email protected].

September 2015 Avaya Collaboration Pod Release Notes 29 Comments on this document? [email protected] Important notices

Release Component Service Pack Patch Avaya IP Flow Manager (IPFM) 2.0.3 Avaya Visualization Performance and Fault Manager (VPFM) 3.0.3 Management Server Console (Windows 2008 R2) Release 2.0.1 • Pod Utility Module • vSphere Desktop Client • Unisphere Service Manager • WinSCP • SolarWinds TFTP Server • PuTTY • Notepad ++ • Firefox

Note: Management Server console also provides a software and firmware repository. Avaya Identity Engines (IDE): 9.0.2 (optional) Avaya Aura® Utility Services 6.3 Secure Access Link 2.2 Avaya Diagnostic Server 2.0.0 (optional) Avaya Secure Remote Access 2.0.1 (optional) Avaya Aura® Communication Manager Simplex and Duplex 6.3.4 Avaya Aura® Session Manager 6.3.7 Avaya Aura® System Manager 6.3.7 Avaya WebLM 6.3.7

Avaya Control Manager 7.218c Avaya Aura® Presence Services 6.2.2

Avaya hardware components The following table lists the Avaya hardware components in Collaboration Pod.

30 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod for Contact Center as a Service release list

Release Component Service Pack Patch VSP 4850GTS switches 4.0.0 VSP 7024XLS switches 10.3.2 Avaya Aura® Session Border Controller 6.3 Media Gateway G450 6.3 Avaya Aura® Messaging (optional) 6.3 (hardware appliance)

Third party components The following table lists the third-party components in Collaboration Pod.

Component Release Service Pack Patch EMC VNX 5300 5.32.000.5.216 EMC Core 6.3 VMware vSphere: EXSi Hypervisor, ESXi, Client Release 5.1 Update 2 and important security patches VMware vCenter Release 5.1 Update 2 and important security patches Oracle SQL Server (optional) SE1 11g

Avaya Collaboration Pod for Contact Center as a Service release list The following table shows the hardware and software component release versions supported for Avaya Collaboration Pod for Contact Center as a Service solutions. Quantities and specific details depend on the Bill of Materials (BOM) generated from the specific Collaboration Pod order. Avaya Collaboration Pod Software 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

September 2015 Avaya Collaboration Pod Release Notes 31 Comments on this document? [email protected] Important notices

authorization from the Avaya Collaboration Pod support team. For more information, contact [email protected].

32 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod for Contact Center as a Service release list

Table 5: Avaya software components for CCaaS Release 1.0.

The following table lists the Avaya software components for CCaaS Release 1.0 and supported releases for each product.

Release Component Service Pack Patch Avaya Control Manager Application Server 7.218c Application Enablement Services 6.3.1 Call Management System (optional) 17.0.2 Avaya Aura® Messaging (optional) 6.3 (virtual appliance) Avaya Aura® Experience Portal (optional) 7 Avaya Aura® Call Center Elite Multichannel (optional) 6.3.1 Avaya Aura® Workforce Optimization (optional) 12.0.1 • Avaya Call Recording (ACR)12.0.1 • Avaya Aura® Call Center Elite Multichanneldatabase (per instance) • Avaya Aura® Experience Portaldatabase • Avaya Contact Recorder Key Management Server (KMJ) ANAV (optional) 4.1 • Real Time Web Server • CTI Probe Server • Historical and VCA Web Server • ANAV database

Avaya hardware components The following table lists the Avaya hardware components in Collaboration Pod.

Third party components The following table lists the third-party components in Collaboration Pod.

September 2015 Avaya Collaboration Pod Release Notes 33 Comments on this document? [email protected] Important notices

Software and Virtual Appliances The following tables show a complete list of software and virtual appliances supported in Collaboration Pod Release 2.0.1. Note: The following table shows default and optional applications based on the reference design for each supported solution. The actual software deployed on each Collaboration Pod is determined by the customer requirements and final configuration. Legend: x: Default o: Optional —: Not Applicable Note: Management Server Console is a Windows Server 2008 R2 VM pre-installed by the manufacturer. The customer must purchase and license additional copies of Windows Server 2008 R2 VMs required to install all other Windows-based applications.

34 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Software and Virtual Appliances

Table 6: Infrastructure Applications

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 VPFM v3.0.3 Red Hat Pre-delivery x x x Enterprise Linux IPFM v2.0.3 Red Hat Pre-delivery x x x Enterprise Linux PVM v2.0.1 Red Hat Pre-delivery x x x Enterprise Linux COM v3.0.2 Red Hat Pre-delivery x x x Enterprise Linux VPS v1.0.3 Red Hat Pre-delivery x x x Enterprise Linux Identity Engines (IDE) - v9.0.2 Red Hat Post-delivery x x x Ignition Server Enterprise Linux VMware vCenter v5.1U2 SUSE Pre-delivery x x x Server vSphere ESXi v5.1 U2 SUSE Pre-delivery x x x Management Server v2.0.1 Windows Pre-delivery x x x Console Server 2008 R2 Secure Remote Access v2.0.1 CentOS Post-delivery o o o (SRA) Oracle Database VM v11g Windows/S Pre-delivery o o o QL 2008 R2 SP1 64

Table 7: Aura VE Applications (6.2 FP3)

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 Communication v6.3.4 Red Hat Pre-delivery x x x Manager (w/CCElite) Enterprise Linux Session Manager v6.3.7 Red Hat Pre-delivery x x x Enterprise Linux Table continues…

September 2015 Avaya Collaboration Pod Release Notes 35 Comments on this document? [email protected] Important notices

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 System Manager v6.3.7 Red Hat Pre-delivery x x x Enterprise Linux Utility Services v6.3 CentOS Post-delivery x x x Web LM v6.3 Red Hat Post-delivery x x x Enterprise Linux Avaya Aura v8.0 Red Hat Post-delivery o — — Conferencing (AAC) Enterprise Linux Avaya Aura Messaging v6.3 Red Hat Post-delivery o o o (AAM) Enterprise Linux Presence Services v6.2.2 Red Hat Post-delivery x x — Enterprise Linux Application Enablement v6.3.1 Red Hat Post-delivery x — x Services Enterprise Linux Agile Communication v6.2.2 Red Hat Post-delivery x — — Environment (ACE) Enterprise Linux Secure Access Link v2.2 CentOS Post-delivery x x x (SAL) Avaya Diagnostic v2.0 Red Hat Post-delivery o o o Server (ADS) Enterprise Linux

Table 8: CC Applications

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 Avaya Call v17.0.2 Red Hat Post-delivery o — o Management System Enterprise (CMS) Linux Avaya Aura Experience v7.0 Red Hat Post-delivery o — o Portal (EP) Enterprise Linux • Avaya Aura Experience Portal (EP) EPM Table continues…

36 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod software files

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 • Avaya Aura Experience Portal (EP) MPP Avaya Aura Experience — Windows/S Post-delivery — — o Portal (EP) Database QL 2008 R2 SP1 64 CC Elite MultiChannel v6.3.1 Windows Post-delivery — — o Server 2008 R2 CC Elite MultiChannel — Windows/S Post-delivery o — o Database (per QL 2008 instance) R2 SP1 64 Work Force v12 Windows Post-delivery o — o Optimization w/Contact Server Recorder (WFO/ACR) 2008 R2 Avaya Control Manager v7.0 Windows Post-delivery o x x (ACM) Server 2008 R2 Standard Edition Avaya Navigator v4.1 Windows Post-delivery — — o (ANAV) Server 2008 R2

Table 9: Additional Appliances

Product Product OS Deployment Ent 1.1 UCaaS CCaaS Version 1.2 1.0 Avaya SBC for v6.3 — Post-delivery o — — Enterprise (SBCE) VE Scopia® Solution v8.3 Windows Post-delivery o — — Server • Scopia® 2008 R2 Management Server • Scopia® Desktop Server (iView)

Avaya Collaboration Pod software files The following table lists the software files available for Avaya Collaboration Pod Release 2.0.1.

September 2015 Avaya Collaboration Pod Release Notes 37 Comments on this document? [email protected] Important notices

Table 10: Avaya Collaboration Pod Release 2.0.1 software files

Vendor Application or component File name VMware vSphere ESXi 5.1 Update 2 VMware-VMvisor- Installer-5.1.0.update02-1483097.x86_64 Patch files as specified: ESXi510-201402001.zip ESXi510-201404001.zip ESXi510-201406001.zip ESXi510-201407001.zip ESXi510-201410001.zip VMware vCenter Server Appliance 5.1 VMware-vCenter-Server- Appliance-5.1.0.20300-2212990_OVF10.ova Avaya Avaya Virtual Services Platform Files as specified: 7000 Series7024 XLS • 7000_10315_diags.bin • 7000_103211s • vsp7000v10.3.2.0 • vsp7000v1032_HELP_EDM Avaya Avaya Virtual Services Platform Files as specified: 4000 Series 4850 GTS • VSP4K.4.0.0.0 • VSP4K.4.0.0.0_modules • vsp4000v4.0.0.0 • vsp4000v400_HELP_EDM_gzip Avaya Session Border Controller Files as specified: Firmware (hardware) ipcs_6.3.0.Q19_de1b5896466ob7493147c1df5edc50 b8.tar ipcs_6.2.1.Q16_a07f5183b74baf0b6e8dae405068f8b b.tar Avaya Session Border Controller (Virtual EMS-sbce-6.3.0000–19–4338.ova Appliance) SBC-sbce-6.3.000–19–4338.ova Avaya Media Gateway G450 Firmware Files as specified: g450_sw_35_8_0.bin Avaya Management Server Console Management_Server_Console_2.0.1.0.11.ova EMC VNX 5300 Firmware CX5–Bundle-05.32.000.5.216.pbu EMC Unisphere Service Manager 20141016_150000UnisphereServiceManager_1.3.3.1 .0072_(7.33.3.0.72).exe EMC Unisphere Central Unisphere-Central-3.5.2.21982.ova Table continues…

38 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod software files

Vendor Application or component File name Oracle SQL Oracle 11g SE1 - Avaya_v2_0.ova Avaya Avaya Configuration and COMVPS-3.0.2.1–4.ova Orchestration Manager including Visualization Provisioning Service

Avaya Avaya IP Flow Manager Ipfm-2.0.3.1–3.ova Avaya Avaya Pod Visualization Manager Pvm-2.0.1–09.ova Avaya Avaya Visualization Performance Vpfm-3.0.3.2–1507.ova and Fault Manager Avaya Avaya Diagnostic Server AvayaDiagnosticServer-2.0.0.0–vApp-e50–07.ova ADS-ServicePack-2.0.1.0–129.tar.gz Avaya Secure Remote Access SRA-2.0.1.0–5050.ova Avaya Avaya Identity Engines Ignition AIEIS_RHEL_6_3_LINUX- Server VM_09_00_02_026940_x86_64.ova Avaya Avaya Identity Engines Access AccessPortal_01.00.00_022931_x86_32.mf Portal AccessPortal_01.00.00_022931_x86_32.ovf AccessPortal_01.00.00_022931_x86_32.vmdk Avaya Avaya Identity Engines DashboardInstaller-9.0.2.26940.exe Dashboard Avaya Avaya Identity Engines Guest GuestManagerInstaller-9.0.0.25816 Manager Avaya Avaya Aura® Conferencing vAAC_LargePlatform_MCP_18.0.21_2014-07-10-150 8-1vDisk150GB_12vCPU_30GBMemory.ova vAAC_MediumPrimary_MCP_18.0.21_2014-07-10-1 508-1vDisk150GB_8vCPU_24GBMemory.ova vAAC_MediumSecondary_MCP_18.0.21_2014-07-10 -1508-1vDisk150GB_8vCPU_24GBMemory.ova vAAC_MediumSimplex_MCP_18.0.21_2014-07-10-1 508-1vDisk150GB_8vCPU_24GBMemory.ova vAAC_SmallPlatform_MCP_18.0.21_2014-07-10-150 8-1vDisk150GB_6vCPU_16GBMemory.ova Avaya Avaya Agile Communication 6.2.2.30.31272-e51-00.ova Environment™ Avaya Application Enablement Services AES-6.3.1.0.19.20130912–e50–00.ova 631_SuperPatch1 Avaya Avaya Aura® Communication • CM-Simplex-06.03.0.124.0–e51.-1.ova Manager • CM-Duplex-06.03.0.124.0–e51–1.ova Table continues…

September 2015 Avaya Collaboration Pod Release Notes 39 Comments on this document? [email protected] Important notices

Vendor Application or component File name Files as specified: • 03.0.124.0-21678 • 03.0.124.0–21904 • KERNEL-2.6.18-348.AV5 • VMWT-2.6.18-348.AV5–5.5–002 • PLAT-rhel5.3–3014.tar Avaya Avaya Aura® Presence Services PS-6.2.0.0–182–VM-29.ova File as specified PS-6.2.3.0–317.zip Avaya Secure Access Link SALGateway-2.2.0.0-vApp-1.0.0.0-e50–09.ova SAL_service_Pack_2.2.1.0_SPPM-3 Avaya Avaya Aura® Session Manager SM-6.3.2.0.632023–e50–00–OVF10.ova File as specified Asm-6.3.7.0.637008-installer.iso Upgrade as specified asm-patch-shellshock.bin Avaya Avaya Aura® System Manager SMGR-6.3.0.8.5682–e50–64.ova File as specified System_Manager_6.3.7_Patch1_r3702403.bin System_Manager_6.3.7.0_r3702275.bin SystemManager_WebLM_Shellshock_Patch.bin Avaya Avaya Aura® Utility Services US-6.3.0.0.20–e51.01_OVF10.ova Service Pack 3 Util_patch_6.3.0.3.20 Avaya Web License Manager WebLM-6.3.2.4.6617–e50–4.16.ova File as specified WebLM_6.3.7_r3702195.bin Avaya Avaya Control Manager Version 7, build 218c Note: Filenames will vary for different configurations. See ACM documentation for more information. Avaya Avaya Call Management System CMS_R17a.k-e51–00.ova CMS_R17fb.m-e51.00.ova Table continues…

40 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Avaya Collaboration Pod software files

Vendor Application or component File name Files as specified: r17Lfb.m.iso r17fb.m_cmsp3–1.bin r17fa.k_cmsp1–1.bin Avaya Avaya Aura® Messaging AM6.03.0.124.0–315–e51–2.ova Files as specified: MSG-03.0.124.0–315_0006 Avaya Avaya Aura® Experience Portal ExperiencePortal_AuxiliaryEPM_7.0.0.0.6604–e51– 50.ova ExperiencePortal_MPP_7.0.0.0.6605–e51–50.ova ExperiencePortal_PrimaryEPM_7.0.0.0.6604–e51– 50.ova Files as specified: 7.0.0.0.6604_Linux adepInstaller-rhel6.4.64.13.10Oct13 External database files (MSSQL, Oracle, Postgres): InstallScripts UpgradeScripts TRANS.TBL Avaya Avaya Aura® Call Center Elite emc-6.3.0–e50.00.ova Multichannel Files as specified: CCM_6_3_0.iso CCM_6_3_1.iso tsapi_client_win32_6.3.1–502 EMC_6.3.1_Patch_1 Avaya Avaya Aura® Workforce WFO12.0.1 Optimization Patch 12–0–SP0–047

Note: Filenames will vary for different configurations. See WFO documentation for more information. Operating System OVA templates for WFO: WFO Windows 2008 R2 64 bit.ova (Windows) WFO RHEL 6 Update 3 64 bit.ova (Linux) Avaya Avaya Call Recorder Avaya_DVD10_Recorder_12.0build1_Linux Table continues…

September 2015 Avaya Collaboration Pod Release Notes 41 Comments on this document? [email protected] Important notices

Vendor Application or component File name Avaya_DVD10_Recorder_12.0build1_Windows Files are specified: acr120061 Avaya ANAV ANAV 4.1 • Real Time Web Server Note: • CTI Probe Server Filenames will vary for different configurations. • Historical and VCA Web Server See ANAV documentation for more information.

Note: To support the full Duplex configuration for Avaya Aura® Communication Manager you must enable VMware® High Availability (HA) and Distributed Resource Scheduling (DRS). Use VMware® HA and DRS and configure Communication Manager (CM) and Session Manager (SM) VLANs for maximum reliability.

Supported browsers Avaya Collaboration Pods supported the following browsers: • Internet Explorer 8.x, 9.x, 10.x • Mozilla Firefox 19.x, 20.x, 21.x

VMware Snapshot considerations VMware Snapshot preserves the state and data of a virtual machine at a specific point in time. Snapshot is useful as a short-term fallback for patching and upgrading the system. However, 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.

42 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] VMware considerations

Caution: Snapshot operations adversely affects application and system performance. Do not keep snapshots for extended operation. 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.

VMware considerations VMware tools reported as “out-of-date.” This is not an issue. The current version of VMware tools is designed to work with the Collaboration Pod components. Important: Do not update the VMware tools software that is packaged with the Collaboration Pods unless instructed to do so by Avaya. The supplied version of VMware is the supported release and has been thoroughly tested.

September 2015 Avaya Collaboration Pod Release Notes 43 Comments on this document? [email protected] Chapter 5: Known issues and limitations

Use the information in this section to learn more about known issues and limitations of Avaya Collaboration Pod for Enterprise Communications. Note: See the individual product documentation for Avaya Aura® Virtualized Environment and individual component Release Notes for details and issues specific to these products.

AES issues The following table lists the AES known issues and limitations:

WI reference Description Avaya Aura® Application Enablement Services (AES) for the virtualized environment does not support DHCP. Workaround — perform the following procedure:

If DHCP is enabled, AES will not start. To deploy AES you must disable DHCP. To determine whether DHCP is enabled, do the following:

1. From the console, log in to AES with the appropriate authorization credentials. Note: You can use su -sroot or su -root. 2. Open the file named /etc/hosts via vi editor 3. Remove the DHCP IP entry if it exits in /etc/hosts file. Note: To determine which is the DHCP IP, view the following files a. cat /etc/sysconfig/network-scripts/ifcfg-eth0 b. cat /etc/sysconfig/network-scripts/ifcfg-eth1 4. Save the /etc/hosts file 5. If both the eth0 and eth 1 files display DHCP enabled, do the following: a. Navigate to the AES Management Console to Networking > Network Configure

44 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] COM issues

WI reference Description b. Configure static ip address on eth0 - physical IP address and network mask. Note: eth1 doesn’t require an IP address unless you are multiple CM duplex. 6. From the terminal prompt, enter the service aesvce restart command.

COM issues The following table lists the COM known issues and limitations:

WI reference Description wi01080509 After executing HA-DRS, the Virtualization Provisioning Service (VPS) does not discover links after it is powered ON. This happens about 50% of the time. WORKAROUND: Run the Hypervisor Connectivity again until links are discovered. wi01197815 Unable to launch CLI manager for COM deployed as an OVA. When you click on Launch CLI Manager link, the browser attempts to load to a test URL with FQDN changed, which causes failure to launch the manager. WORKAROUND: Manually enter the correct URL using the following format: https://yourFQDN/climanager/index.jsp". . For example, if the FQDN of your machine is test.apac.avaya.com; enter the following URL to launch the CLI manager: https://test.apac.avaya.com/climanager/index.jsp wi01197784 Using COM, the CAT tool shows an invalid error of ‘device credentials not present’ when trying to audit the VSP 4000 or VSP 7000 devices. The error expected is ‘Device unsupported’.

IPFM issues The following table lists the IPFM known issues and limitations:

WI reference Description wi01082454 After the IPFM server is down the pop-up banner does not display a proper description. wi01168238 The IPFM Collector queries the database for any existing device when it starts up. If it fails to contact a device, the collector startup does not continue. Workaround: 1. Remove any devices that IPFM collector can’t reach from IPFM web interface (Dashboard -> Devices). Table continues…

September 2015 Avaya Collaboration Pod Release Notes 45 Comments on this document? [email protected] Known issues and limitations

WI reference Description 2. Restart IPFM collector task

Note: For Linux issue command: service ipfix_collector restart Windows: restart “Avaya UCM IPFIX Collector” from task manager.

SAL issues The following table lists the SAL known issues and limitations:

WI reference Description wi01075101 The Collaboration Pod does not support SAL remote connectivity to manage and troubleshoot vCenter and vSphere. WORKAROUND: Use a customer PC to connect to vCenter and establish a Web conference with Avaya support staff to control.

SMGR issues The following table lists the SMGR known issues and limitations:

WI reference Description wi01045405 SMGR causes the browser to get a redirecting page error after switching between user types. WORKAROUND: If you get redirected or cannot access credentials and licensing administration from COM launch points, clear the browser’s cache.

POS Issues The following table lists the Pod Orchestration Suite (POS) known issues and limitations:

WI reference Description wi01083702 The UCM Application Description is not correctly updated to match the Build Version of the POS management applications. This discrepancy is found for VPFM, IPFM, and PVM. UCM should be able to display all current versions

46 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] VPFM issues

VPFM issues The following table lists the VPFM known issues and limitations:

WI reference Description wi01082470 The initial start of ipfix_collector fails after VPFM jboss service is disabled. During the HA-DRS migration, VPFM jboss service is not fully operational after IPFM ipfix_collector starts. IPFM's reliance on VPFM must be taken into consideration after failover scenarios. You need to investigate and determine the best mechanism for handling this reliance. WORKAROUND: restart ipfix_collector with VPFM fully running. wi0112985 SSH timeout needs to be increased to discover file systems and logical volumes for AAM wi01152352 SPB multicast and unicast paths are cleared following a refresh

PVM Issues The following table lists the PVM known issues and limitations:

WI Reference Description wi01125192 Launching PVM for an Extension Pod Note: The master or extension PVM always open in a new browser tab. After the PVM application is opened from System Manager, PVM does not have control or information about the previously opened PVM tab. wi01158051 An issue with the upgrade available to JAVA ™ Platform SE 7 U51 10.51, prevents the Gateway 450 Device manager from launching. WORKAROUND: Add site (http:) to the Exception Site List in the Java control panel security settings. wi01152431 Launching SBC element manager ACME SBC element manager cannot launch from the PVM navigation tree if the user is launching on EI 8. WORKAROUND: use IE9+ or Firefox to avoid issue wi01203953 If you upgrade PVM R2.0 to PVM R2.0.1, the System Manager (UCM) Application information for PVM does not show the R2.0.1 information. In UCM, the PVM application type displays the previous R2.0 application information.

September 2015 Avaya Collaboration Pod Release Notes 47 Comments on this document? [email protected] Known issues and limitations

PUM Issues The following table list the PUM known issues: WI Reference Description wi01170858 RDP connection loss during upgrade of the Management server console WORKAROUND: Connection via vSphere console is still active therefore all VMs should successfully migrate regardless of their state. wi01175254 After deployment of WFO Windows base OS all disk volumes on virtual appliance names are set to "New Volume". WORKAROUND: The disk volumes on virtual appliance names need to be changed by an Avaya professional when the WFO applications are deployed and configured on the base OS virtual appliance. wi01175253 If only few Windows base OS virtual appliance are deployed, Pod Utility Module (PUM) still creates deployment files for other virtual appliances. This leads to high utilization of disk space and also slows down the process due to time taken in creation of these extra templates. WORKAROUND: Use the procedure mentioned in the document Using the Management Server Console for Avaya Collaboration Pod (NN47204–303) for WFO base OS virtual appliance deployment to perform deployment for selected WFO platforms. wi01175255 No user roles or different permissions for WFO Windows base platform templates. WORKAROUND: Only an Avaya administrator is able to change permissions. wi01175257 Cannot use “sysprep” to generalize the OS for WFO Windows base platform template. WORKAROUND: There are no plans to use “sysprep” to generalize the OS for the WFO Windows base platform template. Use the existing process. wi01175309 WFO deployment and disk creation fails due to base VMDK not having an updated script for DNS configuration. wi01201560 PUM does not display more than 100 Virtual Machines correctly. If you have more than 100 VMs, a few hosts display empty. JIRA CPOD-218 Use of PUM to upgrade POS from R2.0 to R2.0.1 does not keep the COM/VPS configuration. WORKAROUND: Backup VPS configuration, perform the POS upgrades using PUM, restore VPS configuration. For more information, see Using the Management Server Console for Avaya Collaboration Pod (NN47204–303).

SBC Issues The following table lists the SBC known issues:

48 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Switch issues

WI Reference Description wi01175619 The SBC factory reset feature does not clear all settings to their original state. The intact settings are causing deployment issues and delays for system administrators.

Switch issues The following table lists the network and aggregation switches known issues and limitations:

WI reference Description wi01176543 The VSP 4850GTS switch configured as the VRRP backup master router does not respond to ping requests to the VRRP IP address. Due to an issue with VSP 4000 Series Release 3.1, any application or device directly connected to the VRRP backup master that requires ICMP ping response reports a loss of connectivity. WORKAROUND: Disable VRRP Backup-Master mode on both VSP 4850GTS switches.

Note: With VRRP Backup-Master mode disabled, the VSP 4850GTS switches can operate as a redundant pair of VRRP routers. The Master VRRP router can route and respond to all traffic sent to the VRRP IP address.

EMC storage issues The following table lists the EMC storage known issues and limitations:

WI reference Description wi01220750 Primary to Standby Storage Processor (SP) in the Disk Processor Enclosure (DPE) can take up to 60 seconds to switch during an EMC failover scenario. The compute servers and Virtual Machines cannot access the EMC storage array during the failover delay. You must wait for the Standby SP to provide service. JIRA CPOD-220 If a complete iSCSI storage internal network failure occurs, operating VMs might experience network and storage connectivity issues once the iSCSI storage network is restored. WORKAROUND: Once the iSCSI storage network is restored, you can reboot the VMs to resolve connectivity issues.

September 2015 Avaya Collaboration Pod Release Notes 49 Comments on this document? [email protected] Known issues and limitations vCenter database issues The following table lists the database known issues: WI Reference Description wi01182779 A failure or ungraceful shutdown of the compute server that hosts the SQL database for vCenter might cause a database issue which prohibits the vCenter appliance from starting. If vCenter cannot be reached 15 minutes after a host migration, the vCenter appliance might have issues starting vCenter services with the error message vpxd failed to start. WORKAROUND: Contact Avaya support or [email protected] for advanced troubleshooting and repair.

50 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Chapter 6: Resolved Issues

Resolved Issues Use the information in this section to learn more about resolved issues and limitations.

PVM issues The following table lists the PVM issues from Release 1.0 that are now resolved:

WI reference Description wi01062853 The PVM Profile> Device Description field does not allow for the addition of an unsupported device such as an ERS 5600 or ERS 8600. wi01063184 The PVM copy and paste functions are not efficient within the Switchs> Summary> Interface tab. This tab must also support exporting to Excel or Word. wi01064706 The PVM Preferences tab does not allow you to modify URLs. wi01065038 The PVM Preferences tab must provide a template where a user can enter the URL of a server. This feature is useful because PVM cannot automatically detect the servers with the corresponding applications installed (i.e. IP Flow, VPFM, VPS). wi01065046 The PVM physical view does not show an enlarged view of the servers. You have to print the physical view to see the hidden objects. wi01065084 The POD navigation search function finds elements, but it does not display any details for the elements. wi01065829 The PVM Profile> Device Description field allows you to do a bulk add of multiple devices, but the state says they are UNREACHABLE. WORKAROUND: Refresh or rediscover to display the correct state. wi01065836 PVM clients do not communicate with each other until you rediscover. For example, if you make changes in one client such as adding or deleting a device, the change does not display in the second client. WORKAROUND: Rediscover the client to display the latest changes. wi01066182 The PVM> POD physical view looks distorted after the browser window is minimized. The view should be re-sized. Table continues…

September 2015 Avaya Collaboration Pod Release Notes 51 Comments on this document? [email protected] Resolved Issues

WI reference Description wi01066184 The PVM> POD physical view shows too many details. Just display the type of device and version such as Virtual Service Platform 7024XLS. wi01066185 The PVM> Service Profile Editor must not display sorting and the Slot OID, Device OID, and Log OID columns. wi01076641 Self Signed Certificate (SSL) does not install on IE. After launching Pod Visualization Manager and attempting to install a Self Signed Certificate in the IE 8 browser, the certificate is installed for that session only, and requires reinstallation for every subsequent session. WORKAROUND: Use the latest Firefox web browser. wi01078350 Switching between VSP switches A and B produces an error message. wi01087188 Adding KVM as a first device to Profile fails. Adding KVM as a first device to the Profile results in the error message. WORKAROUND: add SNMP devices first, then KVM, or add SNMP devices and KVM at the same time. wi01083089 With software version 5.6.2 for the ERS 4826, the information for the chassis is missing. WORKAROUND: Launch EDM (from the same folder, or physical view, or from the extended view) to see the data.

PUM Issues The following table list the PUM issues from Release 2.0 that are now resolved: WI Reference Description wi01175252 Floppy drive is present as one of the drives after the base templates for the WFO base OS virtual appliances are deployed. It is not used for any purpose.

52 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected] Appendix A: Related resources

Documentation reference Following is a high-level list of links to Avaya and third-party documentation for the components contained within Collaboration Pod. • Avaya: www.avaya.com/support . On this site you can find documentation and downloads for networking, management, and applications for the Collaboration Pod • VMware: www.vmware.com • Compute servers: - HP ProLiant DL360p and DL360e Generation 8 servers, see www.hp.com. - Lenovo ThinkServer RD540 and RD340, see www.lenovo.com. • EMC² VNX storage array: www.emc.com • ServerTech Power Distribution Units: www.servertech.com For a detailed reference of documentation for Collaboration Pod and specific components, see: • Avaya Collaboration Pod Documentation Reference (NN47204–113)

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.

September 2015 Avaya Collaboration Pod Release Notes 53 Comments on this document? [email protected] Related resources

• 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. 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 key word 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.

54 Avaya Collaboration Pod Release Notes September 2015 Comments on this document? [email protected]