Migrating Avaya Aura® Conferencing 8

Migrating Avaya Aura® Conferencing

Release 8.004-604403

Issue 1August 2014

© 2014 Avaya Inc.

All Rights Reserved.

NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accurate at the time ofprinting, Avaya assumes no liability for any errors. Avaya reservesthe right to make changes and corrections to the information in thisdocument without the obligation to notify any person or organizationof such changes.

Documentation disclaimer“Documentation” means information published by Avaya in varyingmediums which may include product information, operatinginstructions and performance specifications that Avaya may generallymake available to users of its products and Hosted Services.Documentation does not include marketing materials. Avaya shall notbe responsible for any modifications, additions, or deletions to theoriginal published version of documentation unless suchmodifications, additions, or deletions were performed by Avaya. EndUser agrees to indemnify and hold harmless Avaya, Avaya's agents,servants and employees against all claims, lawsuits, demands andjudgments arising out of, or in connection with, subsequentmodifications, additions or deletions to this documentation, to theextent made by End User.

Link disclaimerAvaya is not responsible for the contents or reliability of any linkedwebsites referenced within this site or documentation provided byAvaya. Avaya is not responsible for the accuracy of any information,statement or content provided on these sites and does notnecessarily endorse the products, services, or information describedor offered within them. Avaya does not guarantee that these links willwork all the time and has no control over the availability of the linkedpages.

WarrantyAvaya provides a limited warranty on Avaya hardware and software.Refer to your sales agreement to establish the terms of the limitedwarranty. In addition, Avaya’s standard warranty language, as well asinformation regarding support for this product while under warranty isavailable to Avaya customers and other parties through the AvayaSupport website: http://support.avaya.com or such successor site asdesignated by Avaya. Please note that if you acquired the product(s)from an authorized Avaya Channel Partner outside of the UnitedStates and Canada, the warranty is provided to you by said AvayaChannel Partner and not by Avaya.

“Hosted Service” means a hosted service subscription that youacquire from either Avaya or an authorized Avaya Channel Partner(as applicable) and which is described further in Hosted SAS or otherservice description documentation regarding the applicable hostedservice. If you purchase a Hosted Service subscription, the foregoinglimited warranty may not apply but you may be entitled to supportservices in connection with the Hosted Service as described furtherin your service description documents for the applicable HostedService. Contact Avaya or Avaya Channel Partner (as applicable) formore information.

Hosted ServiceTHE FOLLOWING APPLIES IF YOU PURCHASE A HOSTEDSERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYACHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USEFOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO UNDERTHE LINK “Avaya Terms of Use for Hosted Services” OR SUCHSUCCESSOR SITE AS DESIGNATED BY AVAYA, AND AREAPPLICABLE TO ANYONE WHO ACCESSES OR USES THEHOSTED SERVICE. BY ACCESSING OR USING THE HOSTEDSERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ONBEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU AREDOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLYAS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IFYOU ARE ACCEPTING THE TERMS OF USE ON BEHALF ACOMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THATYOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESETERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, ORIF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU

MUST NOT ACCESS OR USE THE HOSTED SERVICE ORAUTHORIZE ANYONE TO ACCESS OR USE THE HOSTEDSERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BELIMITED BY THE NUMBER AND TYPE OF LICENSESPURCHASED UNDER YOUR CONTRACT FOR THE HOSTEDSERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTEDSERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITYTO USE FLEX LICENSES, WHICH WILL BE INVOICEDACCORDING TO ACTUAL USAGE ABOVE THE CONTRACTLICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNELPARTNER FOR MORE INFORMATION ABOUT THE LICENSESFOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITYOF ANY FLEX LICENSES (IF APPLICABLE), PRICING ANDBILLING INFORMATION, AND OTHER IMPORTANTINFORMATION REGARDING THE HOSTED SERVICE.

LicensesTHE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYAWEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO ORSUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AREAPPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/ORINSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (ASAPPLICABLE) UNDER A COMMERCIAL AGREEMENT WITHAVAYA OR AN AVAYA CHANNEL PARTNER. UNLESSOTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOESNOT EXTEND THIS LICENSE IF THE SOFTWARE WASOBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYAAFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYARESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOUAND ANYONE ELSE USING OR SELLING THE SOFTWAREWITHOUT A LICENSE. BY INSTALLING, DOWNLOADING ORUSING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOMYOU ARE INSTALLING, DOWNLOADING OR USING THESOFTWARE (HEREINAFTER REFERRED TOINTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TOTHESE TERMS AND CONDITIONS AND CREATE A BINDINGCONTRACT BETWEEN YOU AND AVAYA INC. OR THEAPPLICABLE AVAYA AFFILIATE (“AVAYA”).

Avaya grants you a license within the scope of the license typesdescribed below, with the exception of Heritage Nortel Software, forwhich the scope of the license is detailed below. Where the orderdocumentation does not expressly identify a license type, theapplicable license will be a Designated System License. Theapplicable number of licenses and units of capacity for which thelicense is granted will be one (1), unless a different number oflicenses or units of capacity is specified in the documentation or othermaterials available to you. “Software” means Avaya’s computerprograms in object code, provided by Avaya or an Avaya ChannelPartner, whether as stand-alone products, pre-installed , or remotelyaccessed on hardware products, and any upgrades, updates, bugfixes, or modified versions thereto. “Designated Processor” means asingle stand-alone computing device. “Server” means a DesignatedProcessor that hosts a software application to be accessed bymultiple users. “Instance” means a single copy of the Softwareexecuting at a particular time: (i) on one physical machine; or (ii) onone deployed software virtual machine (“VM”) or similar deployment.

License typesDesignated System(s) License (DS). End User may install and useeach copy or an Instance of the Software only on a number ofDesignated Processors up to the number indicated in the order.Avaya may require the Designated Processor(s) to be identified inthe order by type, serial number, feature key, Instance, location orother specific designation, or to be provided by End User to Avayathrough electronic means established by Avaya specifically for thispurpose.

Named User License (NU). You may: (i) install and use the Softwareon a single Designated Processor or Server per authorized NamedUser (defined below); or (ii) install and use the Software on a Serverso long as only authorized Named Users access and use theSoftware. “Named User”, means a user or device that has beenexpressly authorized by Avaya to access and use the Software. AtAvaya’s sole discretion, a “Named User” may be, without limitation,designated by name, corporate function (e.g., webmaster orhelpdesk), an e-mail or voice mail account in the name of a person or

http://support.avaya.com/

http://support.avaya.com/LicenseInfo

http://support.avaya.com/LicenseInfo

corporate function, or a directory entry in the administrative databaseutilized by the Software that permits one user to interface with theSoftware.

CopyrightExcept where expressly stated otherwise, no use should be made ofmaterials on this site, the Documentation, Software, Hosted Service,or hardware provided by Avaya. All content on this site, thedocumentation, Hosted Service, and the Product provided by Avayaincluding the selection, arrangement and design of the content isowned either by Avaya or its licensors and is protected by copyrightand other intellectual property laws including the sui generis rightsrelating to the protection of databases. You may not modify, copy,reproduce, republish, upload, post, transmit or distribute in any wayany content, in whole or in part, including any code and softwareunless expressly authorized by Avaya. Unauthorized reproduction,transmission, dissemination, storage, and or use without the expresswritten consent of Avaya can be a criminal, as well as a civil offenseunder the applicable law.

VirtualizationEach product has its own ordering code and license types. Note thateach Instance of a product must be separately licensed and ordered.For example, if the end user customer or Avaya Channel Partnerwould like to install two Instances of the same type of products, thentwo products of that type must be ordered.

Third Party Components“Third Party Components” mean certain software programs orportions thereof included in the Software or Hosted Service maycontain software (including open source software) distributed underthird party agreements (“Third Party Components”), which containterms regarding the rights to use certain portions of the Software(“Third Party Terms”). As required, information regarding distributedLinux OS source code (for those Products that have distributed LinuxOS source code) and identifying the copyright holders of the ThirdParty Components and the Third Party Terms that apply is availablein the Documentation or on Avaya’s website at: http://support.avaya.com/Copyright or such successor site as designatedby Avaya. You agree to the Third Party Terms for any such ThirdParty Components

THIS PRODUCT IS LICENSED UNDER THE AVC PATENTPORTFOLIO LICENSE FOR THE PERSONAL USE OF ACONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVEREMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITHTHE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVCVIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN APERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEOPROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE ISGRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEGLA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.

Note to Service ProviderThe Product or Hosted Service may use Third Party Componentssubject to Third Party Terms that do not allow hosting and require aService Provider to be independently licensed for such purpose. It isyour responsibility to obtain such licensing.

Preventing Toll Fraud“Toll Fraud” is the unauthorized use of your telecommunicationssystem by an unauthorized party (for example, a person who is not acorporate employee, agent, subcontractor, or is not working on yourcompany's behalf). Be aware that there can be a risk of Toll Fraudassociated with your system and that, if Toll Fraud occurs, it canresult in substantial additional charges for your telecommunicationsservices.

Avaya Toll Fraud interventionIf you suspect that you are being victimized by Toll Fraud and youneed technical assistance or support, call Technical Service CenterToll Fraud Intervention Hotline at +1-800-643-2353 for the UnitedStates and Canada. For additional support telephone numbers, seethe Avaya Support website: http://support.avaya.com or suchsuccessor site as designated by Avaya. Suspected securityvulnerabilities with Avaya products should be reported to Avaya bysending mail to: [email protected].

TrademarksThe trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation, Hosted Service(s), and Product(s) providedby Avaya are the registered or unregistered Marks of Avaya, itsaffiliates, or other third parties. Users are not permitted to use suchMarks without prior written consent from Avaya or such third partywhich may own the Mark. Nothing contained in this site, theDocumentation, Hosted Service(s) and Product(s) should beconstrued as granting, by implication, estoppel, or otherwise, anylicense or right in and to the Marks without the express writtenpermission 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. andother countries.

Downloading DocumentationFor the most current versions of Documentation, see the AvayaSupport website: http://support.avaya.com, or such successor site asdesignated by Avaya.

Contact Avaya SupportSee the Avaya Support website: http://support.avaya.com for Productor Hosted Service notices and articles, or to report a problem withyour Avaya Product or Hosted Service. For a list of support telephonenumbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated byAvaya), scroll to the bottom of the page, and select Contact AvayaSupport.

http://support.avaya.com/Copyright

http://support.avaya.com/Copyright

HTTP://WWW.MPEGLA.COM

http://support.avaya.com




Contents

Chapter 1: An Introduction to Avaya Aura® Conferencing................................................... 8About this document................................................................................................................ 8Related resources................................................................................................................... 8

Documentation.................................................................................................................. 8Training.......................................................................................................................... 11Viewing Avaya Mentor videos........................................................................................... 11Deploying online help...................................................................................................... 12

Support................................................................................................................................ 14Audience.............................................................................................................................. 14How to use this document...................................................................................................... 15

Preparing your data using the Avaya Aura® Conferencing 8.0 Intelligent Workbook.............. 15Administrative user roles and preconfigured accounts.............................................................. 16Supported Web browsers....................................................................................................... 18Supported hardware.............................................................................................................. 19

Chapter 2: Migrating servers................................................................................................. 21Server replacement............................................................................................................... 21Prerequisites for server replacement....................................................................................... 21Server replacement for simplex deployments........................................................................... 22

Element Manager server replacement for simplex deployments.......................................... 22Non-Element Manager server replacement for simplex deployments................................... 24

Server replacement for redundant deployments....................................................................... 26Primary Element Manager server replacement for redundant deployments.......................... 26Non-primary Element Manager server replacement for redundant deployments.................... 28

Determining which components are hosted on the server ........................................................ 30Backing up Avaya Aura® Conferencing for server replacement.................................................. 35

Backing up the Flash Media Gateway(s) for a feature pack................................................. 36Backing up the Avaya Media Server (MS)......................................................................... 36Backing up conference recordings.................................................................................... 37Backing up the database for a feature pack, a service pack, or a patch................................ 39Backing up the Avaya Aura® Conferencing servers............................................................ 40

Stopping a network element instance...................................................................................... 43Stopping an Element Manager instance.................................................................................. 44Restoring the platform following server replacement................................................................. 44

Restoring the platform from a remote backup server.......................................................... 45Restoring the platform from a USB drive........................................................................... 47Installing the AAC Platform............................................................................................... 49

Restoring an Avaya Aura® Conferencing server following server replacement............................ 59Restoring an Avaya Aura® Conferencing server................................................................. 60

Extracting the application bundle contents............................................................................... 61Installing the database software.............................................................................................. 62

4 Migrating Avaya Aura® Conferencing August 2014Comments? [email protected]

mailto:[email protected]?subject=Migrating Avaya Aura® Conferencing

Installing the database........................................................................................................... 63Restoring the database following server replacement............................................................... 63Installing Element Manager.................................................................................................... 64Installing Avaya Media Server................................................................................................ 64Restoring a network element instance during server replacement.............................................. 65Restoring the recordings following server replacement............................................................. 67Installing WebLM................................................................................................................... 67Verifying the system.............................................................................................................. 68Restoring a Flash Media Gateway (FMG)................................................................................ 68Re-syncing the database data from the secondary instance...................................................... 70

Verifying that the secondary database is running and has no replication errors..................... 71Setting up the database replication......................................................................................... 71

Chapter 3: Migrating from a bare metal solution to a virtualized solution........................ 73Introduction........................................................................................................................... 73Prerequisites......................................................................................................................... 73Migrating from bare metal to VM for a medium simplex deployment........................................... 74

Backing up the database.................................................................................................. 79Backing up the Flash Media Gateway(s)........................................................................... 80Manually installing the VMware tools package................................................................... 80Killing a network element instance.................................................................................... 81Deploying a network element instance.............................................................................. 82Starting a Network Element instance................................................................................. 83

Migrating from bare metal to VM for a medium redundant deployment....................................... 83Setting the database type to single................................................................................... 90Setting the database type to replicated.............................................................................. 91Setting up the database replication................................................................................... 91

Chapter 4: Migrating from a turnkey solution to an Aura® solution.................................. 93Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the fullAvaya Aura® platform............................................................................................................. 93

Adding Avaya Aura® System Manager to the Element Manager GUI................................... 96Adding Avaya Aura® Session Manager to the Element Manager GUI................................... 97Changing the WebLM location to use Avaya Aura® System Manager .................................. 98Configuring Session Manager as the bandwidth management ASM for the applicationserver............................................................................................................................. 98Configuring the access control list (ACL)........................................................................... 99Guidelines for certificate configuration............................................................................. 114Obtaining enrollment password from System Manager..................................................... 116Creating Network Element certificates signed by System Manager.................................... 116Assigning a new certificate to the Element Manager......................................................... 118Assigning a new certificate to the Provisioning Manager................................................... 119Assigning a new certificate to the Collaboration Agent Manager........................................ 120Assigning a new certificate to the Application Server........................................................ 121Assigning a new certificate to the Avaya Media Server..................................................... 122

Contents

August 2014 Migrating Avaya Aura® Conferencing 5Comments? [email protected]


Assigning a new certificate to the Web Conferencing Server............................................. 123Assigning a new certificate to the Web Conferencing Management Server......................... 124Assigning a new certificate to the DCS............................................................................ 125Starting an Element Manager instance from the server console........................................ 125Configuring single sign-on for Element Manager Console and Provisioning Client.............. 126Configuring the route to Avaya Aura® Conferencing on System Manager........................... 130Creating a System Manager- signed certificate for the Flash Media Gateway IP address.... 133Configuring a secure SIP TLS connection from the Flash Media Gateway to Avaya Aura®

Session Manager.......................................................................................................... 134Changing the system default settings to use Avaya Aura® Conferencing (AAC).................. 135Removing the dialing rules in Provisioning Client............................................................. 135Removing all SIP entities for PBXs in Element Manager................................................... 136Removing all the old certificates on Turnkey.................................................................... 136

Chapter 5: Migrating from a DMZ solution to an enterprise solution.............................. 138Migrating Avaya Aura® Conferencing components from the DMZ to the Enterprise................... 138Migrating the Collaboration Agent Manager from the DMZ ..................................................... 140Migrating the Web Conferencing Server from the DMZ........................................................... 142

Chapter 6: Migrating from an enterprise solution to a DMZ solution.............................. 145Migrating from an enterprise solution to a DMZ solution.......................................................... 145Adding a new DMZ server in the Element Manager GUI......................................................... 146Migrating the Collaboration Agent Manager to the DMZ ......................................................... 147Migrating the Web Conferencing Server to the DMZ .............................................................. 149

Chapter 7: Migrating the Web Conferencing Management Server (WCMS) to theenterprise............................................................................................................................... 151

Updating the Web Conferencing Management Server (WCMS) Rsync configuration................. 154Undeploying a network element instance............................................................................... 154Deploying a network element instance.................................................................................. 155Configuring the meeting event processor for the Web conferencing management server.......... 156Starting a network element instance..................................................................................... 156Cleaning up the library files.................................................................................................. 157

Chapter 8: Adding redundancy to your solution............................................................... 158Expanding from a medium non-redundant deployment to a medium redundant deployment...... 158

Reference configurations for medium enterprises............................................................. 158Checklist for expanding an SMB or medium non-redundant deployment to a redundantdeployment................................................................................................................... 160Adding secondary Element Manager server and secondary media and Web conferencingserver hosts.................................................................................................................. 162Adding secondary Element Manager server hosts ........................................................... 163Installing and configuring a secondary database instance................................................. 164

Expanding from a large non-redundant deployment to a large redundant deployment............... 165Reference configurations for large enterprises................................................................. 165Checklist for expanding a large non-redundant deployment to a redundant deployment...... 167

Chapter 9: Upsizing your solution...................................................................................... 171

Contents



Expanding from a medium to a large deployment (without redundancy)................................... 171Checklist for expanding a medium simplex deployment to a large simplex deployment....... 173Adding media and Web conferencing servers.................................................................. 174Adding media and Web conferencing server hosts........................................................... 174Changing engineering parameters for a network element instance.................................... 175Changing engineering parameters in the database........................................................... 176Moving an Avaya Media Server (MS) network element to a new server............................. 177Moving a Web conferencing Server network element to a new server................................ 178

Expanding from a medium to a large deployment (with redundancy)........................................ 179Checklist for expanding a medium redundant deployment to a large redundant deployment.................................................................................................................................... 181

Appendix A: Overview of automatic disaster recovery..................................................... 183Implications of virtualization for automatic disaster recovery.................................................... 185System service state............................................................................................................ 186

Appendix B: Fixing remote host SSH keys........................................................................ 187

Contents



Chapter 1: An Introduction to Avaya Aura®Conferencing

About this documentThis document describes the procedures required to change the configuration of your Avaya Aura®

Conferencing 8.0 deployment. It describes the most common types of migration requests, such asmoving your deployment to or from a Demilitarized Zone (DMZ)1 or switching your deployment froma bare metal solution2 to a virtualized solution3.

Related resources

DocumentationDownload the following related documents at http://support.avaya.com.

The Avaya Support website also includes the latest information about product compatibility, portsand Avaya Aura® Conferencing releases.

Related LinksOverview on page 9Implementation on page 9Administration on page 10Supporting on page 10

1 DMZ or Demilitarized Zone is a physical or logical subnetwork that contains and exposes an organization's external-facing services to a larger and untrusted network, usually the Internet.

2 A bare metal solution is a computer system or network in which a virtual machine is installed directly on hardware ratherthan within the host operating system (OS).

3 A virtualized solution refers to the process of masking server resources with the aim of centralizing administrative tasks.




Overview

Documentnumber

Title Use this document to: Audience

04-604343 Avaya Aura® ConferencingOverview and Specification forAvaya Aura®

Understand the high-level featuresand functionality of the product

Customers,Partners,Services, andSupportpersonnel

04-604344 Avaya Aura® ConferencingOverview and Specification forTurnkey

Understand the high-level featuresand functionality of the product


04-604323 Avaya Aura® ConferencingSolution Description for SME

Understand the high-level featuresand functionality of the solution


04-604328 Avaya Aura® ConferencingSolution Description forMedium Enterprises



04-604333 Avaya Aura® ConferencingSolution Description for LargeEnterprises



Related LinksDocumentation on page 8

Implementation

Documentnumber


04-604418 Deploying Avaya Aura®

Conferencing: BasicInstallation

Perform installation and configurationtasks

Partners,Services, andSupportpersonnel

04-604363 Deploying Avaya Aura®

Conferencing: AdvancedInstallation and Configuration

Perform installation and configurationtasks


Related resources



Documentnumber


04-604353 Upgrading Avaya Aura®

ConferencingPerform upgrading and configurationtasks



Administration

Documentnumber


04-604378 Administering Avaya Aura®

ConferencingPerform system-wide administrationtasks

Systemadministrators

04-604403 Migrating Avaya Aura®

ConferencingPerform system-wide securityadministration and backup/restoretasks


04-604398 Maintaining andTroubleshooting Avaya Aura®

Conferencing

Perform maintenance andtroubleshooting tasks.

Understand logs and fault tracking.




Supporting

Documentnumber


04–604423 Avaya Aura® ConferencingAccounting Records Reference

Collect information about accountingrecords



04-604443 Avaya Aura® ConferencingAlarms and Logs Reference

Collect information about alarms andlogs, including the alarms and logsfamilies


Customers,Partners,

An Introduction to Avaya Aura® Conferencing



Documentnumber


Services, andSupportpersonnel

04-604444 Avaya Aura® ConferencingOperational MeasurementsReference

Collect information about operationalmeasurements




TrainingThe following courses are available on http://www.avaya-learning.com. In the Search field, type thecourse code, and click Go to search for the course.

Course code Course title2U00110O Selling Avaya Aura® Conferencing Solution Learning Bytes2U00325O Avaya Aura® Conferencing 7 L1 Customer Scenario3U00260W Designing Avaya Aura® Conferencing5U00120E Avaya Aura® Conferencing3204 Avaya Aura® Conferencing Implementation and Maintenance Exam

Viewing Avaya Mentor videosAvaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avayaproducts.

About this taskVideos are available on the Avaya Support website, listed under the video document type, and onthe Avaya-run channel on YouTube.

Procedure• To find videos on the Avaya Support website, go to support.avaya.com and perform one of the

following actions:

• In Search, type Avaya Mentor Videos to see a list of the available videos.

Related resources


http://www.avaya-learning.com



• In Search, type the product name. On the Search Results page, select Video in theContent Type column on the left.

• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor andperform one of the following actions:

• Enter a key word or key words in the Search Channel to search for a specific product ortopic.

• Scroll down Playlists, and click the name of a topic to see the available list of videos postedon the website.

Note:

Videos are not available for all products.

Deploying online helpAvaya Aura® Conferencing contains a number of online help files and online manuals to guide youthrough the process of installing, configuring, and maintaining your conferencing system. Theseonline help files include:

• Online help for Element Manager

• Online help for the Provisioning Client

• Online help for Reports

• Online help for users of Collaboration Agent

By default, each of these online help packages is fully integrated with the component which itdescribes. So, for example, if you view help on Element Manager, you can access the ElementManager online help. The Element Manager online help file describes each of the Element Managerfields and describes many of the common procedures that you can perform using the ElementManager interface.



http://www.youtube.com/AvayaMentor


Figure 1: Online Help for Element Manager

Figure 2: Online Help for the Provisioning Client

In the case of the online help for users of Collaboration Agent, Avaya has translated the online helpinto several languages. The list of available languages conforms with the i18n and L10n(internationalization and localization standards). When users install the Collaboration Agentapplication, it chooses which language to display based on the computer's locale.

The online help files are packaged within the Avaya Aura® Conferencing software applicationbundle.

Related resources



SupportGo to the Avaya Support website at http://support.avaya.com for the most up-to-datedocumentation, product notices, and knowledge articles. You can also search for release notes,downloads, and resolutions to issues. Use the online service request system to create a servicerequest. Chat with live agents to get answers to questions, or request an agent to connect you to asupport team if an issue requires additional expertise.

AudienceThe intended audience for this document is:

• Tier 1 Avaya technical support

• Avaya Professional Services

• Authorized Business Partners

You must have the following core competencies:

• The ability to access servers using:

- a locally attached keyboard and monitor or KVM (Keyboard, Video, Mouse) switch

- the ssh remote access protocol

• Basic Linux operations:

- navigating the file system (changing directories)

- managing the implications of uninformed or careless use of system commands while loggedin as the root user

• Basic server tasks:

- powering servers up

- powering servers down

- resetting servers

- inserting and removing CD-ROM and DVD-ROM disks

• Basic Microsoft knowledge:

Windows:

- editing text files

- creating folders

- Microsoft Excel:

• transitioning between worksheets of a workbook

• entering data into cells





• copying/pasting between cells and commands, such as Control+c, Control+v, and Edit >Paste Special menu

• The ability to operate a supported Web browser (such as Firefox or Internet Explorer):

- Interacting with pop-up windows

- Inspecting and accepting x.509 certificates and installing CA certificates that are presentedby the browser

- Downloading and installing software through the browser

• Basic Public Key Infrastructure (PKI) tasks:

- Creating Certificate Signing Requests (CSR)

- Inspecting the details of a certificate

- Installing Certificate Authority certificates on Windows Certificate Store

- Installing Personal certificates on Windows Certificate Store

- Installing Certificate Authority certificates on Firefox Certificate Manager

- Installing Your Certificates on Firefox Certificate Manager

How to use this documentYou must complete a given task successfully before beginning the next one. If you encounter issueswhile performing a step, contact the Avaya Support Web site at http://support.avaya.com to open aservice request.

Use the Avaya Aura® Conferencing 8.0 Intelligent Workbook together with this document to guideyou through the preparatory requirements and installation and configuration steps for Avaya Aura®

Conferencing. The Intelligent Workbook can be found on the Avaya Web site at http://support.avaya.com/.

Related LinksPreparing your data using the Avaya Aura Conferencing 8.0 Intelligent Workbook on page 15

Preparing your data using the Avaya Aura® Conferencing 8.0Intelligent Workbook

The Avaya Aura® Conferencing 8.0 Intelligent Workbook is a data collection tool. It is in theMicrosoft Excel format. The important tabs are Checklist, Design, and Configuration Data tabs.The other steps and tabs of the workbook are dynamic and depend on the layout selected in theDesign tab, so they might not be listed as they are listed below. This is an example of typical tabsthat might be visible:

• Instructions

How to use this document






• 0-Configuration Data

• 1-OS Linux Install

• 2-OS Patches Install

• 3-ACC Apps Install

• 4-Licensing

• 5-Single sign-on

• 6-Config AAC Services

• 7-Config Avaya Aura

• 8-Provisioning

• 9-Web Conferencing: Enabling Web conferencing

• 10-Video

• A-Flare for Windows and iPad

• B-Update AAC

• C-Apply patches

• FAQ

• Troubleshooting

• Values

Related LinksHow to use this document on page 15

Administrative user roles and preconfigured accountsRoles define operational boundaries (access permissions) for administrators. Administrators canhave more than one role, depending on their duties. You assign roles to new administrators whenyou create their accounts. During server installation, the installation software creates the followinguser accounts:

Preconfigured/Admin accounts

Defaultpassword

Preassigned role Description

ntsysadm password System SecurityAdministrator (SSA) role.

The SSA can perform systemconfiguration and specify securityattributes such as:

• Password configuration

• User management

• Certificate management





Defaultpassword


• Access control

• Antivirus

• File System Integrity tools

• Network configuration

• System backup and restorentappadm password Application Administrator

(AA) roleThe AA can install the Avaya Aura®

Conferencing application software andmanage components related to theapplication. The AA is responsible forinstalling, maintaining, patching, andupgrading Avaya Aura® Conferencingsoftware only.

ntsecadm password Security Auditor (SA) role The SA can collect and view securityaudit logs and syslogs at the platformlevel. The SA can also transfer thesecurity logs off the server.

ntbackup password Backup Administrator (BA)role

The BA can perform only systembackups. A BA cannot perform:

• any operation on the server exceptbackups.

• a system restore—only the SSA orroot user can perform a systemrestore.

ntdbadm password Database Administrator(DBA) role

The DBA can manage the databaseschemas and database tools onservers where the database resides.The server must host the database forthis role to be relevant.

ntossadm password Operational Support SystemAdministrator (OSS) role

Downstream processors can use thentossadm account with this role toconnect to the server and collect OSSlogs.

admin

admin1

admin2

admin3

admin4

admin5

admin

admin1

admin2

admin3

admin4

admin5

Unlimited privileges For expert mode login to Avaya Aura®

Conferencing, Element Manager, andProvisioning Manager.

init Not applicable System SecurityAdministrator (SSA) role and

SSA and DBA account for AvayaServices access.

Administrative user roles and preconfigured accounts




Defaultpassword


Database Administrator(DBA) role

craft Not applicable Application Administrator(AA) role

AA account for Avaya Services access

Supported Web browsersAvaya Aura® Conferencing supports the following browsers for Collaboration Agent users andAvaya Aura® Conferencing administrators. Administrators use the following applications toadminister and maintain Avaya Aura® Conferencing:

• Element Manager Console• Provisioning Client• Avaya Conferencing Reports & Monitors

Browsers Operating System Collaboration

Agent

AdministrationApplications

Microsoft InternetExplorer 7.0 and 8.0

Windows 7 yes yes

Microsoft InternetExplorer 9.0 and 10.0

Windows 7 yes yes

Mozilla Firefox

version 10 and later

Windows 7 yes yes

Google Chrome (latestversion)

Windows 7 yes -

Apple Safari (latestversion)

Apple OS X yes -

Possible limitations in relation to the Audio/Video in Collaboration Agent featureWhen running the Audio/Video in Collaboration Agent feature, Google Chrome may demonstratepoor lip synchronization. When Collaboration Agent detects when a user wishes to use the Audio/Video in Collaboration Agent feature in Google Chrome, it displays an information message toinform them of this possible limitation.

In addition, users running Google Chrome for the Mac operating system may experience issueswhen sharing their desktop. Avaya recommends using Apple Safari or Mozilla Firefox for desktopsharing instead.

Specific requirements in relation to the Avaya Web Collaboration audio and videoplug-inThe new Avaya Web Collaboration audio and video plug-in has a particular set of operating systemand browser requirements. These requirements are separate to the limitations that Avaya has




identified with the existing (Flash-based) Audio/Video in Collaboration Agent feature. The followingtable shows the (browser-based) Avaya Web Collaboration audio and video plug-in requirements:

Note:Avaya provides two options for integrated audio and video in this release: The existing (Flash-based) Audio/Video in Collaboration Agent and the new (browser-based) Avaya WebCollaboration audio and video plug-in.

Supported Operating Systems Supported BrowsersMicrosoft Windows Vista, 7, and 8. (32 and 64 bit)

Apple OS X 10.9, 10.8, and 10.7

Mozilla Firefox (latest version)

Google Chrome (latest version)

Microsoft Internet Explorer 8, 9, 10, and 11 forWindows

Apple Safari (latest version) for Apple OS X

Note:

For each of these browsers, the Avaya WebCollaboration audio and video plug-in requiresthe 32–bit versions.

The Avaya Web Collaboration audio and video plug-in does not operate successfully with thefollowing operating systems and browsers:

Unsupported Operating Systems Unsupported BrowsersOlder Microsoft Windows operating systems, such asMicrosoft Windows XP

Google Android and Apple iOS

Google Chrome

Linux

Microsoft Windows Mobile

Any 64–bit version of a browser

Microsoft Metro (Internet Explorer)

Opera

Any other mobile browsers

Supported hardwareAvaya Aura® Conferencing 8.0 supports the HP ProLiant DL360p G8 for all deploymentconfigurations. Alternatively, if you have an existing HP ProLiant DL360 G7, you can reuse it. If youhave existing Dell 610 or IBM S8800 servers, you may be able to reuse them as cascading AvayaMedia Server (MS)’s. However, you cannot reuse the Dell 610 or IBM S8800 servers as AvayaAura® Conferencing 8.0 core servers.

The hardware requirements for Avaya Aura® Conferencing 8.0 are the same whether you areinstalling the product in an Avaya Aura® deployment or a Turnkey deployment. In both cases, it isthe HP ProLiant DL360p G8 server.

Supported hardware



Server type Supported useHP ProLiantDL360p G8

Used for new installations of Avaya Aura® Conferencing 8.0.

HP ProLiantDL360 G7

Can be reused when upgrading existing Avaya Aura® Conferencing 7.2 deployments toAvaya Aura® Conferencing 8.0.4

Dell 610 Can only be used as cascading media servers within Avaya Aura® Conferencing 8.0deployments.5

IBM S8800 Can only be used as cascading media servers within Avaya Aura® Conferencing 8.0deployments.5

4 For Large deployments (previously known as Standalone in the Avaya Aura® Conferencing 7.x releases) the serverhosting the Element Manager and Database must have more than 12GB of RAM. If your server only has 12GB of RAMplease contact Avaya for a memory expansion kit and apply this kit prior to the upgrade to Avaya Aura® Conferencing8.x. For more information on installing and configuring the memory expansion kit, see Deploying Avaya Aura®

Conferencing 7.2.2, which is available from https://support.avaya.com/.5 For more information on cascading media servers, see Configuring cascading.



https://support.avaya.com/


Chapter 2: Migrating servers

Server replacementThis document describes the procedure for replacing an Avaya Aura® Conferencing 8.0 server. Theprocedure applies to the following situations:

• Recovering the Avaya Aura® Conferencing 8.0 software after a hardware server failure.

• Migrating the Avaya Aura® Conferencing 8.0 server from the hardware server that wasrecommended for use for the 7.0 and 7.2 releases to the HP ProLiant DL360p G8 server whichis commonly used for the Avaya Aura® Conferencing 8.0 release.

Note:

If you are going to migrate the server to the new hardware then you must upgrade the AvayaAura® Conferencing software on this server to Avaya Aura® Conferencing 8.0. This section onlycovers replacement and migration of the Avaya Aura® Conferencing 8.0 server to the newhardware, but does not cover upgrades from older Avaya Aura® Conferencing releases. Formore information about the upgrade procedures, see Upgrading Avaya Aura® Conferencingwhich is available from the Support website: http://www.avaya.com/support.

The steps here describe the replacement or migration of a single Avaya Aura® Conferencing 8.0server. However, your Avaya Aura® Conferencing system may consist of multiple servers.

The procedure is out of service. During replacement, the services provided by the server will not beavailable.

Prerequisites for server replacementStore the Avaya Aura® Conferencing 8.0 software DVD-ROMs or ISO images in a secure place

• AAC Platform DVD-ROM

• Application Bundle DVD-ROM

• Platform patches DVD-ROM

Note:

You can burn the ISO images to DVD-ROMs or use them directly.


http://www.avaya.com/support


Server replacement for simplex deploymentsThis section describes the procedure for Avaya Aura® Conferencing server replacement for SMBsimplex, medium simplex and large simplex deployments.

• If the server you want to replace is the primary Element Manager server, see Element Managerserver replacement for simplex deployments on page 22.

• If the server you want to replace is a non-primary Element Manager server, see Non-ElementManager server replacement for simplex deployments on page 24.

Related LinksElement Manager server replacement for simplex deployments on page 22Non-Element Manager server replacement for simplex deployments on page 24

Element Manager server replacement for simplex deploymentsThe following checklist shows the procedure for replacing the Element Manager server for simplexdeployments.

No. Task Description Notes

1 Review the prerequisites Prerequisites for serverreplacement on page 21

2 Determine which AvayaAura® Conferencingcomponents are hostedon this server

Determining whichcomponents are hosted onthe server on page 30

3 Backup Avaya Aura®

Conferencing if theserver is in stable state

Backing up Avaya Aura®

Conferencing for serverreplacement on page 35

If you successfully backup the Avaya Aura® Conferencing server in step 3 or you have previously backed upthe system to a remote backup server or a USB drive then proceed with steps below.

If you have not successfully backed up the Avaya Aura® Conferencing server, you must re-install AvayaAura® Conferencing completely. For more information, see Deploying Avaya Aura® Conferencing, which isavailable from the Avaya Support website:http://www.avaya.com/support

Note:

If you are restoring the system from a previously made backup, ensure that the software versions onthe backup are identical to the software versions that you use for the restore steps, below. Forexample, if you backed up the system when it was AAC 8.0 FP1 SP2 version (MCP 18.1.2.X), then youmust use the same version in the steps below.

4 Stop the network

element instanceshosted on this server if

Stopping a networkelement instance onpage 43

Migrating servers





the server is in stablestate

5 Stop the ElementManager instance if theserver is in stable state

Stopping an ElementManager Instance onpage 44

6 Restore the Avaya Aura®

Conferencing platform onthe server

Restoring the platformfollowing serverreplacement on page 44


Conferencing applicationdata on the server

Restoring an Avaya Aura®

Conferencing serverfollowing serverreplacement on page 59

8 Extract the Avaya Aura®

Conferencing ApplicationBundle contents to theElement Manager server

Extracting the applicationbundle contents onpage 61

9 Install the Avaya Aura®

Conferencing applicationdatabase to the ElementManager server

Installing the databasesoftware on page 62


Conferencing databaseto the primary ElementManager server

Installing the database onpage 63

11 Restore the databasefrom backup

Restoring the databasefollowing serverreplacement on page 63

12 Install the ElementManager

Installing ElementManager on page 64

13 If the server hosts amedia server then installAvaya Media Server(MS)

Installing Avaya MediaServer on page 64

14 Restore all the networkelement instances onthis server exceptElement Manager

Restoring a networkelement instance followingserver replacement onpage 65

15 If the server hosts arecording media serverthen restore therecordings

Restoring the recordingsfollowing serverreplacement on page 67

16 If the server hosts FlashMediaGateway then Install Flas

Restoring the Flash MediaGateway on page 68

Server replacement for simplex deployments




h Media Gateway andrestore its configuration

17 If this system isstandalone AAC theninstall WebLM service

Installing WebLM onpage 67

18 Verify that the AvayaAura® Conferencingsystem is operatingcorrectly for users in themain location

Verifying the system onpage 68

Related LinksServer replacement for simplex deployments on page 22

Non-Element Manager server replacement for simplexdeployments

The following checklist shows the procedure for replacing a non-Element Manager server forsimplex deployments.









Note:


4 Stop the network

element instanceshosted on this server ifthe server is in stablestate


Migrating servers






If you have a backed upserver, see Restoring theplatform following serverreplacement. onpage 44 If not, see Restoring the platform onpage 45



If you have a backed upserver, see Restoring anAvaya Aura® Conferencingserver following serverreplacement on page 59.If not, skip this step.



14 Restore all the networkelement instances onthis server




16 If the server hosts FlashMediaGateway then Install Flash Media Gateway




Related LinksServer replacement for simplex deployments on page 22

Server replacement for simplex deployments



Server replacement for redundant deploymentsThis section describes the procedure for Avaya Aura® Conferencing server replacement for SMBredundant, medium redundant and large redundant deployments.

• If the server you want to replace is the primary Element Manager server, see Primary ElementManager server replacement for redundant deployments on page 26.

• If the server you want to replace is a non-primary Element Manager server, see Non-primaryElement Manager server replacement for redundant deployments on page 28.

Related LinksPrimary Element Manager server replacement for redundant deployments on page 26Non-primary Element Manager server replacement for redundant deployments on page 28

Primary Element Manager server replacement for redundantdeployments

The following checklist shows the procedure for replacing the primary Element Manager server forredundant deployments.









Note:


4 Stop the network



Migrating servers




5 Stop the ElementManager instance if theserver is in stable state








8 Extract the Avaya Aura®

Conferencing ApplicationBundle contents to theElement Manager server

Extracting the applicationbundle contents onpage 61


Conferencing applicationdatabase to the ElementManager server



Conferencing databaseto the primary ElementManager server


11 Restore the databasefrom backup

If you have backed up theserver, seeRestoring thedatabase following serverreplacement on page 63.If not, see Re-syncing thedatabase data from thesecondary instance onpage 70.

12 Set up databasereplication

Setting up the databasereplication on page 71

13 Install the ElementManager

Installing ElementManager on page 64



Server replacement for redundant deployments




15 Restore all the networkelement instances onthis server exceptElement Manager






18 If this system isstandalone AAC theninstall WebLM service

Installing WebLM onpage 67



Related LinksServer replacement for redundant deployments on page 26

Non-primary Element Manager server replacement for redundantdeployments

The following checklist shows the procedure for replacing the non-primary Element Manager serversfor redundant deployments.









Migrating servers




Note:


4 Stop the network









9 If the server hosts thesecondary database,install the Avaya Aura®

Conferencing applicationdatabase


12 If the server hosts thesecondary database, setup database replication




15 Restore all the networkelement instances onthis server




Server replacement for redundant deployments








Related LinksServer replacement for redundant deployments on page 26

Determining which components are hosted on the serverAbout this taskUse this procedure to determine which components are hosted on the server. The Avaya Aura®

Conferencing server may have many different combinations of components deployed. You enter theappropriate information in the table below. The table has four columns:

1. Component name: Contains the names of the components. Each component is either anetwork element or an alternative item of software that can be deployed to the Avaya Aura®

Conferencing server.2. Deployed on server: Defines whether the component is deployed on the hardware server.3. Network Element name: Defines the long name of the network element. The network

elements are referenced by their long names in the Element Manager Console.4. Instance number: Defines the instance number of the component.

Component name Deployed on server Network Element name Instance numberElement Manager ElementManagerAccounting Manager AM1Provisioning Manager 0Collaboration Agent 0Application Server AS1Document ConversionServer

0

Media Server 0Web ConferencingManagement Server

0

Migrating servers



Component name Deployed on server Network Element name Instance numberWeb ConferencingServer

0

Database mcpdbFlash Media Gateway(FMG)

FMG 0

Some of the components, such as Element Manager have pre-defined network element names.This is the default name but administrators can change it. Some of the components, such asProvisioning Manager have pre-defined instance numbers. If the value is 0 then the component canonly have one instance. If the value is - then, the instance number is not applicable for thecomponent.

Procedure1. Log into Element Manager Console.

2. Determine the logical name of the IP address of the server.

a. In the navigation pane of Element Manager Console, select Addresses.b. In the Addresses window, view the IP address of the server and find the corresponding

logical name.

3. Determine the long server name and the short name of the server.

a. In the navigation pane of Element Manager Console, select Servers.b. In the Servers window, view the logical name of the IP address of the server in IPv4

Internal OAM column and find corresponding long server name and short name.

4. Enter the appropriate information in the Element Manager row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Element Manager > Element Manager > Instance.

b. In the Element Manager Instance window, check if the long server name of the serveris displayed in the Server column.

c. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Element Manager row of the table above:

Type YES in the Deployed on server column

Type the ID of the instance in the Instance number column

5. Enter the appropriate information in the Accounting Manager row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Accounting Managers > AM1 > Instance.

b. In the AM1 Instance window, check if the long server name of the server is displayed inthe Server column.

c. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Accounting Manager row of the table above:


Determining which components are hosted on the server



Type the ID of the instance in the Instance number column

6. Enter the appropriate information in the Provisioning Manager row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Provisioning Managers. For each network element listed in theProvisioning Managers window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Provisioning Managers > <Provisioning Manager name> > Instance.

c. In the <Provisioning Manager name> Instance window, check to see if the longserver name of the server is displayed in the Server column.

d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Provisioning Manager row of the table above:


Type the Provisioning Manager in the Network Element name column

7. Enter the appropriate information in the Collaboration Agent row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Collaboration Agents. For each network element listed in theCollaboration Agents window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Collaboration Agents > <Collaboration Agent name> > Instance.

c. In the <Collaboration Agent name> Instance window, check to see if the long servername of the server is displayed in the Server column.

d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Collaboration Agent row of the table above:


Type the Collaboration Agent in the Network Element name column

8. Enter the appropriate information in the Application Server row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Application Servers > AS1 > Instance.

b. In the AS1 Instance window, check if the long server name of the server is displayed inthe Server column.

c. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Application Server row of the table above:


Type the Application Server in the Instance number column

Migrating servers



9. Enter the appropriate information in the Document Conversion Server row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Document Conversion Servers. For each network element listed in theDocument Conversion Servers window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Document Conversion Servers > <Document Conversion name> >Instance.

c. In the <Document Conversion name> Instance window, check to see if the longserver name of the server is displayed in the Server column.

d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Document Conversion Server row of the table above:


Type the Document Conversion Server in the Network Element name column

10. Enter the appropriate information in the Media Server row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Media Servers and Clusters > Media Servers. For each network elementlisted in the Media Servers window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Media Servers and Clusters > Media Servers > <Media Server name> >Instance.

c. In the <Media Server name> Instance window, check to see if the long server name ofthe server is displayed in the Server column.

d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Media Server row of the table above:


Type the Media Server name in the Network Element name column

11. Enter the appropriate information in the Web Conferencing Management Server row in thetable above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Web Conferencing > Web Conferencing Management > WebConferencing Management Servers. For each network element listed in the WebConferencing Management Servers window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Web Conferencing > Web Conferencing Management > WebConferencing Management Servers > <Web Conferencing Manager Servername> > Instance.

c. In the <Web Conferencing Manager Server name> Instance window, check to see ifthe long server name of the server is displayed in the Server column.

Determining which components are hosted on the server



d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Media Server row of the table above:


Type the Web Conferencing Manager Server name in the Network Element namecolumn

12. Enter the appropriate information in the Web Conferencing Server row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Web Conferencing > Web Conferencing Servers and Clusters > WebConferencing Servers. For each network element listed in the Web ConferencingServers window, perform the following sub-steps.

b. In the navigation pane of Element Manager Console, select Feature ServerElements > Web Conferencing > Web Conferencing Servers and Clusters > WebConferencing Servers > <Web Conferencing Server name> > Instance.

c. In the <Web Conferencing Server name> Instance window, check to see if the longserver name of the server is displayed in the Server column.

d. If the long server name of the server is displayed, then find the corresponding ID and fillthe following cells in the Web Conferencing Server row of the table above:


Type the Web Conferencing Server name in the Network Element name column

13. Enter the appropriate information in the Database row in the table above.

a. In the navigation pane of Element Manager Console, select Feature ServerElements > Database > mcpdb > Configuration.

b. In the mcpdb Configuration window check if the short name of the server is displayed inthe Server column.

c. If the short name of the server is displayed, then find the corresponding InstanceNumber and fill the following cells in Database row of the table above:

Type YES in Deployed on server column

Type the ID of the instance in Instance number column

14. Enter the appropriate information in the Flash Media Gateway row in the table above.

ResultYou have now determined which components are hosted on the server.

Next stepsRefer back to your checklist for more information about your next task. You should always use yourchecklist for guidance. You should print it out so that you can mark each task as you complete it.

Migrating servers



Backing up Avaya Aura® Conferencing for serverreplacement

About this taskUse this task to backup Avaya Aura® Conferencing server.

Note:If the server is in failure state, it may be not possible to backup all the required data or even anydata. In such a case, you can use any previously made backups. If you are unable to backup aparticular component and there are no previously made backups, then you need to configurethe component manually.

Procedure1. If this server hosts Flash Media Gateway, see Backing up the flash media gateways for a

feature pack on page 36.

2. If this server hosts Media Server, see Backing up the Avaya media servers on page 36.

3. If this server hosts Recording Media Server, backup the recordings. See Backing upconference recordings on page 37.

4. If this server hosts the database, see Backing up the database for a feature/service pack ora patch on page 39.

5. Backup the server:

a. If this server is in Demilitarized Zone (DMZ) or if the networking issues are observed onthe server, backup the server to a USB drive. See Backing up the servers on page 40.

b. If this server is not in DMZ, backup the server to a remote drive. See Backing up theservers on page 40.

ResultThe Avaya Aura® Conferencing server is backed up.


Related LinksBacking up the Flash Media Gateway(s) for a feature pack on page 36Backing up the Avaya Media Server (MS) on page 36Backing up conference recordings on page 37Backing up the database for a feature pack, a service pack, or a patch on page 39Backing up the Avaya Aura Conferencing servers on page 40

Backing up Avaya Aura® Conferencing for server replacement



Backing up the Flash Media Gateway(s) for a feature packAbout this taskUse this procedure to backup Flash Media Gateway (FMG). The FMG is the server which enablesthe Audio/Video in Collaboration Agent functionality for Avaya Aura® Conferencing. The Audio/Videoin Collaboration Agent feature enables users to receive audio, video, and data content through asingle device.

Procedure1. Log on to the server which hosts Flash Media Gateway as a user with the SSA role (for

example, ntsysadm) through SSH or directly at the server console.

2. At the prompt, type su and press Enter.

3. Type the root password and press Enter to become the root user.

4. At the prompt, type /opt/Avaya/AccWeb/bin/backupConfig and press Enter.

A backup file is created and located at /var/mcp/fmg/backup directory.

5. Copy the Flash Media Gateway backup file to a remote backup server.

ResultThe Flash Media Gateway is backed up.


Related LinksBacking up Avaya Aura Conferencing for server replacement on page 35

Backing up the Avaya Media Server (MS)About this taskUse this procedure to backup the Avaya Media Server (MS).

Procedure1. Log on to the server which hosts Avaya Media Server (MS) as a user with the SSA role (for




4. At the prompt type msBackup.pl and press Enter.

Migrating servers



ResultA backup summary report is displayed. The backup file is stored in the /var/mcp/ma/MAS/platdata/EAM/Backups/latest folder.



Backing up conference recordingsAbout this taskUse this procedure to backup conference recordings.

Procedure1. Configure the SSH keys for conference recordings backup for all recording media server

clusters servers. For more information, see Configuring SSH keys for conference recordingsbackup on page 38.

2. Login to Element Manager Console.

3. In the navigation pane of Element Manager Console, select Addresses.

4. In the Addresses window, click Add.

5. In the Add IPv4 Address dialog box, complete the fields as described below:

Logical Name: Enter the logical name of the backup server's IP address.

IPv4 Address: Enter the IPv4 address of the backup server.

6. When finished, click Apply.

7. In the navigation pane of Element Manager Console, select External Nodes.

8. In the External Nodes window, click Add.

9. In the Add External Node dialog box, complete the fields as described below:

Name: Enter the name of the backup server external node.

IPv4 Address: Select the logical name of the IPv4 address of the backup server.


11. In the navigation pane of Element Manager Console, select Recording > BackupLocations.

12. In the Backup Locations window, click Add.

13. In the Add Backup Locations dialog box, complete the fields as described below:




Name: Enter the name of the backup server.

Node: Select the node for the backup server.

Path: Enter the absolute path under which recordings should be stored on the backupserver.


15. In the navigation pane of Element Manager Console, select Feature Server Elements >Media Servers and Clusters > Media Server Clusters > <Cluster Name> > Recording >Backup/Purge Settings.

The Backup/Purge Settings dialog box is displayed.

16. In the Backup/Purge Settings dialog box, perform the following steps:

a. Select the Backup checkbox.

b. Select the Daily radio button.

c. Select the recording location in the Location drop-down menu.

17. When you are finished, click OK.

18. In the navigation pane of Element Manager Console, select Feature Server Elements >Media Servers and Clusters > Media Server Clusters > <Cluster Name> > Recording >Backup/Purge Maintenance.

The Backup/Purge Maintenance window is displayed.

19. Click Start.

The Status column displays the current status of the operation. When the operation iscomplete, the Status column displays the word, Completed.

20. (Optional) If you want to view the detailed status of the backup, click Details.

ResultConference recordings are backed up.


Related LinksBacking up Avaya Aura Conferencing for server replacement on page 35Configuring SSH keys for conference recordings backup on page 38

Configuring SSH keys for conference recordings backupAbout this taskUse this procedure to configure SSH keys for conference recordings backup.

Migrating servers



Procedure1. Log on to the server which hosts the Avaya Media Server as ntsysadm through SSH or

directly at the server console.

2. At the prompt, type configRecordingBackup -backupip <Backup server IPaddress> -backupuser <Name of user on the backup server> and pressEnter.

3. At the [sudo] password for ntsysadm prompt type sudo password and press Enter.

4. At the <username>@<IP address>’s password prompt type the backup server user'spassword and press Enter.

ResultSSH keys for conference recordings backup are configured.


Related LinksBacking up conference recordings on page 37

Backing up the database for a feature pack, a service pack, or apatch

Note:

The default name for the database is mcpdb. The example commands in this procedure usemcpdb for the database name. If mcpdb is NOT the name of the database (the value for thedb.neName parameter from the installprops.txt file), replace mcpdb_0 with your<db.neName>_0 in the command.

About this taskUse this procedure to backup the database.

Procedure1. Log on to the primary database server as a user with the DBA role.

2. At the prompt type cd /var/mcp/run/MCP_18.0/mcpdb_0/bin/util and press Enter.

3. At the prompt type ./dbBackup.pl <BackupFileName> and press Enter.

ResultThe backup file is created and stored in the /var/mcp/db/backup/latest folder. The backupfile name is <BackupFileName>.tar.gz. The previous manual backup file is moved tothe /var/mcp/db/backup folder. If the/var/mcp/db/backup/latest folder contains a




scheduled automatic backup file, the automatic backup file is moved to the /var/mcp/db/backup/AUTO_history folder.



Backing up the Avaya Aura® Conferencing serversAbout this taskUse this procedure to backup an Avaya Aura® Conferencing server.

Procedure1. Clean up any unneeded files from the server. For more information, see Cleaning up

unneeded files from the server on page 41 and Removing unneeded installers ofPostgreSQL from the Element Manager server on page 42.

2. Configure the remote backup parameters. For more information, see Configuring remotebackup parameters on page 42.

3. Log on to the server using an account with the BA or SSA role, for example, ntsysadm user.

4. At the prompt type bkupSvr -remote and press Enter.

• If you want to back up the servers to a USB drive, type bkupSvr -usbdrive and pressEnter.

5. Enter the password (if required).

ResultAfter the backup is complete, a summary report displays the results of the backup. It is important tocheck the following items in the summary report to:

• Ensure that all backup sets completed successfully.• Note the name and location of the tar file(s) produced.• Note the name and location of the log file produced. If errors occur, see the log file for more

information.


Related LinksBacking up Avaya Aura Conferencing for server replacement on page 35Cleaning up unneeded files from the server on page 41Removing unneeded installers of PostgreSQL from the Element Manager server on page 42

Migrating servers



Configuring remote backup parameters on page 42

Cleaning up unneeded files from the serverThe /var/mcp/loads folder should contain three or fewer loads. When an MR with multiple patchloads exists, keep the latest base/MR load and the latest associated patch load.

Important:

You must delete the loads from the primary Element Manager and the secondary ElementManager simultaneously because the primary Element Manager and the secondary ElementManager monitor the loads. If the load is on one server but not on the other server, the ElementManager copies the loads back to the other Element Manager server.

About this taskUse this procedure to remove old and unneeded loads from the Element Manager servers.

Procedure1. Log on to the primary Element Manager server using an account with the AA role

(ntappadm).

2. In another window, log on to the secondary Element Manager server using an account withthe AA role (ntappadm).

3. On the primary Element Manager server, enter cd /var/mcp/loads.

4. On the secondary Element Manager server, enter cd /var/mcp/loads.

5. On the primary Element Manager server, enter the following command, but do not press theENTER key: rm –rf <loadname>.

6. On the secondary Element Manager server, enter the following command, but do not pressthe ENTER key: rm –rf <loadname>.

7. As close together as possible, press the ENTER key in both the primary Element Managerwindow and the secondary Element Manager window.

ResultThe specified load is removed from the primary Element Manager server and the secondaryElement Manager server.


Related LinksBacking up the Avaya Aura Conferencing servers on page 40




Removing unneeded installers of PostgreSQL from the Element Managerserver

The file name format for installers of PostgreSQL is installer-mcp-postgresql-x.x.xxx.LINUX64.zip.

About this taskUse this procedure to remove old and unneeded installers of PostgreSQL from the ElementManager server with the primary database.

Procedure1. Log on to the Element Manager server with the primary database using an account with the

AA role (ntappadm).

2. Enter cd /var/mcp/media.

3. Enter rm -rf <filename>.

4. Repeat Step 3 for each installer you want to remove.

ResultThe specified installers of PostgreSQL are removed from the Element Manager server.



Configuring remote backup parametersAbout this taskUse this procedure to configure remote backup parameters

Procedure1. Log on to the server for which you want to configure remote backup parameters as

ntsysadm user.

2. Type the ntsysadm password at [sudo] password for ntsysadm prompt and pressEnter.

3. At the prompt, type configBkup and press Enter.

4. Type 2 at Please enter the number [1 to 7] of the type of configuration operationprompt and press Enter.

5. Type Y at Enable remote backup/transfer for listed BackupSets (Y/N)? prompt and pressEnter.

Migrating servers



6. Type the IP address of the backup server at the Enter the IP address of the backup server(in dot notation) prompt and press Enter.

7. Type the path to the directory where backup files will be stored at the Enter the full path ofthe remote "backup to" directory prompt and press Enter.

8. Type the name of the backup user on backup server at the Enter userid for login to x.x.x.xprompt and press Enter.

9. Press Enter at the Please enter a passphrase for the bkrstr-all private key (or <ENTER>for no passphrase) prompt.

10. Type N at the Would you like to protect it with a passphrase (Y/N)? prompt and pressEnter.

11. Type Y at the Are you sure you want to continue connecting (yes/no)? prompt and pressEnter.

12. Type the password of the backup user on the backup server at the Please [email protected]'s password prompt and press Enter.

ResultRemote backup parameters are configured.



Stopping a network element instanceAbout this taskUse this procedure to stop a network element instance.

Procedure1. In the navigation pane of Element Manager Console, select Feature Server Elements >

<network element type> > <network element instance you want to stop > NEMaintenance.

2. In the Maintenance window, select the row that has a value of the target instance in the IDcolumn.

3. Click Stop.

The Maint state changes from None to Stopping, indicating that the stop operation is inprogress. When the stop operation is complete, the following state changes occur:

• The Maint state changes back to None.

Stopping a network element instance



• The Admin state changes from Online to Offline.

4. Close the Maintenance window.

ResultThe network element instance is stopped.


Stopping an Element Manager instanceAbout this taskUse this procedure to stop a network element instance of Element Manager.

Procedure1. In the navigation pane of Element Manager Console, select Feature Server Elements>

Element Manager > Element Manager > NE Maintenance.

2. In the NE Maintenance window, select the row for the primary instance of Element Manager(EM_0).

3. Click Stop.

The Confirmation dialog box appears, prompting you to confirm that you want to stop theactive Element Manager.

4. In the Confirmation dialog box, click OK.


ResultThe network element instance is stopped.


Restoring the platform following server replacementAbout this taskUse this task to restore the Avaya Aura® Conferencing platform

Migrating servers



Procedure1. If you have the backup of this server on remote backup server, see Restoring the platform

from a remote backup server on page 45.

2. If you have the backup of this server on USB drive, see Restoring the platform from a USBdrive on page 47.

3. If you do not have the backup of this server, see Installing the platform on page 49.

ResultThe Avaya Aura® Conferencing platform is restored


Related LinksRestoring the platform from a remote backup server on page 45Restoring the platform from a USB drive on page 47Installing the AAC Platform on page 49

Restoring the platform from a remote backup serverAvaya supplies a tool called upgradePrepKit to help you with this task. This tool is not part of theAvaya Aura® Conferencing core bundle of software. You can obtain the tool from https://support.avaya.com/. This tool is easy to use and automates many of the steps involved in therestore procedure. The manual restore steps are included here for your reference.

About this taskUse this procedure to restore the Avaya Aura® Conferencing platform from a remote backup server.

Procedure1. Insert the AAC Platform DVD-ROM, and reboot the server.

The following message on the installation welcome screen appears:

Welcome to the MCP Core Linux System Installer2. At the boot prompt, type install-kvm, and press Enter.

3. To check the integrity of the install media, type y, and press Enter.

Important:

If you do not check the integrity, a defective DVD-ROM or optical drive can goundetected and result in an installation failure.

If you receive a message indicating that the integrity check has failed, follow therecommendations to clean or replace DVD-ROM, or replace the optical drive.

Restoring the platform following server replacement


HTTPS://SUPPORT.AVAYA.COM/



If there are no issues with the integrity check, the installation continues to the next prompt.

4. At the prompt, Would you like to view licensing information? (Y/N) [Y]?• Type n if you have already viewed the licensing information from a previous server

installation, and press Enter. Proceed to Step 5.

OR• Type y to acknowledge the licensing attributes, and press Enter.

You are prompted for the following:

a. At the prompt, Enter Selection, select one of the following:

• Enter 1 for a Licensing overview.• Enter 2 for a summary of Open Source RPMs and Licenses.• Enter 3 to exit.

b. Press Enter until the Enter Selection prompt appears again.

c. At the prompt to acknowledge the licensing information, type y, and press Enter.

Warning:

In the following step, the installer erases all existing data on the primary disk drive. Thedata on the secondary disk drive is preserved

5. At the Continue [c], abort [a] prompt, type c to continue, and press Enter.

6. At the prompt, Do you want to keep this date and time (Y/N) [Y].

• Type y to keep the current system date and time, and press Enter. Proceed to the nextstep.

• Type n to change the system date and time from the BIOS clock, and press Enter.

Proceed to Modifying the BIOS clock.

7. The installer attempts to identify the hardware type of the target server, perform one of thefollowing:

• If the installer has detected your target server as a known reference server:

Type A to accept and proceed to Step 9 or type O and proceed to Classifying the hardwareenvironment.

OR• The installer does not detect your target server as a known reference server:

At the prompt, type a number that corresponds to your hardware type, and press Enter.

8. At the prompt, Is this information correct? y/n, type y to continue or n to correct.

9. At the prompt to choose the install type, type 2 and press Enter.

10. At the Enter the VLAN ID for the local network (0=no VLAN) (0-4094)[0] prompt press Enter.

Migrating servers



11. At the Enter this machine's IP address prompt type the IP address of server andpress Enter.

12. At the Enter the default gateway IP address prompt type the gateway IP addressof this server and press Enter.

13. At the Enter the netmask prompt type the server’s netmask and press Enter.

14. At the Enter the SFTP server's IP address prompt type the IP address of thebackup server and press Enter.

15. At the Enter the SFTP user id prompt type the name of backup user on backup serverand press Enter.

16. At the Enter the SFTP password prompt type the password of the backup user on thebackup server and press Enter.

17. At the Enter the remote SFTP directory prompt type the path to the directory wherebackup file is stored and press Enter.

18. At the Is this information correct (Y/N) prompt of the Secure FTP ConfigurationValidation screen check the information, type Y and press Enter.

19. At the Enter Tar File prompt type the number of the correct backup file for this serverlisted above and press Enter.

20. At the Continue [c], Abort [a] prompt of the Configuration Validation screen checkthe information, type c and press Enter.

21. At the Continue [c], Abort [a] prompt of the The following User Accounts will berestored screen check the information, type c and press Enter.

22. At the Press the Enter Key to continue with the installation... prompt ofthe System Configuration Complete screen press Enter.

23. Wait until the installation is completed and the server will reboot.



Related LinksRestoring the platform following server replacement on page 44

Restoring the platform from a USB driveAbout this taskUse this procedure to restore the Avaya Aura® Conferencing platform from a USB drive.







3. To check the integrity of the install media, type y, and press Enter.

Important:





installation, and press Enter. Proceed to Step 5.

OR• Type y to acknowledge the licensing attributes, and press Enter.



• Enter 1 for a Licensing overview.

• Enter 2 for a summary of Open Source RPMs and Licenses.

• Enter 3 to exit.



Warning:

In the following step, the installer erases all existing data on the primary disk drive. Thedata on the secondary disk drive is preserved




• Type n to change the system date and time from the BIOS clock, and press Enter.

Proceed to Modifying the BIOS clock.

Migrating servers





Type A to accept and proceed to Step 9 or type O and proceed to Classifying the hardwareenvironment.

OR

• The installer does not detect your target server as a known reference server:



9. At the prompt to choose the install type, type 3 and press Enter.

10. At the Enter Tar File prompt type the number of the correct backup file for this serverlisted above and press Enter.

11. At the Continue [c], Abort [a] prompt of the Configuration Validation screen checkthe information, type c and press Enter.

12. At the Continue [c], Abort [a] prompt of the The following User Accounts will berestored screen check the information, type c and press Enter.

13. At the Press the Enter Key to continue with the installation... prompt ofthe System Configuration Complete screen press Enter.

14. Wait until the installation is completed and the server will reboot.

15. Disconnect the USB drive from the server.



Related LinksRestoring the platform following server replacement on page 44

Installing the AAC PlatformThis section provides the procedures for installing the Avaya Aura® Conferencing platform operatingsystem and base level packages to the target servers required for the initial system installation.

Before you begin• Ensure that you have the skills required to install, configure, and upgrade Avaya Aura®

Conferencing. For a list of the required core competencies, see Audience on page 14. Beforeundertaking any advanced procedures, you must complete the required Avaya Aura®




Conferencing training, as listed in Training on page 11. Avaya recommends that you downloadall available Avaya Aura® Conferencing documentation, as listed in Documentation on page 8.

• Obtain the latest Avaya Aura® Conferencing 8.0 Platform DVD-ROM and the ApplicationBundle DVD-ROM.

• Obtain the Linux service pack patch disk.• Ensure that the DVD-ROM drive is selected as the first priority boot device in the system BIOS

(typically configured during initial BIOS setup).• Ensure that the server backup file is on a remote server• Ensure access to the server console through a locally attached keyboard and monitor or a

Keyboard, video card, and monitor (KVM) switch.• Plan and identify the deployment layout including all network IP addresses, hostnames, and

FQDNs using the Avaya Aura® Conferencing Intelligent Workbook.• Plan and identify any expansion servers using the Avaya Aura® Conferencing Intelligent

Workbook.

About this taskAvaya Aura® Conferencing must be installed on a Linux platform. Use the following procedure toinstall the Avaya Aura® Conferencing platform operating system and base level packages on the HPProLiant DL360p G8 server.




3. To check the integrity of the system, type y, and press Enter.

Important:





installation, and press Enter. Proceed to Step 5 on page 51.

OR

• Type y to acknowledge the licensing attributes, and press Enter.

Migrating servers





• Enter 1 for a Licensing overview.• Enter 2 for a summary of Open Source RPMs and Licenses.• Enter 3 to exit.



Warning:

In the following step, the installer erases all existing data on the attached disk drives.




• Type n to change the system date and time from the BIOS clock, and press Enter.Proceed to Modifying the BIOS clock on page 52.



Type A to accept and proceed to Step 9 on page 51 or type O and proceed to Classifyingthe hardware environment on page 52.

OR• The installer does not detect your target server as a known reference server:



9. At the prompt to choose the install type, type 1 to select Manual Install, and press Enter.

10. On the System Configuration screen, at the prompt, Press the Enter Key to beginconfiguration, press Enter, and proceed to Configuring the system on page 53.

11. Configure the NTP clock source settings. See Configuring the NTP clock on page 56.

12. Configure the Syslog Server. See Configuring the Syslog Server on page 58.

Related LinksRestoring the platform following server replacement on page 44Modifying the BIOS clock on page 52Classifying the hardware environment on page 52Configuring the system on page 53Configuring the NTP clock on page 56




Configuring the Syslog Server on page 58

Modifying the BIOS clockDuring the software installation of the target server, you can modify the BIOS clock.

Before you beginThe procedure for Installing the license attributes is completed.

Procedure1. At the prompt Enter the month (1-12) [x] type the number that represents the

current month, and press Enter. For example, 1 represents January and 12 representsDecember.

2. At the prompt Enter the day (1-xx) [x] type the value for the current date, and pressEnter.

3. At the prompt Enter the year (YYYY) [xxxx] type the current year, and press Enter.

4. At the prompt Enter the hour (0-23) [xx] type the value for the current hour usingthe 24–hour clock, and press Enter. For example, the first hour of the day is 0 and the lasthour of the day is 23.

5. At the prompt Enter the minutes (0-59) [xx], type the minutes using the 24–hourclock, and press Enter. For example, the first minute of the day is 0 and the last minute ofthe day is 59.

6. At the prompt Do you want to keep this date and time (Y/N) [Y] ?, type y tosave your changes, and press Enter.

ResultThe BIOS clock is modified. To verify the procedure:

• Log in as the root user and check that date is set correctly by running date command.

Next stepsRefer back to Step 7 on page 51 in Installing the AAC Platform on page 49 to continue with theinstallation process.

Related LinksInstalling the AAC Platform on page 49

Classifying the hardware environmentDuring the software installation of the target server, you can classify the server hardware as either aknown reference server or as a non-reference server. The installer usually determines thisclassification but it can be manually changed in the following procedure.

Note:

If two disks have been detected and the reference server does not support the RAID-1 software,the two physical disks are identified by the installer as a single disk drive. If a single disk has

Migrating servers



been detected and the reference server requires two disks for RAID-1 disk mirroring, theinstallation aborts.

About this taskConfigure the target server as a reference or non-reference server and to change the defaulthardware.

Procedure1. If the installer identifies the target server as a reference server, choose the number in the list

that corresponds to the hardware type, and proceed to Step 3. For example, type 7 for HPDL360 G8.

2. If the installer does not detect the server as a reference server, a list of hardware optionsappears, type 1 for Other, and press Enter. Proceed to Step 4.

3. If the target server is a reference server, at the prompt, Hardware Environment:<hardware platform>, for example, HP DL360 G8, type y, and press Enter.

4. If the installer detects a non-reference server, at the prompt, Hardware Environment:Other, type y, and press Enter.

5. A message appears to indicate the size and number of disks. If the physical diskconfiguration matches the requirements for the reference server, press Enter to continue.

• If one of the two disks detected on the target server is not a RAID logical disk, at theprompt, type y, and press Enter to configure RAID-1 between the two disks.

• If configuring RAID-1, a message appears indicating the size of the disk, press Enter.

The hardware is configured.

ResultThe hardware is classified. To verify the procedure:

1. Log in as the root user and run the command swversion.pl | grep Hardware.2. Check that hardware type is the same as was entered during platform installation.

For example, HP ProLiant DL360p G8.



Configuring the systemDuring the Linux operating system installation, you are prompted to configure the usernames,passwords, server time, IP address, DNS, and hardware type for your system.

About this taskConfigure the system.




Procedure1. On the Network Configuration screen, at the prompt Enter hostname (FQDN), type a

hostname for the server.

Note:

You must enter the fully qualified domain name (FQDN) in the Enter hostname field,rather than the short name.

2. At the prompt Enter bond name [bond0], press Enter to accept the default.

A list of available Ethernet Network interfaces appears.

3. At the prompt Enter the first slave [eth0] type the Bond0 Slave0 value for theserver or press Enter to accept the default value.

4. At the prompt Enter the second slave [eth1], type the Bond0 Slave1 value for theserver or press Enter to accept the default value.

5. At the prompt Enter VLAN ID (0=no VLAN) (0-4094), type 0 as this is not supported,and press Enter.

6. At the prompt Enter subnet name [sn0], press Enter to accept the default value.

7. At the prompt Enter IP address, type the Network IP address of the server, and pressEnter.

8. At the prompt, Enter subnet prefix length (1-32), type the Network Prefix of theserver, and press Enter.

9. At the prompt Enter gateway IP address, type the Network Default Gateway, andpress Enter.

10. At the prompt Do you want to configure DNS Client? (Y/N) [Y], type y andpress Enter.

The following prompt appears:Please select one of the following actions:– [A]dd Domain Suffix(es)- Re[S]elect all Domain Suffix(es)- [C]ontinue

11. At the prompt, type c to continue or a to add suffixes, and press Enter.

12. At the prompt How many DNS Servers would you like to reference (1-3)[1], type the number of available DNS servers, and press Enter.

13. At the prompt Enter DNS Server, type the IP address of the DNS server, and pressEnter.

14. At the prompt You entered “<IP address>”. Is this correct? (Y/N) [N],verify the IP address.

15. If the IP address is correct, type y and press Enter.

Migrating servers



16. The System Console Redirection screen appears. At the prompt Select an option (1–3), type 3 to select Do not redirect the system console after installationas the default, and press Enter.

17. The Timezone Selection screen appears. At the prompt Enter Region (1-62), type thenumber that corresponds to the Timezone Field1 for the target server, and press Enter.

18. If you see the screen Timezone Selection for Region, at the prompt Enter Timezone, typethe number that corresponds to the Timezone Field2 for the target server, and press Enter.

19. The Configuration Validation screen appears. Type y to accept the values or type n toreenter the information. Press Enter.

ResultThe system is configured. To verify the procedure:

1. Log in as the root user.2. Check that the Hostname is set correctly by running hostname command.

3. Check that the network is configured correctly:

Run cat /admin/nwk/userinfo.txt and check that bond name, slave names, VLANID, subnet name, server IP, Network Prefix and Network Default Gateway are configuredcorrectly.

Run ifconfig and check that bond name, slave names, subnet name, server IP, andNetwork Default Gateway are configured correctly.

Run ping <server IP> to check that system is a ping-able from an external server.

4. Check that the DNS is configured correctly:

Run cat /etc/resolv.conf | grep name and check that all configured DNS serversare present at displayed list.

Run cat /etc/resolv.conf | grep search and check that all configured DomainSuffix are present at displayed list.

Run nslookup `hostname` and check that the DNS hostname name was resolvedsuccessfully.

Run nslookup <server IP> and check that the server IP was resolved successfully.

5. Check that the timezone is configured correctly.

Run tzConfig.pl. Then, press ENTER and check that default value for Timezone is thesame as it was entered during installation. Press ENTER in order to complete working withtzConfig.pl.






Configuring the NTP clockDuring the software installation, you are prompted to configure the Network Time Protocol (NTP)settings.

Note:

You must use the same NTP sources that are being used on the System Manager. For moreinformation about the NTP server IP addresses, see the Avaya Aura® Conferencing IntelligentWorkbook.

About this taskConfigure the NTP clock settings.

Procedure1. At the prompt, Please indicate the Clock Source function of this server:

• 1. Primary Clock Source server (primary Element Manager servermachine). For example, EMServer1.

• 2. Secondary Clock Source server (secondary Element Manager servermachine). For example, EMServer2.

• 3. This server is NOT a Clock Source server (all other servermachines). If you select this option, continue to Step 5 on page 57.

Select an option (1–3):Note:

If this is a non-redundant layout and you are configuring a server hosting ElementManager, type 1, and press Enter.

2. The primary clock source server requires an external clock. At the prompt, SelectExternal Clock for time source(s) external to this server.Select Internal clock to use the system clock as the time source.E — External Clock Source (IP Addresses)I — Internal Clock (Unreliable)Select an option (E, I): Type e, and press Enter.

3. At the prompt How many external clock sources would you like toreference (1–2) [1], type a number based on the following:

• If both External Clock Source #1 and External Clock Source #2 have an IP address, type2, and press Enter.

• If there is only one external clock source, type 1 or press Enter to accept the default.

4. At the prompt Enter Clock Source IP address #1, type the IP address for theexternal clock source.

If you have more than one clock source, a second prompt appears.

Migrating servers



5. At the prompt, Enter IP Address of Primary Clock Source, type the IP addressfor the Primary Clock Source, and press Enter.

If you have a secondary clock source, a second prompt appears.

6. At the prompt, Enter IP Address of Secondary Clock Source, type the IP addressfor the Secondary Clock Source, and press Enter.

Note:

For non-redundant layouts, you can use the same IP address for primary and secondaryclock source.

7. At the prompt, Is this information correct? Y/N [N], type y to continue or n tocorrect.

8. At the prompt, Please indicate the Clock Source function of this server:a. Primary clock Source server (primary Element Manager server

machine)b. Secondary Clock Source server (secondary Element Manager server

machine)c. This server is NOT a Clock Source server (all other server

machines)Select an option (1–3) [1]. Type 2, and press Enter.

9. At the prompt, The Secondary Clock Source server requires the use of anexternal clock.Select External Clock for time source(s) external to this server.

Select Internal Clock to use the local system clock as the time source.

E - External Clock source (IP Addresses)I - Internal Clock (Unreliable)Select an option (E, I): Type e, and press Enter.

10. At the prompt, How many external clock sources would you like toreference (1–2) [1], type 2, and press Enter.

11. At the prompt, Enter IP Address of Primary Clock Source:, type the IP address,and press Enter.

ResultThe NTP clock is configured. To verify the procedure:

1. Log in as the root user.2. Run the command ntpConfig.pl and at the following prompt Do you wish to

configure/display the NTP configuration? Enter 'c' to configure, 'd'to display, or 'q' to quit [c/d/q]:, enter d and check that NTP servers areconfigured correctly and time is synchronized with NTP server.




3. At the prompt Do you wish to configure/display the NTP configuration?Enter 'c' to configure, 'd' to display, or 'q' to quit [c/d/q]:, enterq to complete work with ntpConfig.pl script.

4. Run following commands and check that the NTP shift is small and there is no issues:service ntpd stopntpdate <ntpServer_ip>service ntpd start



Configuring the Syslog ServerDuring the Linux operating system installation, you are prompted to configure the Syslog Server.

About this taskConfigure the settings for the Syslog Server, if required.

Procedure1. On the Syslog Configuration screen, at the prompt Do you wish to configure a

Syslog Server IP address (Y/N) [N]?, type n (default), and press Enter. Proceedto the next section for viewing the user accounts and passwords.

• If you want to configure the Syslog Server IP address, type y, and press Enter. Proceedto the next step.

2. At the prompt Enter the Syslog Server IP address, type the value for the Syslog IPaddress, and press Enter.

3. On the Configuration Validation screen, if the values are correct, type y, and press Enter toaccept and continue or type n, and press Enter to reenter the data.

ResultThe syslog is configured. To verify the procedure:

1. Log in as the root user and run the command syslogConfig.pl.

2. At the Do you wish to configure/unconfigure/display the SysLog ServerIP Address? Enter 'c' to configure, 'u' to unconfigure, 'd' todisplay, or 'q' to quit [c/u/d/q]: prompt, enter d in order to see if the syslog isconfigured correctly.

3. At the Do you wish to configure/unconfigure/display the SysLog ServerIP Address? Enter 'c' to configure, 'u' to unconfigure, 'd' todisplay, or 'q' to quit [c/u/d/q]: prompt, enter q to complete working with thesyslogConfig.pl script.

Migrating servers



4. Run the command ntpConfig.pl.

5. At the Do you wish to configure/display the NTP configuration? Enter'c' to configure, 'd' to display, or 'q' to quit [c/d/q]: prompt, enterc in order to emulate the ntp changing. This is required in order to send a message to thesyslog.

6. Press ENTER and accept the default values.

Wait until the ntpConfig.pl script completes.

7. Take a look in syslog logs on the syslog server and check that the logs about the ntp updateappeared.



Restoring an Avaya Aura® Conferencing server followingserver replacement

About this taskUse this task to restore the Avaya Aura® Conferencing server. Skip this task if you do not have anybackups.

Procedure1. If you have the backup of this server on remote backup server, restore the server using the

restoreSvr -remote command. For more information, see Restoring an Avaya Aura®

Conferencing server on page 60.

2. If you have the backup of this server on USB drive, restore the server using therestoreSvr -usbdrive command. For more information, see Restoring an Avaya Aura®

Conferencing server on page 60.

ResultThe Avaya Aura® Conferencing server is restored.


Related LinksRestoring an Avaya Aura Conferencing server on page 60

Restoring an Avaya Aura® Conferencing server following server replacement



Restoring an Avaya Aura® Conferencing serverThe restore of a server's operating system and configuration data (that is, “server” data) consists ofre-installing and commissioning the server and utilizing the previously backed up serverconfiguration data to restore the server. For instructions on installation and commissioning an AvayaAura® Conferencing server, see Deploying Avaya Aura® Conferencing 8.0, which is available from https://support.avaya.com/.

Important:

The information stored for a particular server is specific to that server. Do not use administrationdata (or any Platform data or Application data) for a server other than the server from which thedata was originally backed up.

This procedure contains the details regarding the execution of the restoreSvr script, whichrestores the server data. This server data includes the Avaya Aura® Conferencing data forEMServer1 and the backups of the database for the server hosting both database applications.

You must re-install and commission all servers with the Platform data used as the remoteadministration date.

About this taskUse this procedure to restore the Avaya Aura® Conferencing server.

Procedure1. Configure the remote backup parameters on the server. For more information, see

Configuring remote backup parameters on page 42.

2. Log on to the server which you want to restore as ntsysadm user.

3. At the prompt, type restoreSvr -remote and press Enter.

• If you want to back up the servers to a USB drive, type restoreSvr -usbdrive andpress Enter.

4. Type ntsysadm's password at [sudo] password for ntsysadm prompt and pressEnter.

5. Type the pass phrase for SvrBkup Job identity if it is required and press Enter.

6. Type the appropriate number to select a backup file from the list and press Enter.

7. Enter Y to confirm restore from selected backup file.

8. Repeat Steps 6 to 7 until the server is restored completely.

ResultThe Avaya Aura® Conferencing server is restored.


Migrating servers




Related LinksRestoring an Avaya Aura Conferencing server following server replacement on page 59

Extracting the application bundle contentsBefore you begin

• Make sure you have the latest version of the following Avaya Aura® Conferencing 8.0 software:- Avaya Aura® Conferencing application bundle

You can download the ISO images of this software from the PLDS Web site and burn the ISOimages to DVD- ROM.

• Ensure that you have the skills required to install, configure, and upgrade Avaya Aura®

Conferencing. For a list of the required core competencies, see Audience on page 14. Beforeundertaking any advanced procedures, you must complete the required Avaya Aura®

Conferencing training, as listed in Training on page 11. Avaya recommends that you downloadall available Avaya Aura® Conferencing documentation, as listed in Documentation on page 8.

About this taskUse this procedure to extract the Avaya Aura® Conferencing 8.0 application bundle contents to theprimary Element Manager server.

Procedure1. Insert the Avaya Aura® Conferencing 8.0 Application Bundle DVD-ROM in the primary

Element Manager server. If you don’t have a DVD-ROM then copy the Avaya Aura®

Conferencing 8.0 Application Bundle ISO image to the primary Element Manager server andplace it in the /var/mcp/extract directory using the ntappadm account.

2. Log on to the primary Element Manager server as a user with the AA role (for example,ntappadm) through SSH or directly at the server console and type mcpExtractContent -aat and press Enter.

3. Type the number corresponding to the Application Bundle ISO image that you want toextract or the number of Optical drive option, if you want to extract contents from DVD-ROM.Press Enter.

ResultAll required installation files are present on the primary Element Manager server.


Extracting the application bundle contents



Installing the database softwareAbout this taskUse this procedure to install the database software.

Procedure1. Log on to the primary Element Manager server (that is, the server hosting EM instance 0) as

a user with the SA role (for example, ntappadm) through SSH or directly at the serverconsole.

2. At the prompt, type cd /var/mcp/install and press Enter.

3. At the prompt, type ./mcpDbSwInstall.pl and press Enter.

A communications test to the target database server is performed, and a configurationsummary is presented.

4. If database type is replicated then you will be prompted to select the primary or thesecondary database instance.

• Select the Primary option if you want to install the primary instance of the database.

• Select the Secondary option if you want to install the secondary instance of the database.

5. Select the database installer file when you will be prompted.

Note:

If you receive an error or you are not prompted to select the target database installer zipfile, stop and contact Avaya support.

Depending on the server hardware and the target server receiving the installation, theinstallation process could take up to 15 minutes.

Once the installation is complete, the following message is displayed: mcpDbSwInstall Completed Successfully.

If the message does not display, stop and contact Avaya support.

ResultThe database installation is completed.


Migrating servers



Installing the databaseAbout this taskUse this procedure to install the Avaya Aura® Conferencing database

Procedure1. Log into the primary Element Manager server as ntappadm user.


3. At the prompt, type dbInstall.pl and press Enter.

4. At the Continue with these settings?(Y/N) prompt, type Y and press Enter.

5. Wait until the database installation has completed.

ResultThe Avaya Aura® Conferencing database is installed.


Restoring the database following server replacementBefore you beginIf the backup file you want to restore is stored in a remote location, retrieve the backup file and placeit in the /var/mcp/db/backup folder. If needed, you can restore the database backup from theserver backup.

About this taskUse this task to restore the primary database from a backup file.

Note:This task can cause possible loss of data and interruption of service. Only trained personnelshould perform this procedure.

Procedure1. Log on to the server that hosts the primary database using an account with the DBA role

(ntdbadm).

2. At the prompt, type cd /var/mcp/run/MCP_18.0/mcpdb_0/bin/util and pressEnter.

3. At the prompt, type ./dbRestore.pl <backupName> where <backupName> is the nameof the tar.gz file (with or without the tar.gz extension) and press Enter.

Installing the database



Note:

If mcpdb is not the name of the database (the value for the db.neName parameter fromthe installprops.txt file), replace mcpdb_0 with <your db.neName>_0 in the command.

Ignore all of the compiler warning messages. These messages do not impact service.


Installing Element ManagerAbout this taskUse these steps to install the Element Manager instance.

Procedure1. Log on to the primary Element Manager server using an account with the AA role

(ntappadm).

The primary Element Manager server is the server hosting EM instance 0.


3. At the prompt, type ./emUpgrade.pl and press Enter.

4. At the Continue with these settings?(Y/N)[N]: prompt check the information,type Y and press Enter.

ResultOnce the installation is complete, the following message is displayed:

Upgrade successful.Next stepsRefer back to your checklist for more information about your next task. You should always use yourchecklist for guidance. You should print it out so that you can mark each task as you complete it.

Installing Avaya Media ServerAbout this taskUse this procedure to install Avaya Media Server.

Migrating servers



Procedure1. Log on to the server which hosts Avaya Media Server as a user with the SSA role (for


2. At the prompt, type su – and press Enter.

3. Type the root password, and then press Enter to become the root user.

4. If this server is the primary Element Manager server then go to step 8.

This procedure is for all types of servers. But if this is the primary Element Manager server,skip steps 5-7.

5. At the prompt, type scp ntappadm@<IP address of the primary ElementManager server>:/var/mcp/loads/MCP_MediaServer_18*zip /var/mcp/loads/ and press Enter.

6. At the Are you sure you want to continue connecting (yes/no)? prompt,type yes and press Enter.

7. At the ntappadm@<IP address>'s password prompt, type the ntappadm password forthe primary Element Manager server and press Enter.

8. At the prompt, type mcpMsInstall.pl press Enter.

The install script finds the zipped file. The system will detect more than one zipped file.

9. At the Use this load? (Y/N) [Y] prompt, type y, and press Enter

10. At the Continue installation? (Y/N) prompt, type y and press Enter.

ResultThe Installation completed SUCCESSFULLY message is displayed. The Avaya MediaServer load is now installed.


Restoring a network element instance during serverreplacement

About this taskUse this task to restore a network element instance.


network element type > network element you want to upgrade > NE Maintenance.

Restoring a network element instance during server replacement



2. Click Kill.

3. Click Undeploy.

4. In the navigation pane of Element Manager Console, select Feature Server Elements >network element type > network element you want to upgrade > Instance.

5. In the Instance window, select the row that has a value of the target instance in the IDcolumn.

6. Click Edit.

7. From the Load or Patch box in the Edit Instance dialog box, select the target value, andclick Apply.

8. In the navigation pane of Element Manager Console, select Feature Server Elements >network element type > network element you want to upgrade > NE Maintenance.

9. In the NE Maintenance window, select the row that has a value of the target instance in theID column.

10. Click Deploy.

11. The Maint state changes from None to Deploying, indicating that the deploy operation is inprogress. When the deploy operation is complete, the following state changes occur:


• The Admin state is Offline.

• The link status is Down.

• The Oper state is Unavailable.

12. Click Start.

13. The Maint state changes from None to Starting, indicating that the start operation is inprogress. When the start operation is complete, the following state changes occur:


• The Admin state is Online.

• The link status is Up.

• The Oper state is Active or Hot Standby.

ResultThe network element instance is restored.


Migrating servers



Restoring the recordings following server replacementAbout this taskUse this task to restore your conference recordings.

Procedure1. Configure SSH keys for conference recordings backup. See Configuring SSH keys for

conference recordings backup on page 38.

2. Login to the Element Manager Console.

3. In the navigation pane of Element Manager Console, select Feature Server Elements >Media Server and Clusters > Media Server Clusters > <Cluster to which the mediaserver belongs> > Recording > Restore Maintenance.

The Restore Maintenance window is displayed.

4. Click Start.

The Status column displays the current status of the operation. When the operation iscomplete, the Status column displays Completed.

5. (Optional) If you want to view the detailed status of the backup, click Details.


Installing WebLMAbout this taskUse these steps to install WebLM.

Procedure1. Log to primary Element Manager server as ntappadm.

2. Type weblmInstall.pl.

3. Select weblm load.

4. Type Y to confirm.

Example[ntappadm@server58 install]$ weblmInstall.plThe following webLM application load instances have been found:[1] /var/mcp/weblm_v6.3.3.5.8255_Tomcat_7.0.30.zip[2] /var/mcp/weblm_v6.3.3.5.8255_tomcat_v7.0.30.zipPlease select which weblm load you wish to install [1..2]: 2Do you want to install "WebLM service" (Y/N)?[Y]: Y

Restoring the recordings following server replacement



Installing WebLM service...Installation of WebLM service completed successfully

Verifying the systemYou can verify the successful operation of Avaya Aura® Conferencing by conducting a testconference and testing the various features.

About this taskUse this procedure to verify the system is operating properly for the main location.

ProcedureVerify the following services are operating properly:

• Audio/Video conferencing

• Web conferencing

• Document conversion

• Screen sharing

• Recording

• Recording playback

• Audio/Video in Collaboration Agent

Important:

If the system is not operating correctly, contact your next level of support.

ResultThe system is operating correctly for the main location.


Restoring a Flash Media Gateway (FMG)The Flash Media Gateway (FMG) powers the Audio/Video in Collaboration Agent functionality.

Before you beginIf the backup file you want to restore is stored in a remote location, retrieve that backup file andplace it in the /var/mcp/db/backup folder.

Migrating servers



About this taskUse this procedure to restore Flash Media Gateway (FMG).

Procedure1. Log on to the Element Manager server as a ntappadm user.

2. At the prompt, type scp ntappadm@<IP addressof the Element Managerserver>:/var/mcp/media/avica/* ntappadm@<IP address of the FlashMedia Gateway Server>:/var/mcp/media/avica/ and press Enter.

3. At the Are you sure you want to continue connecting (yes/no)? prompt,type yes and press Enter.

4. At the ntappadm@<IP address>’s password prompt, type the ntappadm password forthe Flash Media Gateway server and press Enter.

5. Log on to the server which hosts Flash Media Gateway as a user with the SSA role (forexample, ntsysadm) through SSH or directly at the server console



8. At the prompt, type cd /var/mcp/media/avica and press Enter.

9. At the prompt, type chmod +x AccWeb-a-b-c.i386.rpm.bin and press Enter.

10. At the prompt, type ./AccWeb-a-b-c.i386.rpm.bin and press Enter.

11. Skip the configuration tool by typing no at the Do you want to run theconfiguration tool now? [yes or no] prompt.

12. Copy the backup package to /var/mcp/fmg/backup directory

13. Execute backup script on each FMG server: /var/mcp/run/fmg/bin/restoreConfig.

14. Select the backup you want to restore.

15. At the prompt, type service red5 start and press Enter.

16. Perform these steps on each FMG server.

17. Verify that Audio/Video in Collaboration Agent is operating properly.

If Audio/Video in Collaboration Agent is not operating properly, contact your next level ofsupport.


Restoring a Flash Media Gateway (FMG)



Re-syncing the database data from the secondaryinstance

Before you beginEnsure that the secondary database is running and there are no replication errors. See Verifyingthat the secondary database is running and there are no replication errors on page 71.

About this taskUse this task to re-sync the database data from the secondary database instance to the primaryone.

This procedure can cause possible loss of data and interruption of service. Only trained personnelshould perform this procedure.

Procedure1. Log on to the server that hosts the secondary database using an account with the DBA role

(ntdbadm).

2. At the prompt, type cd /var/mcp/run/MCP_18.0/mcpdb_1/bin/util and pressEnter.

3. At the prompt, type ./resync.pl and press Enter.

Note:

If mcpdb is not the name of the database (the value for the db.neName parameter fromthe installprops.txt file), replace mcpdb_1 with <your db.neName>_1 in thecommand.

Note:

Ignore all of the compiler warning messages. These messages are notservice impacting.

ResultThe database is restored.


Related LinksVerifying that the secondary database is running and has no replication errors on page 71

Migrating servers



Verifying that the secondary database is running and has noreplication errors

About this taskUse this task to verify that the secondary database instance is running and has no replication errors.

Procedure1. Log in to Element manager Console.

2. In the navigation pane of Element Manager Console, select Feature Server Elements >Database > <Database name> > Monitor.

3. In the Database Instance Monitor window, go to the Replication tab.

4. Make sure that the Incoming Batches and Outgoing Batches have 0 values in the Errorscolumn.

Note:

If the Errors column value is not 0 then you cannot re-sync the database data from thesecondary instance. Instead, you must configure the system manually.


Related LinksRe-syncing the database data from the secondary instance on page 70

Setting up the database replicationIn a redundant deployment, a database on the primary side is replicated to the secondary side. Thisreplication process means that the database is copied so that, in the unlikely event of the primaryserver going offline, Avaya Aura® Conferencing maintains a copy of all conferencing accountinformation.

Previously, you stopped the replication process. Now, in this procedure, you must restart it again, toensure redundancy functionality on the new system.

About this taskUse the following procedure to set up database replication.

Procedure1. Log on to the server hosting Element Manager instance 0 as ntappadm or an account with

the AA role.

Setting up the database replication



2. Type cd /var/mcp/install and press Enter.

3. Type ./setupDBReplication.pl and press Enter.

The system displays the following information:Deploying files to xxx.xxx.xxx.xxx...Deploying files to the Secondary DBDeploying files to xxx.xxx.xxx.xxx...DB Operation Completed.Resync from primary DB to secondary DB.This will take a while, please be patient and wait ... setupDBReplication.pl completed successfully

Note:

If this information is not displayed, stop and contact your next level of support.

4. In the Element Manager Console, verify that the alarms No connection to DB instance clearwithin a couple of minutes.

ResultThe database replication is set up.


Related LinksMigrating from bare metal to VM for a medium redundant deployment on page 83

Migrating servers



Chapter 3: Migrating from a bare metalsolution to a virtualized solution

IntroductionThis section describes how to migrate an Avaya Aura® Conferencing (AAC) bare metal system to aVMware host as a vAAC Virtual Machine (VM) in Release 8.0.

Before migrating the system, you must identify the deployment model of the system as well as thesystem component network configuration information. Network configuration information includes IP,FQDN, gateway, subnet details, and so on. The same network configuration is used for the vAACVM on VMware hosts.

Avaya supports the following deployment models for migration from an AAC bare metal system to avAAC Virtual Machine:

• Medium simplex

• Medium redundant

PrerequisitesThe following prerequisites apply to medium simplex and medium redundant deployment models:

• You must have the same software on the bare metal Avaya Aura® Conferencing (AAC) systemand the vAAC VM.

• You must use the same configuration details for the bare metal Avaya Aura® Conferencing(AAC) system and the vAAC VM. In other words, you will reuse the same IP, FQDN, gatewayIP, subnet, and so on.

• You must factor some down time for your Avaya Aura® Conferencing system.

• You must download the vAAC Platform OVA file to the local PC for the deployment.

• You must upload the Platform ISO file to the VMware Host shared storage:

- The ISO has to be same as the bare metal AAC system.

- The ISO has to be uploaded to the VMware host shared storage which must be accessiblefor the deployed VM.



Migrating from bare metal to VM for a medium simplexdeployment

Table 1: Checklist

Number Task References NotesBackup the bare metal Avaya Aura® Conferencing system components and shutdown the bare metal

system.1 On the bare metal Avaya Aura®

Conferencing system, backup the AvayaMedia Server (MS).

Backing up the Avayamedia servers onpage 36

2 On the bare metal Avaya Aura®

Conferencing system, backup thedatabase.

Backing up thedatabase on page 79


Conferencing system, backup the FlashMedia Gateway (FMG).

See the Backup andRestore tab in the AAC-AViCA-Intelligent-Workbook, which isavailable from https://support.avaya.com/

Backing up the flashmedia gateways onpage 80


Conferencing system, backup theconference recordings.

Backing up conferencerecordings on page 37


Conferencing system, backup the AvayaAura® Conferencing server

Note:

You must use the remote method.(bkupSvr -remote)

Backing up theservers on page 40

6 Shutdown the bare metal Avaya Aura®

Conferencing server

Deploy the vAAC platform VM and restore the platform data7 Deploy vAAC Platform VM (do not Power

On).

8 Configure the Avaya Aura® Conferencingplatform ISO access from the VM and theVM Boot BIOS Setup

1. In vSphere Client, select thedeployed VM, right-click on it andselect Edit Settings...

Migrating from a bare metal solution to a virtualized solution



Number Task References Notes2. In the Edit Settings popup window,

display the Hardware tab and selectCD/DVD drive 1.

3. In the Device Type panel, selectDatastore ISO File. ClickBrowse ....

4. Select the Platform ISO file from theshared storage and click Open.

5. In the Edit Settings popup window, inthe Device Status panel, checkConnect at power on.

6. From the Edit Settings popupwindow, navigate to Options >Advanced > Boot Options.

7. In the Force BIOS Setup panel,check The next time the virtualmachine boots, force entry intothe BIOS setup panel.

8. Click OK on the Edit Settings popupwindow.

9 Start the VM and configure the VM BIOS

1. Power on the VM.

2. Right click the VM and select OpenConsole.

3. In the BIOS Setup Utility screen,press the right arrow key to the Boottab.

4. Move down the arrow key to CD-ROM Drive and enter +.

5. Press the right arrow key to the Exittab.

6. Save the change.

The Initial platform ISO installationprocess screen displays.

10 Restore the Platform using the remotebackup option.

Restoring the platformfrom a remote backupserver on page 45

11 After the Platform has restored andconfigured successfully, power off theVM.

Migrating from bare metal to VM for a medium simplex deployment



Number Task References Notes12 Reconfigure the VM ISO access and the

VM Boot BIOS Setup.


2. In the Edit Settings popup window,display the Hardware tab and selectCD/DVD drive 1.

3. In the Edit Settings popup window, inthe Hardware tab, in the DeviceStatus panel, uncheck Connect atpower on.




13 Power on the VM and reconfigure the VMBIOS

1. Power on the VM.

2. Right click on the VM and selectOpen Console.


4. Move down the arrow key to CD-ROM Drive and enter - .


6. Save the change.

The VM boots up normally.

14 Install the VMware tools package Manually install theVMware toolspackage on page 80

Restore and start up vAAC components




Number Task References Notes15 Configure the remote backup

parameters.Configuring remotebackup parameters onpage 42

16 Restore theAvaya Aura® Conferencingserver by executing the commandrestoreSvr -remote as a ntsysadmuser.

Restoring an AvayaAura® Conferencingserver on page 60

17 Install the database software byexecuting the commandmcpDbSwInstall.pl in /var/mcp/install as a ntappadm user.


18 Install the database by executing thecommand dbInstall.plin /var/mcp/install as a ntappadmuser.


19 Restore the database by executing thecommand /var/mcp/run/MCP_18.0/mcpdb_0/bin/util/dbRestore.pl<db backup file name> as thentdbadm user.


20 Install the Avaya Media Server (MS)software by executing the commandmcpMsInstall.pl as a root user.


21 Deploy the Element Manager byexecuting the command emDeploy.plin /var/mcp/install as a ntappadmuser.

22 Starting the Element Manager byexecuting the command /var/mcp/install/emStart.pl as a ntappadmuser.

23 Kill, deploy, and start each of the networkelements from the Element ManagerConsole.

Killing a network elementinstance on page 81

Deploying a NetworkElement instance onpage 82

Starting a NetworkElement instance onpage 83

24 Restore the recordings:

1. Configure the recording backupserver but do not use the existingSSH key from the restore process.

Configuring SSH keys forconference recordingsbackup on page 38




Number Task References Notes2. Login to the Element Manager

Console and navigate to MediaServers and Clusters > MediaServer Clusters >MediaServerCluster1 >Recording > Restore >Maintenance > Start.

25 Install the FMG software by following thesteps in the Flash Media Gateway (FMG)worksheet (AViCA I&C1–FMGInstallation).

1. Execute the command /var/mcp/media/avica/AccWeb-3.1_AAC-NIGHTLY.2014xxxx#xxx.i386.rpm.bin asa root user.

2. At the Do you agree to theabove license terms? [yesor no] prompt, enter yes.

3. At the Do you want to run theconfiguration tool now?[yes or no] prompt, enter no.

Note:

You only need to run theconfiguration tool when you areinstalling the FMG.

See the AViCA I&C > 1–FMG Installation tab inthe AAC-AViCA-Intelligent-Workbook,which is available from https://support.avaya.com/

Restoring the FlashMedia Gateway onpage 68

26 Restore the FMG:

1. Copy the backup file from the remotesite to /var/mcp/fmg/backup/.

2. Login to the FMG server as a rootuser.

3. Run thecommand /var/mcp/run/fmg/bin/restoreConfig and select thebackup you want to restore.

4. Execute the command servicered5 start to start the service.

5. Verify that the /var/mcp/media/prov_pa_installs/otv/AccWebCustomerConfig.xml fileis the proper configuration file. Ifrequired, copy the backup fileAccWebCustomerConfig.xml





Number Task References Notesfrom the remote site to /var/mcp/media/prov_pa_installs/otv/.

Note:

If the FMG is not working properly,select the FMG and click theRestart button.

Related LinksBacking up the database on page 79Backing up the Flash Media Gateway(s) on page 80Manually installing the VMware tools package on page 80Killing a network element instance on page 81Deploying a network element instance on page 82Starting a Network Element instance on page 83

Backing up the databaseNote:

The default name for the database is mcpdb. The example commands in this procedure usemcpdb for the database name. If mcpdb is NOT the name of the database (the value for thedb.neName parameter from the installprops.txt file), replace mcpdb_0 with your<db.neName>_0 in the command.

About this taskUse this procedure to backup the database.

Procedure1. Log on to the primary database server as a user with the DBA role.

2. At the prompt type cd /var/mcp/run/MCP_18.0/mcpdb_0/bin/util and press Enter.

3. At the prompt type ./dbBackup.pl <BackupFileName> and press Enter.

ResultThe backup file is created and stored in the /var/mcp/db/backup/latest folder. The backupfile name is <BackupFileName>.tar.gz. The previous manual backup file is moved tothe /var/mcp/db/backup folder. If the/var/mcp/db/backup/latest folder contains ascheduled automatic backup file, the automatic backup file is moved to the /var/mcp/db/backup/AUTO_history folder.





Related LinksMigrating from bare metal to VM for a medium simplex deployment on page 74

Backing up the Flash Media Gateway(s)About this taskUse this procedure to backup Flash Media Gateway (FMG). The FMG is the server which enablesthe Audio/Video in Collaboration Agent functionality for Avaya Aura® Conferencing. The Audio/Videoin Collaboration Agent feature enables users to receive audio, video, and data content through asingle device.

Procedure1. Log on to the server which hosts Flash Media Gateway as a user with the SSA role (for




4. At the prompt, type /opt/Avaya/AccWeb/bin/backupConfig and press Enter.

A backup file is created and located at /var/mcp/fmg/backup directory.

5. Copy the Flash Media Gateway backup file to a remote backup server.

ResultThe Flash Media Gateway is backed up.



Manually installing the VMware tools packageBefore you beginThe deployed vAAC VM must be powered on and running. It must have access to the currentVMware host’s datastore.

About this taskUse this task to manually install a compatible VMware tools package to the deployed vAAC VM.

Procedure1. In vSphere Client, select the deployed VM, right-click on it and click Edit Settings...




2. In the Edit Settings popup window, on the Hardware tab, select CD/DVD drive 1.

3. From the Device Type panel, select Datastore ISO File and click Browse...

4. On the Browse dialog, navigate to Datastores > vmimages > tools-isoimages > linux.iso.Click Open on the linux.iso file.

5. In the Edit Settings popup window, in the Device Status panel, select Connected.

6. Click OK.

7. Login to SSH and switch user to the root user (su -)

8. Execute mount /dev/cdrom /mnt/cdrom.

9. Execute cd /tmp.

10. Execute tar zxf /mnt/cdrom/VMwareTools-xx.xx.xx-xxxxxxx.tar.gz.

11. Execute umount /mnt/cdrom.

12. Execute cd vmware-tools-distrib.

13. Execute ./vmware-install.pl.

14. Follow the VWware-Tools installation prompts using all of the default values.

15. After the VMware-Tools has installed successfully, execute reboot to restart the server.



Killing a network element instanceAbout this taskUse this procedure to kill a network element instance.

Procedure1. Log on to the Element Manager Console.

2. In the navigation pane of Element Manager Console, select Feature Server Elements ><network element type> > <network element instance you want to kill> > NEMaintenance.


4. Click Kill.




The Maint state changes from None to Killing, indicating that the kill operation is inprogress. When the kill operation is complete, the following state changes occur:


• The Admin state changes from Online to Offline.


ResultThe network element instance is up and running.



Deploying a network element instanceAbout this taskUse this procedure to deploy a network element instance.


<Network Element type> > <Network Element instance you want to deploy > NEMaintenance.

2. In the Maintenance dialog box, select the row that has a value of the target instance in the IDcolumn.

3. Click Deploy.

The Maint state changes from None to Deploying, indicating that the deploy operation is inprogress. When the deploy operation is complete, the Maint state changes back to None,and the Admin state changes from Configured to Offline.


ResultThe Network Element instance is deployed.


Related LinksMigrating from bare metal to VM for a medium simplex deployment on page 74Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151




Starting a Network Element instanceAbout this taskUse this procedure to start a Network Element instance.

Procedure1. Log on to Element Manager Console.

2. In the navigation pane of Element Manager Console, select Feature Server Elements><Network Element type> > <Network Element instance you want to start> > NEMaintenance.


4. Click Start.

The Maint state changes from “None” to “Starting,” indicating that the start operation is inprogress. When the start operation is complete, the following state changes occur:

• The Maint state changes back to “None.”

• The Admin state changes from “Offline” to “Online.”

• The Link state changes from “Down” to “Up.”

• The Oper state changes from “Unavailable” to either “Active” or “Hot Standby,” based onthe instance of the component.

ResultThe Network Element instance is up and running.


Migrating from bare metal to VM for a medium redundantdeployment

Table 2: Checklist

Number Task References NotesBackup the bare metal Avaya Aura® Conferencing system components and shutdown the bare metal

system.1 On the primary server bare metal Avaya

Aura® Conferencing system, backup theAvaya Media Server (MS).

Backing up the Avayamedia servers onpage 36

Migrating from bare metal to VM for a medium redundant deployment



Number Task References Notes2 On the primary server bare metal Avaya

Aura® Conferencing system, backup thedatabase.

Note:

This step does not apply for mediumredundant secondary serverdeployment.

Backing up thedatabase on page 79

3 On the primary server bare metal AvayaAura® Conferencing system, backup theFlash Media Gateway (FMG).

See the Backup andRestore tab in the AAC-AViCA-Intelligent-Workbook, which isavailable from https://support.avaya.com/

Backing up the flashmedia gateways onpage 80

4 On the primary server bare metal AvayaAura® Conferencing system, backup theconference recordings.

Backing up conferencerecordings on page 37

5 On the primary server bare metal AvayaAura® Conferencing system, backup theAvaya Aura® Conferencing server

Note:

You must use the remote method.(bkupSvr -remote)

Backing up theservers on page 40

6 Repeat steps 1–5 for the secondaryserver.


Conferencing secondary server


Conferencing primary server

Deploy the vAAC platform VM and restore the platform data9 On the primary VM, deploy vAAC

Platform VM (do not Power On).

10 On the primary VM:

Configure the Avaya Aura® Conferencingplatform ISO access from the VM and theVM Boot BIOS Setup.





Number Task References Notes2. In the Edit Settings popup window,

display the Hardware tab and selectCD/DVD drive 1.

3. In the Device Type panel, selectDatastore ISO File. ClickBrowse ....

4. Select the Platform ISO file from theshared storage and click Open.

5. In the Edit Settings popup window, inthe Device Status panel, checkConnect at power on.





Start the VM and configure the VM BIOS.

1. Power on the VM.

2. Right click the VM and select OpenConsole.


4. Move down the arrow key to CD-ROM Drive and enter +.


6. Save the change.

The Initial platform ISO installationprocess screen displays.


Restore the Platform using the remotebackup option.

Restoring the platformfrom a remote backupserver on page 45





Number Task References NotesAfter the Platform has restored andconfigured successfully, power off theVM.


Reconfigure the VM ISO access and theVM Boot BIOS Setup.


2. In the Edit Settings popup window,display the Hardware tab and selectCD/DVD drive 1.

3. In the Edit Settings popup window, inthe Hardware tab, in the DeviceStatus panel, uncheck Connect atpower on.





Power on the VM and reconfigure the VMBIOS

1. Power on the VM.

2. Right click on the VM and selectOpen Console.


4. Move down the arrow key to CD-ROM Drive and enter - .


6. Save the change.

The VM boots up normally.




Number Task References Notes16 On the primary VM:

Install the VMware tools package

Manually install theVMware toolspackage on page 80

17 Repeat steps 10–16 for the secondaryVM.

Restore and start up vAAC components18 Configure the remote backup parameters

on the primary.Configuring remotebackup parameters onpage 42

19 Configure the remote backup parameterson the secondary.

Configuring remotebackup parameters onpage 42

20 On the primary, restore theAvaya Aura®

Conferencing server by executing thecommand restoreSvr -remote as antsysadm user.


21 On the secondary, restore theAvayaAura® Conferencing server by executingthe command restoreSvr -remote asa ntsysadm user.


22 Install the primary database software onthe primary by executing the commandmcpDbSwInstall.pl in /var/mcp/install as a ntappadm user.


23 Change the database type to SINGLE onthe primary, by executing the commandpopulateInstallpropsFile.plin /var/mcp/install as a ntappadmuser.

Setting the database typeto single on page 90

24 Install the database on the primary byexecuting the command dbInstall.plin /var/mcp/install as a ntappadmuser.


25 Restore the database on the primary byexecuting thecommand /var/mcp/run/MCP_18.0/mcpdb_0/bin/util/dbRestore.pl<db backup file name> as thentdbadm user.


26 Change the database type toREPLICATED on the primary, byexecuting the commandpopulateInstallpropsFile.pl

Setting the database typeto replicated onpage 91




Number Task References Notesin /var/mcp/install as a ntappadmuser.

27 Install the secondary database softwareon the primary by executing thecommand mcpDbSwInstall.plin /var/mcp/install as a ntappadmuser.


28 Replicate the database from the primaryto the secondary by executing thiscommand on the PrimarysetupDBReplication.plin /var/mcp/install as ntappadm.

Wait until database replication isconfigured.


29 Install the Avaya Media Server (MS)software on the primary by executing thecommand mcpMsInstall.pl as aroot user.


30 Install the Avaya Media Server (MS)software on the secondary by executingthe command mcpMsInstall.pl as aroot user.


31 Deploy the Element Manager on theprimary by executing the commandemDeploy.pl in /var/mcp/installas a ntappadm user.

32 Starting the Element Manager on theprimary by executing thecommand /var/mcp/install/emStart.pl as a ntappadm user.

33 Kill, deploy, and start each of the networkelements from the Element ManagerConsole.

Killing a network elementinstance on page 81

Deploying a NetworkElement instance onpage 82

Starting a NetworkElement instance onpage 83

34 Restore the recordings:

1. Configure the recording backupserver but do not use the existingSSH key from the restore process.

2. Login to the Element ManagerConsole and navigate to Media

Configuring SSH keys forconference recordingsbackup on page 38




Number Task References NotesServers and Clusters > MediaServer Clusters >MediaServerCluster1 >Recording > Restore >Maintenance > Start.


Install the FMG software by following thesteps in the Flash Media Gateway (FMG)worksheet (AViCA I&C1–FMGInstallation).

1. Execute the command /var/mcp/media/avica/AccWeb-3.1_AAC-NIGHTLY.2014xxxx#xxx.i386.rpm.bin asa root user.

2. At the Do you agree to theabove license terms? [yesor no] prompt, enter yes.

3. At the Do you want to run theconfiguration tool now?[yes or no] prompt, enter no.

Note:

You only need to run theconfiguration tool when you areinstalling the FMG.

See the AViCA I&C > 1–FMG Installation tab inthe AAC-AViCA-Intelligent-Workbook,which is available from https://support.avaya.com/



Restore the FMG:

1. Copy the backup file from the remotesite to /var/mcp/fmg/backup/.

2. Login to the FMG server as a rootuser.

3. Run thecommand /var/mcp/run/fmg/bin/restoreConfig and select thebackup you want to restore.

4. Execute the command servicered5 start to start the service.

5. Verify that the /var/mcp/media/prov_pa_installs/otv/AccWebCustomerConfig.xml fileis the proper configuration file. Ifrequired, copy the backup fileAccWebCustomerConfig.xml





Number Task References Notesfrom the remote site to /var/mcp/media/prov_pa_installs/otv/.

Note:

If the FMG is not working properly,select the FMG and click theRestart button.

37 Repeat steps 35–36 for the secondary.

Related LinksSetting the database type to single on page 90Setting the database type to replicated on page 91Setting up the database replication on page 71

Setting the database type to singleIn a redundant deployment, a database on the primary side is replicated to the secondary side. Thisreplication process means that the database is copied so that, in the unlikely event of the primaryserver going offline, Avaya Aura® Conferencing maintains a copy of all conferencing accountinformation.

This task temporarily disables the replication process during the upgrade. At the end of the upgrade,you must restart the process by setting the database type to REPLICATED.

About this taskUse this procedure to set the database type to single.


2. At the prompt, type populateInstallpropsFile.pl and press Enter.

3. At all the prompts with the exception of Database Type (SINGLE/REPLICATED)?, retainthe existing values.

4. At the Database Type (SINGLE/REPLICATED)? prompt, type SINGLE and press Enter.

ResultThe database type is set to single.






Setting the database type to replicatedIn a redundant deployment, a database on the primary side is replicated to the secondary side. Thisreplication process means that the database is copied so that, in the unlikely event of the primaryserver going offline, Avaya Aura® Conferencing maintains a copy of all conferencing accountinformation.

About this taskUse this procedure to set the database type to single.



3. At all the prompts with the exception of Database Type (SINGLE/REPLICATED)?, retainthe existing values or enter values that were used during initial Avaya Aura® Conferencinginstallation.

4. At the Database Type (SINGLE/REPLICATED)? prompt, type REPLICATED and pressEnter.

ResultThe database type is set to replicated.



Setting up the database replicationIn a redundant deployment, a database on the primary side is replicated to the secondary side. Thisreplication process means that the database is copied so that, in the unlikely event of the primaryserver going offline, Avaya Aura® Conferencing maintains a copy of all conferencing accountinformation.

Previously, you stopped the replication process. Now, in this procedure, you must restart it again, toensure redundancy functionality on the new system.

About this taskUse the following procedure to set up database replication.




Procedure1. Log on to the server hosting Element Manager instance 0 as ntappadm or an account with

the AA role.

2. Type cd /var/mcp/install and press Enter.

3. Type ./setupDBReplication.pl and press Enter.

The system displays the following information:Deploying files to xxx.xxx.xxx.xxx...Deploying files to the Secondary DBDeploying files to xxx.xxx.xxx.xxx...DB Operation Completed.Resync from primary DB to secondary DB.This will take a while, please be patient and wait ... setupDBReplication.pl completed successfully

Note:

If this information is not displayed, stop and contact your next level of support.

4. In the Element Manager Console, verify that the alarms No connection to DB instance clearwithin a couple of minutes.

ResultThe database replication is set up.






Chapter 4: Migrating from a turnkeysolution to an Aura® solution

Migrating from Avaya Aura® Conferencing turnkey toAvaya Aura® Conferencing with the full Avaya Aura®

platformUse the following checklist to migrate your deployment from an Avaya Aura® Conferencing turnkeysolution to an Avaya Aura® Conferencing solution that is integrated with the Avaya Aura® platform,which consists of Avaya Aura® System Platform and Avaya Aura® System Manager.


1 Disable the Access Control List(ACL) rules on Avaya Aura®

Conferencing servers if they areused.

Configuring the access controllist on page 99

2 Add Avaya Aura® System Managerto the Element Manager GUI.

Adding System Manager to theElement Manager GUI onpage 96

3 Add Avaya Aura® SessionManager to the Element ManagerGUI.

Adding Session Manager to theElement Manager GUI onpage 97

4 Change the WebLM location to useAvaya Aura® System Manager.

Changing the WebLM location touse System Manager on page 98

5 Configure Avaya Aura® SessionManager as the bandwidthmanagement ASM for theapplication server

Configuring Session Manager asthe bandwidth management ASMfor the application server onpage 98

6 Stop all network element instancesexcept Element Manager

Stopping a network elementinstance on page 43

7 Create network elementcertificates signed by Avaya Aura®

System Manager.

See Creating Network Elementcertificates signed by the SystemManager on page 116.

8 Assign new certificates to allnetwork element instances.

Assigning a new certificate to theElement Manager on page 118




Assigning a new certificate to theProvisioning Manager onpage 119

Assigning a new certificate to theCollaboration Agent Manager onpage 120

Assigning a new certificate to theApplication Server on page 121

Assigning a new certificate to theAvaya Media Server on page 122

Assigning a new certificate to theWeb Conferencing Server onpage 123

Assigning a new certificate to theWeb Conferencing ManagementServer on page 124

Assigning a new certificate to theDCS on page 125

9 Remove all of the old certificateson the Turnkey solution.

Removing all the old certificates onTurnkey on page 136

10 Stop Element Manager Stopping an Element ManagerInstance on page 44

11 Restart all network elementinstances.

Stopping a network elementinstance on page 43

Stopping an Element ManagerInstance on page 44

Starting a network elementinstance on page 156

Starting an Element Managerinstance from the serverconsole on page 125

12 Configure single sign-on forElement Manager Console andProvisioning Client.

Configuring single sign-on onpage 126

13 Configure ACL rules on the AvayaAura® Conferencing server toreflect network topology changes ifthey were used.

Configuring the access controllist on page 99

14 Create a SIP entity for AvayaAura® Conferencing on AvayaAura® System Manager.

Configuring the route to AvayaAura Conferencing on SystemManager on page 130

Migrating from a turnkey solution to an Aura® solution




15 Create a certificate for the FlashMedia Gateway (FMG) IP addressthat is signed by Avaya Aura®

System Manager.

Creating a System Manager signedcertificate for the FMG IPaddress on page 133

16 Configure a SIP TLS connectionfrom the Flash Media Gateway(FMG) to the Avaya Aura® SessionManager.

Configuring a secure SIP TLSconnection from the FMG toSession Manager on page 134

17 In Provisioning Client, enableAllow bandwidth managementand disable User PasswordOwned Locally.

Changing the system defaultsettings to use Avaya AuraConferencing (AAC) on page 135

18 Remove the dialing rules inProvisioning Client.

Removing the dialing rules inProvisioning Client on page 135

19 Remove all SIP entities for PBXs inElement Manager.

Removing all SIP entities for PBXsin Element Manager on page 136

20 Verify that the Avaya Aura®

Conferencing system is operatingcorrectly.

Verifying the system on page 68

Related LinksAdding Avaya Aura System Manager to the Element Manager GUI on page 96Adding Avaya Aura Session Manager to the Element Manager GUI on page 97Changing the WebLM location to use Avaya Aura System Manager on page 98Configuring Session Manager as the bandwidth management ASM for the application server onpage 98Configuring the access control list (ACL) on page 99Guidelines for certificate configuration on page 114Obtaining enrollment password from System Manager on page 116Creating Network Element certificates signed by System Manager on page 116Assigning a new certificate to the Element Manager on page 118Assigning a new certificate to the Provisioning Manager on page 119Assigning a new certificate to the Collaboration Agent Manager on page 120Assigning a new certificate to the Application Server on page 121Assigning a new certificate to the Avaya Media Server on page 122Assigning a new certificate to the Web Conferencing Server on page 123Assigning a new certificate to the Web Conferencing Management Server on page 124Assigning a new certificate to the DCS on page 125Starting an Element Manager instance from the server console on page 125Configuring the route to Avaya Aura Conferencing on System Manager on page 130

Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform



Creating a System Manager- signed certificate for the Flash Media Gateway IP address onpage 133Configuring a secure SIP TLS connection from the Flash Media Gateway to Avaya Aura SessionManager on page 134Changing the system default settings to use Avaya Aura Conferencing (AAC) on page 135Removing the dialing rules in Provisioning Client on page 135Removing all SIP entities for PBXs in Element Manager on page 136Removing all the old certificates on Turnkey on page 136

Adding Avaya Aura® System Manager to the Element ManagerGUI

About this taskUse this task to add and configure System Manager in the Element Manager GUI.

Procedure1. In the navigation pane of the Element Manager Console, select Addresses.

2. In the Addresses window, click Add (+).

3. In the Add IPv4 Address dialog box, enter the logical name SMGRExtOAMSvcAddr and IPaddress of the System Manager that is being used.

4. Click Apply.


6. In the External Nodes window, click Add (+).

7. In the Add External Node dialog box, enter the logical name SMGRExtNode and select IPaddress you specified in Step 3.

8. Click Apply.

9. In the navigation pane of Element Manager Console, select Avaya Aura Core > SystemManager.

10. In the System Manager window, click Add (+).

11. In the Add System Manager dialog box, complete the following fields:

• Short Name

• Long Name

• Node: Select the external node you specified in Step 7.

• Port

• FQDN

12. Click Apply.





Related LinksMigrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full AvayaAura platform on page 93

Adding Avaya Aura® Session Manager to the Element ManagerGUI

About this taskUse this task to add and configure Session Manager in the Element Manager GUI.

Procedure1. In the navigation pane of the Element Manager Console, select Addresses.


3. In the Add IPv4 Address dialog box, enter the logical name ASM1ExtOAMSvcAddr and IPaddress of the Session Manager that is being used.

4. Click Apply.


6. In the External Nodes window, click Add (+).

7. In the Add External Node dialog box, enter the logical name ASM1ExtNode and select IPaddress you specified in Step 3.

8. Click Apply.

9. In the navigation pane of Element Manager Console, select Avaya Aura Core > SessionManager.

10. In the Session Manager window, click Add (+).

11. In the Add Session Manager dialog box, complete the following fields:

• Short Name

• Long Name

• Trusted

• ExemptDosProtection

• Node: Select the external node that you specified in Step 7.

• Select one of these options:

- Enable SIP TCP: Select this check box to enable SIP TCP.

- Enable SIP TLS: Select this check box to enable SIP TLS.




12. Click Apply.



Changing the WebLM location to use Avaya Aura® SystemManager

About this taskUse this task to enable the System Manager WebLM.

Procedure1. In the navigation pane of the Element Manager Console, select Licensing > WebLM

Location.

2. In the WebLM Location dialog box, select System Manager (SMGRExtNode) as the WebLMinstance location.

3. Click OK.



Configuring Session Manager as the bandwidth managementASM for the application server

About this taskUse this task to configure Session Manager as the bandwidth management ASM for the applicationserver.

Procedure1. In the navigation pane of the Element Manager Console, select Feature Server Elements >

Application Servers > <AS NE Instance> > Bandwidth Management ASM.




2. In the <AS NE Instance> Bandwidth Management ASM dialog box, select the SessionManager you want to use as the primary Session Manager.

3. If you want to use two Session Managers, select the second Session Manager as theSecondary Session Manager.

4. Click Apply.



Configuring the access control list (ACL)There are two parts to the ACL configuration: internal ACL rules and external ACL rules. Theinternal rules pertain to connections that are used within the system and are auto-generated fromthe Avaya Aura® Conferencing database. The external rules pertain to restricting external access toAvaya Aura® Conferencing. You must configure the external rules manually. The following sectionsdescribe how to configure both internal and external ACL rules.

Note:

You must complete all tasks provided in Configuring internal ACL rules on page 99 and Configuring external ACL rules on page 101 before the ACL configuration is complete. Theinternal ACL rules will be applied only when the external ACL rules are configured andcommitted.

Related LinksMigrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full AvayaAura platform on page 93Configuring internal ACL rules on page 99Configuring external ACL rules on page 101

Configuring internal ACL rulesAbout this taskUse the following procedure to configure internal ACL rules.

Procedure1. Generate an internal ACL configuration file. See Generating an internal ACL configuration

file on page 100.

2. Install an internal ACL configuration file on the primary Element Manager server. See Installing an internal ACL configuration file on the primary Element Manager server onpage 100.




3. Install an internal ACL configuration file on all other servers. See Installing an internal ACLconfiguration file on all other servers on page 101.

Related LinksConfiguring the access control list (ACL) on page 99Generating an internal ACL configuration file on page 100Installing an internal ACL configuration file on the primary Element Manager server on page 100Installing an internal ACL configuration file on all other servers on page 101

Generating an internal ACL configuration fileBefore you beginYou must be able to log onto the primary Element Manager server a user with the ApplicationAdministrator (AA) role.

About this taskUse the following procedure to generate an internal ACL configuration file.

Procedure1. Log onto the primary Element Manager server as a user with the AA role.

2. At the command prompt, enter cd /var/mcp/install and press Enter.

3. Enter mcpGenIntACLConfig.pl and press Enter.

The internal ACL configuration file has now been generated and resides on the primaryElement Manager server. You must now install the internal ACL configuration file on allservers in the system (including the primary Element Manager server).

Related LinksConfiguring internal ACL rules on page 99

Installing an internal ACL configuration file on the primary Element Manager serverBefore you beginYou must be able to log onto the primary Element Manager server as a user the System SecurityAdministrator (SSA) role.

About this taskUse the following procedure to install an internal ACL configuration file on the primary ElementManager server.

Procedure1. Log onto the primary Element Manager server as a user with the SSA role.

2. At the command prompt, enter mcpInstIntACLConf –copy and press Enter.





Installing an internal ACL configuration file on all other serversBefore you beginYou must be able to log onto the primary Element Manager server a user with the System SecurityAdministrator (SSA) role.

About this taskUse the following procedure to install an internal ACL configuration file on all other servers.

If your deployment supports integrated audio and video, this includes the Flash Media Gateway(FMG) server. For more information on integrated audio and video, see Deploying integrated audioand video.

Procedure1. Log onto the server as a user with the SSA role.

2. At the command prompt, enter mcpInstIntACLConf and press Enter.

3. At the prompt Remote server IP address, enter the primary Element Manager serverinternal OAM IP address and press Enter.

4. At the prompt SFTP user id, enter the SSA user name defined on the primary ElementManager server and press Enter.

5. At the prompt SFTP password, enter the SSA password and press Enter.

6. At the prompt Please retype the password to confirm, re-enter the SSA passwordand press Enter.

7. At the prompt Confirm (Y or N), enter y and press Enter.

Note:

If you receive an error message that the remote host identification has changed, see Fixing remote host SSH keys on page 187 to fix the problem. Once you fix the keys,retry the script on this server.

8. Repeat Steps 1 through 7 on all remaining servers in the system.

Note:

The internal ACL rules are applied to the system only after you commit the ACL rules viathe iptcfg tool. See Importing an external ACL configuration file on page 103.


Configuring external ACL rulesAbout this taskThere are multiple methods available for configuring external ACL rules. The iptcfg tool provides aninteractive menu that enables you to

• configure the settings for an individual node




• configure the settings for a port• configure the DSCP settings• import configuration files

The import files used in this section were auto-generated after the platform was installed. If theimport file want not generated automatically, you must create that file manually.

When external ACL rules are committed via the iptcfg tool, the internal ACL rules file (previouslyinstalled) is used by the iptcfg tool to create firewall rules for the internal nodes. No further action isrequired to include the internal ACL rules.

Use the following procedure to configure external ACL rules.

Procedure1. If the Avaya Media Server is deployed on the target server, prepare the Avaya Media Server.

See Preparing the Avaya Media Server on page 102.

2. Perform one of the following steps:

• Create a configuration file and then import it using the iptcfg tool. See Importing anexternal ACL configuration file on page 103.

• Configure the rules manually using the iptcfg tool. See Configuring external ACL rulesmanually (using the iptcfg tool) on page 105.

3. Verify the ACL configuration. See Verifying the ACL configuration on page 108.

Related LinksConfiguring the access control list (ACL) on page 99Preparing the Avaya Media Server on page 102Importing an external ACL configuration file on page 103Configuring external ACL rules manually (using the iptcfg tool) on page 105Verifying the ACL configuration on page 108External ACL configuration settings on page 108Example of import.dat file on page 113

Preparing the Avaya Media ServerBefore you begin

• You must be able to log onto the server as a user with the System Security Administrator(SSA) role.

• You must know the root password.

About this taskPerform this procedure on all servers where the Avaya Media Server is deployed, regardless of thelayout type (that is, SMB, medium, or lrage)).


2. At the prompt, enter su - and press Enter.




3. At the prompt password, enter the root password, and press Enter.

4. Enter aacconfiginstall.pl and press Enter.

The following message is displayed:Install AAC configuration/var/mcp/ma/MAS/bin/chmodplat.sh/var/mcp/ma/MAS/bin/dscpconfig.sh install/var/mcp/ma/MAS/bin/dscpconfig.sh install

Related LinksConfiguring external ACL rules on page 101

Importing an external ACL configuration fileBefore you beginYou must be able to log onto the server as a user with the System Security Administrator (SSA)role.

About this taskUse the following procedure to import an external ACL configuration file. The import files are serverspecific. As a result, each server in the Avaya Aura® Conferencing system will require its own importfile containing IP addresses that are specific to that server. The Element Manager server import fileand the Avaya Media Server import file differ slightly.

The Avaya Media Server ACL import file has additional syntax that is not present in the ElementManager Server import file. For more information, see the Avaya Media Server-specific ACL importexample file, which is located in the directory /opt/mcp/ipt/example on an Avaya MediaServer. You must use the root login to access this directory.

You can view an example of an Element Manager server ACL configuration file with instructions onhow to configure the file. This example file is located in the directory /opt/mcp/ipt/example onthe Avaya Aura® Conferencing server. You must use the root login to access this directory.

Note:Since the Element Manager server import file and the Avaya Media Server import file differslightly, it is important that you use the appropriate example file for each server type.

The following are examples of external trusted nodes that you may need to configure in the importfile:

• remote syslog server• remote NTP server• administrator PCs• DNS servers

To see an example of an external ACL configuration file, see Example of import.dat file onpage 113.

To see the lists of trusted nodes, trusted ports, and DSCP settings that you must configure on eachserver according to your deployment layout, see External ACL configuration settings on page 108.




Note:You must perform this procedure on all servers in the Avaya Aura® Conferencing system.


2. At the prompt, enter su - and press Enter.

3. At the password prompt, enter the root password, and press Enter.

4. Create an ACL import file based on a server-specific ACL import example file (import.dat).

The example file of an Element Manager server ACL configuration file is located in thedirectory /opt/mcp/ipt/example on the Avaya Aura® Conferencing server.

The Avaya Media Server-specific ACL import example file is located in thedirectory /opt/mcp/ipt/example on an Avaya Media Server.

Note:

Ensure that the trusted nodes listed in the import file contain the IP address of theadministrator PC from which you log onto the server. If the administrator PC is notconfigured as a trusted node, you will be unable to access this server once the ACLrules are committed. (Access to this server will be blocked.)

5. Type exit and press Enter to revert back to a login with the SSA role.

6. After you create the ACL import file, enter iptcfg and press Enter.

The IPTables Configurations Options menu appears.

7. At the prompt Selection [1 to 9], enter 4 to select Import Configurations, and pressEnter.

A warning appears informing you that this operation will revise the existing IPTables rules.

8. At the prompt Proceed (Y or N), enter y and press Enter.

9. At the prompt Import file name (full path), enter the full path and ACL import filename for this server and press Enter.

The following warning appears:

WARNING: Trusted nodes must include those from which the user logsinto the current server to perform the maintenance tasks. If youhave not specified them as trusted nodes in the import file, youwill not be able to log in to the server again after the importinghas completed.






Configuring external ACL rules manually (using the iptcfg tool)Before you beginYou must be able to log onto the server as a user with the System Security Administrator (SSA)role.

About this taskUse this procedure to configure the external ACL rules using the iptcfg tool. See External ACLconfiguration settings on page 108 to determine the list of trusted nodes, trusted ports, and DSCPsettings you must configure on each server.

Note:You must perform this procedure on all servers in the Avaya Aura® Conferencing system.

If your deployment supports integrated audio and video, this includes the Flash Media Gateway(FMG) server. For more information on integrated audio and video, see Deploying integratedaudio and video.


2. At the command prompt, enter iptcfg and press Enter.


3. At the prompt Selection [1 to 9], enter 1 to select Configure Trusted Nodes, andpress Enter.

The Trusted Nodes Configuration Options menu appears.

4. Perform the following steps for each trusted node you want to add to the configuration:

a. At the prompt Selection [1 to 6], enter 2 to select Add a new trusted nodeconfiguration, and press Enter.

b. Enter the local IPv4 node address.

c. At the prompt Enter trusted node type, enter 1 to add a single trusted node tothe local IPv4 address you entered in Step B, and press Enter.

d. Enter the IPv4 trusted node address, and press Enter.

e. Enter y and press Enter to confirm your action.

f. Repeat Steps A through E for each trusted node you want to add to the configuration.

5. At the prompt Selection [1 to 6] for the Trusted Nodes Configuration Options menu,enter 5 to select Return to main menu, and press Enter.

6. Enter y and press Enter to confirm your action.





Note:

The list of trusted nodes is not added to the IPTables rules yet. The changes will becommitted to the IPTables rules after you complete this procedure.

7. At the prompt Selection [1 to 9], enter 2 to select Configure Trusted Ports, andpress Enter.

The Trusted Port Configuration Options menu appears.

8. Perform the following steps for each trusted port you want to be enabled on the server:

a. At the prompt Selection [1 to 4], enter 1 to select List all trusted portconfiguration, and press Enter.

The list of all trusted port configurations is displayed.

b. At the prompt Selection [1 to 4], enter 2 to select Modify a trusted portconfiguration, and press Enter.

c. At the prompt Enter ID of trusted port configuration to be modified,enter the ID of the port you want to modify (from the list of all trusted port configuration),and press Enter.

d. Press Enter to confirm your action.

e. At the prompt Enter port status, enter 1 to enable the port or enter 0 to disablethe port.

f. Press Enter.

g. Press Enter to confirm your change.

h. Repeat Steps A through G for each trusted port you want to enable on the server.

9. At the prompt Selection [1 to 4] for the Trusted Port Configuration Options menu,enter 3 to select Return to main menu, and press Enter.



Note:

The list of trusted ports is not added to the IPTables rules yet. The changes will becommitted to the IPTables rules after you complete this procedure.

11. At the prompt Selection [1 to 9], enter 3 to select DSCP Marking, and press Enter.

The DSCP Marking Configuration Options menu appears.

12. Perform the following steps for each DSCP value you want to configure on the server:

a. At the prompt Selection [1 to 4], enter 1 to select Show DSCP markingconfiguration, and press Enter.

The DSCP marking configuration is displayed.




b. At the prompt Selection [1 to 4], enter 2 to select Modify DSCP values, andpress Enter.

c. At the prompt Enter ID of the DSCP category to be modified, enter the IDof the DSCP value you want to modify (displayed in the DSCP marking configuration),and press Enter.

d. Enter the DSCP value and press Enter.

e. Press Enter to confirm your change.

f. Repeat Steps A through E for each DSCP value you want to configure on the server.

13. At the prompt Selection [1 to 4] for the DSCP Marking Configuration Options menu,enter 3 to select Modify DSCP marking status, and press Enter.

14. Enter 1 to enable the DSCP marking status or enter 0 to disable it.

15. Press Enter.

16. Press Enter to confirm your change.

17. At the prompt Selection [1 to 5] for the DSCP Marking Configuration Options menu,enter 4 to select Return to main menu, and press Enter.



Note:

The DSCP configuration changes are not added to the IPTables rules yet. The changeswill be committed to the IPTables rules after you complete this procedure.

19. At the prompt Selection [1 to 9], enter 5 to select Commit IPTables Rules, andpress Enter.


The following warning appears:

WARNING: Trusted nodes must include those from which the user logsinto the current server to perform the maintenance tasks. If youhave not configured these as trusted nodes, you will not be able tolog in to the server again after the configuration changes arecommitted.


22. Restart the Web Conference Server (WCS) network element.

This is an important step. If you do not restart the WCS, the WCS will not operate correctlyand users will not be able to start or join a Web collaboration.





Verifying the ACL configurationBefore you beginYou must be able to log onto the server as a user with the System Security Administrator (SSA)role.

About this taskUse the following procedure to verify the ACL configuration.

Note:You must perform this procedure on all Avaya Aura® Conferencing core servers and AvayaMedia Servers.


2. At the command prompt, enter iptstatus -n and press Enter.

The list of trusted nodes is displayed.

3. Verify that the list of trusted nodes contains the trusted nodes that you configured either inthe import file or manually.

Note:

The full list of trusted nodes contains internal ACL trusted nodes as well as externaltrusted nodes that you configured either in the import file or manually. The list of externaltrusted nodes is a subset of all ACL rules.

4. Enter iptstatus -p and press Enter.

The list of trusted ports is displayed.

5. Verify that the list of trusted ports matches the trusted ports that you configured either in theimport file or manually.

6. Enter iptstatus -d and press Enter.

The list of DSCP values is displayed.

7. Verify that the list of DSCP values matches the DSCP values that you configured either inthe import file or manually.

8. Ensure that all rules according to the external ACL configuration table are configured. See External ACL configuration settings on page 108.


External ACL configuration settingsThe following table shows how you should configure the trusted ports, trusted nodes, and DSCPmarking on each server on the Avaya Aura® Conferencing system for each deployment layout.




Table 3: External ACL configuration settings

Deploymentlayout

Servers Trusted Ports Trusted Nodes DSCP Marking

SMB andmedium(simplex andredundant)

Element Managerservers

6000 - 42599 • DNS server

• remote NTP servers

• remote syslog server

• remote backup server

• FTP server

• administrator PC

• Element ManagerService address

Note:

If you do not addthe ElementManager Serviceaddress as atrusted node, theadministratorcannot launchMCP ElementManager.

• If you plan onimplementing automaticdisaster recovery (ADR)in your deployment,then you must make theprimary and secondaryElement Managerstrusted nodes of eachother. For moreinformation, see Configuring ADR.

Disabled

SMB andmedium withDMZ (simplexand redundant)


6000–42599 • DNS server




• FTP server



Disabled




Deploymentlayout


Note:


• If you plan onimplementing automaticdisaster recovery (ADR)in your deployment,then you must make theprimary and secondaryElement Managerstrusted nodes of eachother. For moreinformation, see Configuring ADR.

Web ConferencingServers (WCS)

443

8140–8142

Note:

If you do notenable 8140–8142, the WebCollaborationService will notoperatesuccessfully.

• DNS server



• FTP server

Disabled

Flash MediaGateway (FMG)server

The RTP and RTCPports should matchthe range of themedia servers.

Note:

By default, theFMG RTP portrange is40000-60000and the mediaserver portrange is6000-42599.

Enabled




Deploymentlayout


You mustadjust one ofthese rangesettings toensure that theFMG ports arewithin themedia serverrange.

Ensure that theclient configurationfile for the Audio/Video inCollaboration Agentclient uses thefollowing values:

• RTMPT: Port 80

• RTMPS: Port 443

Do not use RTMPport 1935 or all.

Large (simplexand redundant)


• DNS server




• FTP server



Note:


• If you plan onimplementing automaticdisaster recovery (ADR)in your deployment,

Disabled




Deploymentlayout


then you must make theprimary and secondaryElement Managerstrusted nodes of eachother. For moreinformation, see Configuring ADR.

Web ConferencingServers (WCS)

443

8140–8142

Note:

If you do notenable 8140–8142, the WebCollaborationService will notoperatesuccessfully.

• DNS server



• FTP server

Disabled

Avaya MediaServers (MS)

6000 - 42599 • DNS server



• FTP server

Enabled

Flash MediaGateway (FMG)server

The RTP and RTCPports should matchthe range of themedia servers.

Note:

By default, theFMG RTP portrange is40000-60000and the mediaserver portrange is6000-42599.You mustadjust one ofthese rangesettings toensure that theFMG ports arewithin themedia serverrange.

Enabled




Deploymentlayout


Ensure that theclient configurationfile for the Audio/Video inCollaboration Agentclient uses thefollowing values:

• RTMPT: Port 80

• RTMPS: Port 443

Do not use RTMPport 1935 or all.


Example of import.dat fileThe rules for an external ACL configuration file appear in:

/opt/mcp/ipt/example/import.datFollow the instructions in the example file to configure an ACL configuration file properly.

Here is an example of the import.dat file (external ACL configuration file) for Element Managerservers in SMB or medium redundant and SMB or medium simplex layouts:trusted node 192.168.209.241 192.168.209.212trusted node 192.168.209.241 192.168.209.10trusted node 192.168.209.241 192.168.209.20trusted node 192.168.209.241 192.168.209.13siptcpport 5060 0siptcptlsport 5061 0httpport 80 0httpsport 443 1dscpenabled falseddscpvalue 1 48dscpvalue 2 18dscpvalue 3 16mediaports 6000 42599 1





Guidelines for certificate configurationThe Certificate Authority that is used to sign certificates and the requirements for the common nameof the certificates, for each Network Element interface, is shown in the following table. The NetworkElements that require certificates to be signed by the System Manager Certificate Authority can alsobe signed by another Certificate Authority instead, for example, an intermediate enterpriseCertificate Authority. In this situation, the System Manager CA is configured as an intermediateCertificate Authority of an Enterprise Certificate Authority.

For more information, see Deploying Avaya Aura® Conferencing, which is available from https://support.avaya.com/.

Important:

If the System Manager Certificate Authority is mentioned, there must be a trust relationshipbetween that Network Element and the System Manager.

Note:

If TLS is enabled for the SIP interfaces, TLS must be enabled on each of the SIP interfaces asshown in the following table. Avaya recommends that you deploy the system with TLS enabledand is enabled by default.

Note:

If you are using a reverse proxy in your deployment, then third party certificates are not installedon Avaya Aura® Conferencing.

Table 4: Guidelines for certificates

This table lists the configuration guidelines for large deployments. The footnotes show the differences for SMBand medium enterprises.

Network Element Network Elementinterface

CertificateAuthority

Logical Name Common Name

Element Manager EM Internal OAM System Manager EMIntOAMCert FQDN of serviceaddress

EM External OAM N/A N/A N/AProvisioningManager

Prov InternalOAM HTTPS

System Manager EMS1-FQDN-CERT FQDN of serveraddress

Prov ExternalOAM HTTPS

N/A N/A N/A

CA DirectoryServer

System Manager EMS1-FQDN-Cert FQDN of serveraddress

CA HTTPS Enterprise/Public/System Manager

EMS1-FQDN-Cert FQDN of serveraddress

CA SIP System Manager EMS1-IP-Cert IP address of serveraddress




Network Element Network Elementinterface

CertificateAuthority

Logical Name Common Name

CollaborationAgent

CA HTTPS Enterprise/Public/System Manager

WCSH1-FQDN-Cert6

FQDN of serveraddress

CA DirectoryServer

System Manager WCSH1-FQDN-Cert FQDN of serveraddress

CA SIP System Manager WCSH1-IP-Cert7 IP address of serveraddress

Application Server AS SIP System Manager ASSIPCert IP address of theservice address

AS DirectoryServer

EMS1-FQDN-Cert FQDN of serveraddress

Media Server Media Server SIP System Manager MS1S1-IP-CERT7 IP address of serveraddressMedia Server

SOAPMS1S1-IP-CERT7

DocumentConversionServer

DCS HTTPS System Manager WCSH1-FQDN-Cert6

FQDN of serveraddress

WebConferencingManagementServer

WCMS HTTPS System Manager EMS1-IP-Cert IP address of serveraddress

WebConferencingServer8

WCS HTTPS Enterprise/Public/System Manager

WCS1Cert FQDN of serviceaddress or wildcard.An example wildcard is*.mydomain.com


6 For SMB and medium size deployments, use the existing EMS1-FQDN-Cert and EMS2-FQDN-Cert.7 For SMB and medium size deployments, use the existing EMS1-IP-Cert and EMS2-IP-Cert.8 If you are using a third party Certificate Authority to generate certificates, the certificate for the WCS network element

must support the following Certificate Key Usages:

• Signing

• Key encipherment

• Web Server Authentication

• Web Client Authentication




Obtaining enrollment password from System ManagerThe trust management services enables auto enrollment for certificates from System Manager. Youare required to know the enrollment password when requesting certificates from the SystemManager. If you already know the enrollment password, you can skip this procedure.

About this taskUse the following procedure to obtain the enrollment password.

Procedure1. Log on to System Manager.

2. On the System Manager console, click Services > Security.

3. In the navigation pane, click Certificates.

4. Click Enrollment Password.

5. On the Enrollment Password screen, in the Existing Password field, record the passwordfor use in the following procedure.

6. On the Security tab, click x to close the Security window.

Next stepsProceed to Creating Network Element certificates signed by the System Manager on page 116.


Creating Network Element certificates signed by System ManagerThe System Manager can be used on your network as a Certificate Signing Authority for NetworkElements that require certificates. Integration with the System Manager Trust Management serviceallows certificate enrollment for certificates issued by the System Manager to the Avaya Aura®

Conferencing components directly from the Avaya Aura® Conferencing Element Manager.

Before you beginYou must know the enrollment password as completed in Obtaining enrollment password fromSystem Manager on page 116.

About this taskUse the following procedure to create X.509 Certificates signed by the System Manager for anyNetwork Elements created after the initial installation, or to create new certificates when necessary.

Procedure1. In the Address box of the Web browser, enter the following address: https://<FQDN>:

12121




where <FQDN> is the EM Internal OAM Service IP address. (This is the logical IP address ofthe server running Element Manager Console.)

Note:

This is a secure site. If you get a certificate error message, follow the instructions onyour browser to install a valid certificate on your computer.

2. Press Enter.

A Web page appears displaying the IP address you entered and the link Launch ElementManager Console.

3. On the <IP address> page, click Launch Element Manager Console.

4. From the IPv4 Service Address box on the Element Manager Console window, select theFQDN/IP address of the server running Element Manager.

5. Click Connect.

6. On the Element Manager Authentication window, click the Accept the certificate for thissession only option button.

7. Click Apply.

A connection is established to the active element manager (EM) instance.

8. In the UserID box on the Element Manager Console window, enter admin.

9. In the Current Password box, enter admin.

10. Click Ok.

11. In the navigation pane of Element Manager Console, click Security > CertificateManagement > Enrollment Request.

12. In the Certificate Enrollment window, complete the following fields:

• Logical Name: Type a logical name for the certificate to be assigned to a specificmanaged network element, for example, Provisioning Manager NE.

• Bit length: Select 1024, 2048, or 4096 from the list. If your security policy does notspecify bit length, select 2048.

• Common name: Type the FQDN or IP address, for example, emsvc.avaya.com. See Guidelines for certificate configuration on page 114 for guidance on common name valuesfor certificates that use the System Manager as the Certificate Signing Authority.

• Enrollment password: This password must match the current Enrollment Password thatis configured on System Manager.

13. Click Submit.

ResultThe certificate is automatically installed on the Element Manager Keystore.




Note:Prior to certificate expiry, Avaya recommends that you generate a new certificate using a newlogical name and then refresh the certificate by changing the network element to use the newlogical name. The expired certificate can then be removed from the Element Manager Keystore.


Assigning a new certificate to the Element ManagerNote:

You do not need to complete this task for the initial installation of Avaya Aura® Conferencing.You only require this task if you need to update the certificate for another reason, such as anFQDN change, a certificate expiry, or a certification revocation.

Before you begin• A new certificate for the Element Manager must exist in the Element Manager Keystore.• Single sign-on from the System Manager to the Element Manager Console requires that the

certificate has the FQDN of the EM Service address as the Common Name of the certificate.• The certificate has been signed by a CA that the System Manager trusts. This is typically the

System Manager CA.

Note:The Element Manager Network Instance will require a restart afterwards.

About this taskUse the following procedure to assign a new certificate to the Element Manager.


2. In the navigation pane of Element Manager Console, select Feature Server Elements >Element Manager.

3. In the Element Manager window, select the element manager.

4. Click Edit (-/+).

5. In the Edit Element Manager dialog box, complete the following:

• Enable HTTP Port: Clear this check box.

• Internal OAM – HTTPS Certificate: Select the required HTTPS certificate by logicalname, for example, EMIntOAMCert.

6. Click Apply.

7. Click File > Exit on the Element Manager Console to exit.




8. Log on to EMServer with an account using the AA role, such as, ntappadm, through SSH ordirectly at the server console.

9. At the password prompt, type the password for ntappadm.

10. Type emStop.pl, and press Enter.

11. Type emStart.pl, and press Enter.

12. Log on to the Element Manager Console.

13. (Optional) If the new certificate is signed by a different Certificate Authority not previouslytrusted by the Element Manager Console, an Element Manager Authentication Dialogwindow appears. Select Store the certificate’s signing certificate authority as a trustedcertificate for this and future connections

14. Click Apply.

Next stepsProceed to Assigning a new certificate to the Provisioning Manager on page 119.


Assigning a new certificate to the Provisioning ManagerNote:


Before you begin• A certificate for the Provisioning Manager must exist in the Element Manager Keystore.• Single sign-on from the System Manager to the Provisioning Manager requires that the

certificate has the FQDN of the server hosting the Provisioning Manager as the CommonName.

• The certificate has been signed by a CA that the System Manager trusts. This is typically theSystem Manager CA.

Note:If the Provisioning Manager is online, it will require a restart of the Network Element Instanceafterwards.

About this taskUse the following procedure to assign a certificate to the Provisioning Managers.





2. In the navigation pane of Element Manager Console, select Feature Server Elements >Provisioning Managers.

3. In the Provisioning Managers window, select the PROV1.


5. In the Edit PROV1 dialog box, complete the following fields:

In the Prov section:

• Enable HTTP Port: Clear the check box.

• Internal OAM HTTPS Certificate: Select the required HTTPS certificate by logical name,for example, Prov1IntOAMCert.

In the PA section:


• HTTPS Certificate: Select the required HTTPS certificate by logical name, for example,PA1Cert.

• SIP Certificate: If the Enable SIP TLS Port option is enabled, select the required SIPcertificate by logical name, for example, PA1SIPCert.

Note:

The certificates in the PA submenus are required only when the PA is co-hosted with theProvisioning Manager.

6. Click Apply.

7. Repeat this procedure for any additional Provisioning Managers.

Next stepsProceed to Assigning a new certificate to the Collaboration Agent Manager on page 120.


Assigning a new certificate to the Collaboration Agent ManagerNote:

This procedure is specific to large deployments with redundancy and large simplexdeployments. If you have an SMB or a medium deployment with redundancy or an SMB or amedium deployment simplex deployment, you can skip this procedure.

The large deployment layouts make use of independent Collaboration Agent Manager NetworkElements to provide support for physical separation from the Provisioning Manager NetworkElement for security and scalability.




Before you beginCertificates for the Collaboration Agent Manager must exist in the Element Manager Keystore.

Note:If Collaboration Agent Manager is online, it will require a restart of the Network ElementInstance afterwards.

About this taskUse the following procedure to assign a certificate to the Collaboration Agent Manager.


Collaboration Agent.

2. In the Collaboration Agent Managers window, select CA1.


4. In the Edit Collaboration Agent dialog box, complete the following fields:


• PA HTTPS Certificate: Select the required HTTPS certificate by logical name, forexample, CA1Cert.

• SIP Certificate: If the Enable SIP TLS Port option is enabled, select the required SIPcertificate by logical name, for example, CA1SIP.

5. Click Apply.

Next stepsProceed to Assigning a new certificate to the Application Server on page 121.


Assigning a new certificate to the Application ServerNote:


Before you begin• A new certificate for the Application Server must exist in the Element Manager Keystore.• The certificate has been signed by a Certificate Authority that the System Manager trusts. This

is typically the System Manager Certificate Authority.




Note:If the Application Server is online, it will require a restart of the Network Element Instanceafterwards.

About this taskUse the following procedure to assign a certificate to the Application Server.


Application Servers.

2. In the Application Servers window, select AS1.


4. In the Edit Application Server dialog box, complete the following field:

• SIP Certificate: If the Enable SIP TLS option is enabled, select the required SIPcertificate by logical name, for example, ASSIPCert

5. Click Apply.

Next stepsProceed to Assigning a new certificate to the Avaya Media Server on page 122.


Assigning a new certificate to the Avaya Media ServerBefore you begin

• A new certificate for each Avaya Media Server must exist in the Element Manager Keystore.• The new certificate has been signed by a Certificate Authority that is in the Element Manager

Truststore.• The Avaya Media Server is in the Offline State.

About this taskUse the following procedure to assign a new certificate the Avaya Media Server.

Procedure1. In the navigation pane of the Element Manager Console, select Feature Server Elements >

Media Servers and Clusters > Media Servers.

2. In the Media Servers window, select MS1.





4. In the Edit Media Server dialog box, complete the following fields:

• SIP Certificate: If the SIP TLS option is enabled, select the required SIP certificate fromthe list. This list corresponds to the logical names in the Keystore, for example, AMS1Cert.

• SOAP Certificate: If the Enable SOAP/TLS option is enabled, select the appropriatecertificate form the list. This list corresponds to the logical names in the Keystore.Generally, the same certificate used for the SIP interface is used here, for example,AMS1Cert.

5. Click Apply.

Next stepsProceed to Assigning a new certificate to the Web Conferencing Server on page 123.


Assigning a new certificate to the Web Conferencing ServerBefore you beginA new certificate with a common name using the FQDN of the Web Conferencing Server must existin the Element Manager Keystore.

Note:If the Web Conferencing Server is online, it will require a restart of the Network ElementInstance afterwards.

About this taskUse the following procedure to assign a new certificate to the Web Conferencing Server.


Web Conferencing > Web Conferencing Servers.

2. In the Web Conferencing Server window, select WCS1.


4. In the Edit Web Conferencing Server dialog box, complete the following field:

• HTTPS Certificate: Select the required HTTPS certificate by logical name, for example,WCS1Cert.

5. Click Apply.

6. Repeat this procedure for any additional Web Conferencing Servers.

Next stepsProceed to Assigning a new certificate to the Web Conferencing Management Server on page 124.





Assigning a new certificate to the Web Conferencing ManagementServer

Note:


Before you begin• A new certificate for the Web Conferencing Management Server must exist in the Element

Manager Keystore.• The certificate has been signed by a Certificate Authority that is in the Element Manager

Truststore. This is typically the System Manager Certificate Authority.

About this taskUse the following procedure to assign a new certificate to the Web Conferencing ManagementServer.


Web Conferencing > Web Conferencing Management Servers.

2. In the Web Conferencing Manager Servers window, select WCMS1.


4. In the Edit Web Conferencing Manager Server dialog box, complete the following field:

• HTTPS Certificate: Select the required certificate from the list. This list corresponds to thelogical names in the Keystore, for example, EMS1-IP-Cert.

5. Click Apply.

Next stepsProceed to Assigning a new certificate to the DCS on page 125.





Assigning a new certificate to the DCSBefore you begin

• A new certificate for the Document Conversion Server (DCS) must exist in the ElementManager Keystore.

• The certificate has been signed by a Certificate Authority that is in the Element ManagerTruststore. This is typically the System Manager Certificate Authority.

About this taskUse the following procedure to assign a new certificate to the DCS.


Document Conversion Servers > Document Conversion Servers.

2. In the Document Conversion Servers window, select the DCS, for example, DCS1.


4. In the Edit DCS dialog box, complete the following field:

• HTTPS Certificate: Select the required certificate from the list. This list corresponds to thelogical names in the Keystore, for example, WCSH1-FQDN-Cert.

Note:

This certificate must be based on the FQDN, not the IP address.

5. Click Apply.



Starting an Element Manager instance from the server consoleAbout this taskUse the following procedure to start the primary Element Manager, database, and other networkelements.

Procedure1. Log on to the server hosting EM instance 0 either through ssh or the server console. At the

logon prompt, type ntappadm or logon to an account with the AA role assigned.




2. Type cd /var/mcp/install, and press Enter.

3. Type ./emStart.pl, and press Enter.


Configuring single sign-on for Element Manager Console andProvisioning ClientIntroduction

System Manager is a central management system that delivers a set of shared managementservices and a common console across multiple products. With single sign-on (SSO) enabled forAvaya Aura® Conferencing, you can administer all the components using System Manager. Thischapter provides the procedures to configure SSO, configure System Manager to recognize eachnetwork element, and configure the administrator PC.


Configuring time on System Manager and network elementsAbout this taskTo use single sign-on (SSO), System Manager and all the network elements must havesynchronized clocks. A clock skew of a few seconds results in SSO to fail. If the Home portlet ismissing menus or functions, logon access to the Element Manager Console or Provisioning Clientcan fail.

Note:Ensure your servers use the Network Time Protocol (NTP) time sources.

Procedure1. Log on to the System Platform Console.

2. In the navigation pane, click Server Management > Date/Time Configuration.

3. On the Server Management Date/Time Configuration page, verify that you are using NTPserver in the Manage Time Servers area. If only Local Clock displays, add at least one NTPserver and in the Added Servers field, and click start ntpd. Use the Primary Clock Sourceand Secondary Clock Source values, and check the Local Time value.

Warning:

Clicking start ntpd causes the system platform and server to restart.




4. Open an SSH connection and log into EMServer1 as ntsysadm to verify the time on theserver.

5. Type date, and press Enter.

6. Compare the time on the System Platform Console with the time on the application server. Ifthe time difference between the System Platform Console and the application server isgreater than 60 seconds, perform the following steps:

a. Verify that the NTP is configured on the application server.

b. On the application server, run the ntpConfig tool.

c. Type c to configure.

d. Use the Primary Clock Source and Secondary Clock Source values

e. Type date, and press Enter.

f. Compare the time on the System Platform console with the time on EMServer1. If thetime difference between the System Platform Console and the application server is stillgreater than 60 seconds, perform Steps G through K to correct the date and timemanually on the application server by forcing the NTP time update.

g. At the command prompt, enter su — to log in as root.

h. After you log in as root, type service ntpd stop, and press Enter to stop the ntpdservice.

i. Run /usr/sbin/ntpdate <Primary Clock Source IP address> to update thesystem time.

j. Type date, and press Enter to verify that the date and time have been adjusted.

k. Type service ntpd start, and press Enter to start the ntpd service.

7. Repeat Steps 5 and 6 for each application server.

Next stepsProceed to configuring network element FQDNs in System Manager.


Configuring the application server network elements on System ManagerAbout this taskDetails of each Network Element must be added in the System Manager inventory so that it ispossible to launch the Network Elements directly from System Manager. To configure details ofeach Element Manager, use the following procedure.

Note:System Manager must have only PROVs from one Avaya Aura® Conferencing system in yourinventory. If you have another Avaya Aura® Conferencing system, and you enter the PROV




elements in the System Manager inventory, you can encounter problems. System Manageralways sends conferencing profile data to one PROV. The data is sent to the first availablePROV in the inventory.

Note:To use single sign-on (SSO), the System Manager FQDN, Element Manager FQDN, andProvisioning Client FQDN (if required) must belong to the same root domain.

Procedure1. Log on to System Manager as admin.

2. On the System Manager console, click Inventory.

3. In the navigation pane, click Manage Elements.

4. On the Manage Elements page, click New.

5. In the General section on the New Elements page, select Conferencing from the Type list.

The page refreshes and additional fields appear.

6. In the General section on the New Conferencing page, complete the following fields:

• Name: Type AAC-EM.

• Node: Type the FQDN of the Element Manager Service IP address.

7. Click Access Point.

8. In the Access Point section, click New.

9. In the Access Point Details section, complete the following fields:

• Name: Type the FQDN of the Element Manager Service IP address.

• Access Point Type: Select EMURL.

• Protocol: Select https.

• Host: Type the FQDN of the Element Manager Service IP address.

• Port: Type 12121.

• Path: Type sso.

• Order: Type 0.

10. Click Save.

11. Click Commit.

The addition of Element Manager on System Manager is now complete.

12. For Provisioning Manager, perform the following steps:

a. On the Manage Elements page, click New.

b. On the New Elements page, complete the following fields:

• Name: Type AAC-PROV.




• Type: Select Conferencing.

• Node: Type the FQDN of the EMServer1.

c. Click Access Point.

d. In the Access Point area, click New.

e. In the Access Point Details area, complete the following details:

• Name: Type the IP address of EMServer1.

• Access Point Type: Select EMURL.

• Protocol: Select https.

• Host: Type the FQDN of the EMServer1.

• Port: Type 8443.

• Path: Type prov/sso.

• Order: Type 0.

f. Click Save.

g. Click Commit.

The addition of Provisioning Client on System Manager is now complete.

Next stepsProceed to Launching Element Manager Console and Provisioning Client from System Manager.


Launching Element Manager Console and Provisioning client from SystemManager

After single sign-on is enabled, you can launch network elements directly from System Manager.

Note:

System Manager administrators have permissions for controlling access to Conferencing andElement Manager and Provisioning Client elements. By default, administrators with eitherNetwork Administrator or System Administrator roles have read, write, and expert modepermissions. You can change role assignments and configure permissions for access to variouselements. On System Manager home page, click Users > Administrators.

Warning:

If you have Expert mode privileges, you see an Expert mode warning on certain ProvisioningClient pages. This mean that the data on this page is normally controlled by System Manager.Only make changes on these pages to fix synchronization issues with System Manager.




About this taskUse the following procedure to launch the Element Manager Console and Provisioning Client fromSystem Manager.


2. On the System Manager console, click Elements > Conferencing.

3. On the Conferencing Dashboard page, in the Name column, select the name of ElementManager Console.

4. From the IPv4 Service Address box on the Element Manager Console window, select the IPaddress of the server running Element Manager Console.

5. Click Connect.

The Element Manager Console window appears.

6. From the Element Manager Console menu bar, select File > Exit to exit Element ManagerConsole.

7. On the Conferencing Dashboard page, in the Name column, select the name of ElementManager Console. Click the name of the Provisioning Client you want to access.

The Welcome to the Provisioning Client page appears.

8. On the Provisioning Client page, click Logout.

ResultThe Element Manager Console and Provisioning client can now be launched from System Manager.


Configuring the route to Avaya Aura® Conferencing on SystemManager

About this taskUse the following procedure to configure the route to Avaya Aura® Conferencing from SystemManager.

Procedure1. Log in to System Manager.

2. On the System Manager console, click Elements > Routing.

3. In the navigation pane, click SIP Entities.

4. On the SIP Entities page, click New.




5. Complete the following fields:

• Name: Enter a unique name from 3 to 64 characters for this SIP entity.

• FQDN or IP Address: Type the FQDN or IP address of the AS1 signaling service.

• Type: Select Conferencing.

The screen refreshes to display the following:

• Adaptation: Select from the list.

• Location: Select your location.

• Time Zone: Select a time zone from the list.

• Override Port & Transport with DNS SRV: Select the check box to enable it.

• SIP Timer B/F (in seconds): Type a value between 1 to 32, default is 4.

• Credential name: Type a name.

• Call Detail Recording: Select from the list.

• SIP Link Monitoring: Select Use Session Manager Configuration.

• Supports Call Admission Control: Select the check box to enable it.

• Shared Bandwidth Manager: Select the check box to enable it.

• Primary Session Manager Bandwidth Association: Select your Session Managerentity.

• Backup Session Manager Bandwidth Association

6. Click Commit.

7. In the navigation pane, click Entity Links.

8. On the Entity Links page, click New.

9. Complete the following fields:

• Name: Enter a name for this link.

• SIP Entity 1: Select the Aura Session Manager entity.

• Protocol: Select TCP.

OR

Select TLS.

• Port: Enter 5060 for TCP or 5061 for TLS.

• SIP Entity 2: Select the Avaya Aura® Conferencing SIP entity you previously created.

• Port: Enter 5060 for TCP or 5061 for TLS.

• Connection Policy: Select Trusted.




Note:

If TLS is selected for SIP Entity 1 then it must also be selected for SIP Entity 2.

10. Click Commit.

11. In the navigation pane, click Routing Policies.

12. On the Routing Policies page, click New.

13. In the Name box on the Routing Policies page, enter a name for this routing policy.

14. In the SIP Entity as Destination area, click Select.

15. On the SIP Entity List page, select the Avaya Aura® Conferencing SIP entity.

16. Click Select.

17. Click Commit.

18. In the navigation pane, click Dial Patterns.

19. On the Dial Patterns page, click New.

20. In the Pattern box on the Dial Pattern Details page, type the routing/pilot number that is partof the dialing number to join MeetMe conferences.

21. In the Min box, type the number of digits that match the pattern number. This is the minimumnumber of digits in the dialing number.

22. In the Max box, type the number of digits that match the pattern number. This is themaximum number of digits in the dialing number.

23. In the Originating Location and Routing Policies area, click Add.

24. In the Originating Location area, select your location.

25. In the Routing Policies area, select the routing policy that you previously created for AvayaAura® Conferencing.

26. Click Select.

27. Click Commit.

ResultYou have configured the routing policy so that when you dial a number that contains the pattern youspecified, your call goes to the Avaya Aura® Conferencing Application Server.





Creating a System Manager- signed certificate for the Flash MediaGateway IP address

About this taskUse the following procedure to create a certificate for the Flash Media Gateway IP address that issigned by System Manager.


2. Click Services > Security.

3. In the navigation pane, click Certificates > Authority.

4. In the navigation pane, click Add End Entity.

5. In the Add End Entity window, complete the following fields:

• End Entity Profile: Select INBOUND_OUTBOUND_TLS from the list.

• Username: Enter the IP address of the Flash Media Gateway.

• Password: Enter any password. You will use this password when creating the certificate.

• Confirm Password: Type the password again.

• CN, Common Name (first entry): Enter the userID for the specific administrator. Forexample, admin.

• Token: Select JKS file from the list.

6. Click Add End Entity.

7. In the navigation pane, click Public Web.

8. In the navigation pane of the new browser window or tab, click Create Keystore.

9. Type the user name and password, and click OK.

10. Click OK.

11. Click OK, and save the *.jks file on your PC.





Configuring a secure SIP TLS connection from the Flash MediaGateway to Avaya Aura® Session Manager

About this taskUse this procedure to configure a secure SIP TLS connection from the Flash Media Gateway toAvaya Aura® Session Manager.

Procedure1. Log on to System Manager and create a TLS SIP entity link from Session Manager to each

Flash Media Gateway using port 5061.

2. Open a web browser and go to https://<PROV IP address or FQDN>:8443/fmgadmin/index.html where <PROV IP address or FQDN> is the IP address or FQDNof the server running Provisioning Manager.

The Log On page for Avaya One Touch Video 3.0 appears.

3. In the User Name box, enter admin.

4. In the Password box, enter admin01.

5. Click Log on.

The Legal Notice page appears.

6. On the Legal Notice page, read the information provided.

7. To accept the information displayed, click Accept.

The Welcome page appears.

8. From the Flash Media Gateway area in the navigation panel, click List All.

9. In the System Status area of the Flash Media Gateway page, select a Flash Media Gateway,and click Edit.

10. In the SIP Trunk area, change the port from 5060 to 5061, and click Save.

11. Repeat Steps 9 and 10 for each Flash Media Gateway.

12. From the Cluster area in the navigation panel, click List All.

13. In the System Status area of the Flash Media Gateway page, select a cluster, and click Edit.

14. In the SIP Trunk area, make the following changes:

• Port: Set to 5061 (or other port that is used for SIP TLS on Session Manager).• Enable: Set to TRUE.• TLS certificate: Click Upload, select the certificate you create in Creating a System

Manager- signed certificate for the Flash Media Gateway IP address on page 133 andupload the file.

• Key Store Password: Enter the password from Step 3 in Creating a System Manager-signed certificate for the Flash Media Gateway IP address on page 133.




15. Click Save.

16. Go to the Flash Media Gateway on the Management Portal client and restart all Flash MediaGateways.


Changing the system default settings to use Avaya Aura®

Conferencing (AAC)About this taskUse this task to enable Allow Bandwidth Management and disable User Password OwnedLocally in the Provisioning Client

Procedure1. In the Provisioning Client, navigate to System Management > System Default Settings.

2. In the System Default Settings tab, enable the Allow Bandwidth Management checkbox.

3. In the System Default Settings tab, disable the User Password Owned Locally checkbox.

4. Click Save.



Removing the dialing rules in Provisioning ClientAbout this taskUse this task to remove the dialing rules in Provisioning Client. Remember, there are two types ofdialing rules: Pretranslation rules and Translation rules.

Procedure1. In the Provisioning Client, navigate to System Management > Dialing Rules.

2. In the Pretranslations tab, choose pretranslation rule you want to remove and click Delete.

3. In confirmation window type your password and click Confirm.

4. Repeat steps 2-3 for each of the pretranslation rules.




5. In the Translations tab, choose translation rule you want to remove and click Delete.

6. In confirmation window type password and click Confirm.

7. Repeat steps 5-6 for each of the translation rules.



Removing all SIP entities for PBXs in Element ManagerAbout this taskUse this task to remove all SIP entities for PBXs in the Element Manager GUI.

Procedure1. In the navigation pane of the Element Manager Console, select SIP Entity > SIP Entity.

2. In the SIP Entity window, select SIP entity for the PBXs you want to remove, click Delete (-).

3. In Confirmation window click Yes.

4. Repeat steps 1-3 for all SIP entities for PBXs.



Removing all the old certificates on TurnkeyAbout this taskUse this task to remove all the old certificates on the Turnkey solution in the Element Manager GUI.

Procedure1. In the navigation pane of the Element Manager Console, select Security > Certificate

Management > Keystore.

2. In the Keystore window, select old certificate you want to remove, click Delete (-).

3. In Confirmation window click Yes.




4. Repeat steps 1-3 for all the old certificates you want to remove.






Chapter 5: Migrating from a DMZ solutionto an enterprise solution

Migrating Avaya Aura® Conferencing components from theDMZ to the Enterprise

This section describes how to move Avaya Aura® Conferencing components from the DemilitarizedZone (DMZ) back to the enterprise. In the DMZ, Avaya Aura® Conferencing components areaccessible to external users. By moving these components into the enterprise, they are no longeraccessible to external users through the DMZ.

However, Avaya Aura® Conferencing 8.0 now supports Application Delivery Controllers (ADCs). Youcan provide external access to Avaya Aura® Conferencing using this new ADC functionality. TheADC functionality is now the recommended method for the provision of external access. ADCs offerload balancing capabilities as well as providing a reverse proxy. One of the key benefits of using anADC in the solution is that the number of firewall rules required is greatly reduced, simplifyingconfiguration and maintenance of the solution.

However, if you wish to offer integrated audio and video to external users who reside outside of theenterprise, using the new Avaya Web Collaboration audio and video plug-in, then you must installand configure a Session Border Controller (SBC). You cannot continue to offer integrated audio andvideo to external users when you move the Avaya Aura® Conferencing components from the DMZto the enterprise unless you also install and configure an SBC. In this context, “integrated audio andvideo” means that users can receive their audio and their video feeds through the Web. Thisfunctionality means that users do not have to dial into the conference using a phone connection.The Collaboration Agent user application provides users with all they need to interact with otherparticipants.

Before you begin the this migration task, you should download the following guides from https://support.avaya.com/:

• Deploying Avaya Aura® Conferencing: Advanced Installation and Configuration• Upgrading Avaya Aura® Conferencing• Avaya Aura® Conferencing Port Matrix Guide

These guides contain essential information and you will require this information in order to completethe migration from the DMZ into the enterprise. Ensure that you have downloaded and openedthese guides before working your way through the migration steps.






1 Ensure that you have theappropriate ADChardware configured inthe DMZ.

Avaya recommends usingan Application DeliveryController to allow externalaccess. See Configuring areverse proxy in DeployingAvaya Aura® Conferencing:Advanced Installation andConfiguration.

2 Ensure that you have theappropriate hardwareconfiguration for thisdeployment.

See Deployment Options inDeploying Avaya Aura®

Conferencing: AdvancedInstallation andConfiguration.

3 Install the appropriatesoftware on theenterprise server(s) andensure that you apply theappropriate patches.

See Installing software inDeploying Avaya Aura®


4 Migrate the CollaborationAgent Manager networkelement(s) to anadditional Avaya Aura®

Conferencing WebServer in the enterpriseor remove and configureuse of the CollaborationAgent through theProvisioning Manager inthe enterprise datacenter depending on theappropriate deploymentlayout.

Migrating the CollaborationAgent Manager from theDMZ on page 140

5 Configure the virtualservices on the ADC forthe Collaboration Agent.

See Configuring a reverseproxy in Deploying AvayaAura® Conferencing:Advanced Installation andConfiguration.

6 Migrate the WebConferencing networkelements from theservers in the DMZ toeither the ElementManager Server(s) or anadditional Avaya Aura®

Conferencing WebServer(s) in the

Migrating the WebConferencing Server fromthe DMZ on page 142

Migrating Avaya Aura® Conferencing components from the DMZ to the Enterprise




enterprise data centerdepending onappropriate deploymentlayout.

7 Configure the virtualservices on the ADC forthe Web Conferencingserver.

See Configuring a reverseproxy in Deploying AvayaAura® Conferencing:Advanced Installation andConfiguration.

8 If your deploymentsupports Audio/Video inCollaboration Agent,install it on the identifiedserver in the enterprise.

If your deploymentsupports the new AvayaWeb Collaboration audioand video plug-in,configure it on theidentified server in theenterprise.

See Deploying integratedaudio and video inDeploying Avaya Aura®


If you wish to offer thenew Avaya WebCollaboration audio andvideo plug-in to externalusers who reside outsideof the enterprise, youmust add and configure aSession Border Controller(SBC). An SBC isessential for externalaccess to this feature.The steps for installingand configuring your SBCare in Deploying AvayaAura® Conferencing:Advanced Installation andConfiguration.

9 Uninstall the Audio/Videoin Collaboration Agentsoftware on the identifiedserver in the DMZ.

See Uninstalling softwarein Deploying Avaya Aura®


10 Configure ACL rules onthe Avaya Aura®

Conferencing server toreflect network topologychanges if they wereused.

Configuring the accesscontrol list on page 99

Migrating the Collaboration Agent Manager from the DMZBefore you beginEnsure that you:

• Install and configure an Application Delivery Controller (ADC) in the DMZ.

Migrating from a DMZ solution to an enterprise solution



• Acquire a certificate for the virtual server on the ADC that fronts the Collaboration Agent.

About this taskUse this task to move the Collaboration Agent from the DMZ to the internal enterprise network.

If this is an SMB or medium deployment, the Provisioning Manager also provides CollaborationAgent services. In this case, you must undeploy and remove the Collaboration Agent networkelement instead of moving it into the internal enterprise.

Avaya recommends using an ADC to allow external access. If this is a redundant deployment and isalready using an ADC to load balance and provide high availability, you can move one CollaborationAgent instance at a time. You can do this by disabling the Collaboration Agent instance that you aremoving at the ADC and then changing the internal address at the ADC prior to enabling theCollaboration Agent network instance again. This process ensures that the ADC can continue toroute Collaboration Agent traffic to other Collaboration Agent instances during the move. Anyexisting connections, however, are lost and userz must reconnect and login again to the otherCollaboration Agent.

Procedure1. Stop the Collaboration Agent instance.

For more information, see Stopping a network element instance on page 43.

2. Undeploy the Collaboration Agent instance.

For more information, see Undeploying a network element instance on page 154.

3. If this is a large deployment, change the server for the Collaboration Agent instance to thenew server, otherwise skip to step 4.

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Collaboration Agent Managers > <Collaboration Agent networkelement> > Instance.

b. In the <Collaboration Agent network element> Instance dialog, select theCollaboration Agent network element instance.

c. Click Edit (-/+).

d. In the Edit <Collaboration Agent network element> Instance dialog, select the WebServer from the Server list. For example, WCSServer1.

e. Click Apply.

4. If this is an SMB or medium deployment, undeploy and remove the Collaboration Agentnetwork elements. The Provisioning Manager network element provides Collaboration Agentfunctionality as a subsystem of the Provisioning Manager.



c. Click Delete (-).

Migrating the Collaboration Agent Manager from the DMZ



d. Click Yes to confirm.

5. Change the certificate configured for the Collaboration Agent HTTPS Certificate inaccordance with the guidelines for certificate configuration.

For more information, see Guidelines for certificate configuration on page 114.

6. Deploy and start the Collaboration Agent network element.

For more information, see Deploying a Network Element instance on page 82 and Starting anetwork element instance on page 156.

7. Configure the Application Delivery Controller (ADC).

See Configuring a reverse proxy in Deploying Avaya Aura® Conferencing: AdvancedInstallation and Configuration.

8. Update the firewall rules for the DMZ firewall to reflect these changes.

For more information, see the Avaya Aura® Conferencing Port Matrix Guide, which isavailable on http://support.avaya.com/.

9. Repeat these steps for any additional Collaboration Agent network elements.


Migrating the Web Conferencing Server from the DMZBefore you beginEnsure that you:

• Acquire new IPv4 addresses for each Web Conferencing Server service address on the subnetto which the Web Conferencing Server is moving.

• Update the enterprise Domain Name Server (DNS) with any IP address changes.• Install and configure an Application Delivery Controller (ADC) in the DMZ, with virtual servers

available to proxy connections to the Web Conferencing Server.• Acquire a certificate for the virtual server on the ADC that fronts the Web Conferencing Server.

Note:If your ADC supports Web sockets, then only one virtual server is required per WebConferencing Server cluster. This virtual server will have the Web Conferencing Server clusterFully Qualified Domain Name (FQDN) assigned to it using the Domain Name Server (DNS) andthe certificate must be assigned against this FQDN. Otherwise, there must be a one-to-onemapping between virtual servers on the ADC and Web Conferencing Servers in the WebConferencing Server cluster with a certificate for each virtual server.





About this taskUse this task to move a Web Conferencing Server in the DMZ to the internal enterprise network. Inorder to continue to provide external access, Avaya recommends using an Application DeliveryController.

Procedure1. Stop all instances of the Web Conferencing Servers (WCS) in the Web Conferencing Server

cluster.


2. Undeploy all Web Conferencing Server instances.


3. Change the servers for the Web Conferencing Server instances to the Avaya Aura®

Conferencing servers in the enterprise network. For example, in an SMB simplexdeployment, change the server configuration for the Web Conferencing Server networkelement instance to EMServer1.

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Web Conferencing > <Web Conferencing Servers and Clusters > WebConferencing Servers > <Web Conferencing Server network element> >Instances.

b. In the <Web Conferencing Server> Instance dialog, select the Web ConferencingServer network element instance.


d. In the Edit <Web Conferencing Server> Instance, select the destination Avaya Aura®

Conferencing server from the Server list. For example, EMServer1.

e. Click Apply.

f. Repeat these steps for any additional Web Conferencing Server instances in thecluster.

4. Change the Web Conferencing Server address for each Web Conferencing Server in thecluster.

a. In the navigation pane of the Element Manager Console, select Addresses.

b. Select the row from the Addresses frame for the current Web Conferencing Serverservice address.


d. Modify the IPv4 address to be the new IPv4 address for the Web Conferencing Serverservice address.

e. Click Apply.


Migrating the Web Conferencing Server from the DMZ



5. Change the certificate configured for the Web Conferencing Server in accordance with theguidelines for certificate configuration.


6. Deploy and start the Web Conferencing Server network elements.


7. Configure the Application Delivery Controller (ADC).

See Configuring a reverse proxy in Deploying Avaya Aura® Conferencing: AdvancedInstallation and Configuration.



9. Repeat these steps for any additional Web Conferencing Server clusters.






Chapter 6: Migrating from an enterprisesolution to a DMZ solution

Migrating from an enterprise solution to a DMZ solutionThis section describes how to move Avaya Aura® Conferencing components from the enterprise tothe Demilitarized Zone (DMZ). In the DMZ, Avaya Aura® Conferencing components are accessibleto external users. In this context, “Avaya Aura® Conferencing components” refers to the WebConferencing Server (WCS) and the Collaboration Agent (CA) network element instances.


1 Ensure that you have theappropriate ADChardware configured inthe DMZ.

Avaya recommends usingan Application DeliveryController to allow externalaccess. See Configuring areverse proxy in DeployingAvaya Aura® Conferencing:Advanced Installation andConfiguration.

2 Install the appropriatesoftware on theenterprise server(s) andensure that you apply theappropriate patches.

See Installing software inDeploying Avaya Aura®


Ensure that you configurethe recommended securityhardening in the DMZ fordeploying WebConferencing Server andCollaboration Agentnetwork elementinstances.

See the Avaya Aura®

Conferencing Port MatrixGuide.

3 Disable the AccessControl List (ACL) ruleson Avaya Aura®

Conferencing servers.


4 Add a new DMZ server inthe Element ManagerGUI.

Adding a new DMZ serverin the Element ManagerGUI on page 146




5 Migrate the WebConferencing Server(WCS) network elementinstance to the DMZ.

Migrating the WebConferencing Server to theDMZ on page 149

6 Migrate the CollaborationAgent (CA) networkelement instance to theDMZ.

Migrating the CollaborationAgent Manager to theDMZ on page 147.

7 Uninstall the Audio/Videoin Collaboration Agentsoftware on the identifiedserver in the Enterprise.

See Uninstalling softwarein Deploying Avaya Aura®


8 If your deploymentsupports Audio/Video inCollaboration Agent,install it on the identifiedserver in the DMZ.

If your deploymentsupports the new AvayaWeb Collaboration audioand video plug-in,configure it on theidentified server in theDMZ.

See Deploying integratedaudio and video inDeploying Avaya Aura®


9 Configure ACL rules onthe Avaya Aura®

Conferencing server toreflect network topologychanges if they wereused.


Adding a new DMZ server in the Element Manager GUIAbout this taskUse this task to add a new DMZ server to the Element Manager interface.

Procedure1. Add a new IP address for the DMZ server:


b. In the Addresses window, click Add (+).

Migrating from an enterprise solution to a DMZ solution



c. In the Add IPv4 Address dialog, enter the logical name DMZSvrIntOAMAddr and theIP address of the DMZ Server that you are using.

d. Click Apply.

2. Create a DMZ server:

a. In the navigation pane of the Element Manager Console, select Servers.b. In the Servers window, click Add (+).c. In the Add Server dialog box, complete the following fields:

• Short Name• Long Server Name• Physical Site• IPv4 Internal OAM (Default) Address: Select the IP address that you specified in Step

1.• Operating System: Select Linux.

d. Click Apply.


Migrating the Collaboration Agent Manager to the DMZAbout this taskUse this task to move the Collaboration Agent to the DMZ.

If this is an SMB or medium deployment, the Provisioning Manager also provides CollaborationAgent services. In this case, you must create new Collaboration Agent instance on the DMZ server.

Procedure1. If this is a large deployment, stop and undeploy the Collaboration Agent network element,

otherwise stop the Provisioning Manager network element.

For more information, see Stopping a network element instance on page 43 and Undeploying a network element instance on page 154.

2. If this is a large deployment, change the server for the Collaboration Agent instance to thenew server. If this is an SMB or medium deployment, skip this step.



Migrating the Collaboration Agent Manager to the DMZ




d. In the Edit <Collaboration Agent network element> Instance dialog, select the WebServer from the Server list. For example, DMZServer.

e. Click Apply.

3. If this is an SMB or medium deployment, add new a new Collaboration Agent networkelement. If this is a large deployment, skip this step.

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Collaboration Agent Managers.

b. Click Add (+).

c. Enter information in all of the required details.

d. Click Apply to confirm.

e. In the navigation pane of the Element Manager Console, select Feature ServerElements > Collaboration Agent Managers > <Created Collaboration Agent> >Instance.

f. Click Add (+).

g. Enter information in all of the required details.

h. In the Add <Collaboration Agent network element> Instance dialog, select the WebServer from the Server list. For example, DMZServer.

i. Click Apply to confirm.

4. Change the certificate configured for the Collaboration Agent HTTPS Certificate inaccordance with the guidelines for certificate configuration.


5. Deploy the Collaboration Agent network element.

For more information, see Deploying a Network Element instance on page 82.

6. If this is a large deployment, start the network element. If this is an SMB or mediumdeployment, start the Collaboration Agent and Provisioning Manager network elements.

For more information, see Starting a network element instance on page 156.



8. Repeat this procedure for any additional Collaboration Agent network elements.






Migrating the Web Conferencing Server to the DMZBefore you beginEnsure that you acquire new IPv4 addresses for each Web Conferencing Server service address onthe subnet to which the Web Conferencing Server is moving.

About this taskIf you have a deployment that has the Web Conferencing Server in the internal network, use thistask to move the Web Conferencing Server to the DMZ.

Procedure1. Stop all instances of the Web Conferencing Servers (WCS) in the Web Conferencing Server

cluster.


2. Undeploy all Web Conferencing Server instances.


3. Change the servers for the Web Conferencing Server instances to the Avaya Aura®

Conferencing servers in the DMZ For example, in an SMB simplex deployment, change theserver configuration for the Web Conferencing Server network element instance toDMZServer.

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Web Conferencing > <Web Conferencing Servers and Clusters > WebConferencing Servers > <Web Conferencing Server network element> >Instances.

b. In the <Web Conferencing Server> Instance dialog, select the Web ConferencingServer network element instance.

c. Click Edit (-/+).d. In the Edit <Web Conferencing Server> Instance, select the destination Avaya Aura®

Conferencing server from the Server list. For example, DMZServer.

e. Click Apply.


4. Change the Web Conferencing Server address for each Web Conferencing Server in thecluster.


b. Select the row from the Addresses frame for the current Web Conferencing Serverservice address.

c. Click Edit (-/+).d. Modify the IPv4 address to be the new IPv4 address for the Web Conferencing Server

service address.

Migrating the Web Conferencing Server to the DMZ



e. Click Apply.

5. Change the certificate configured for the Web Conferencing Server in accordance with theguidelines for certificate configuration.


6. Deploy and start the Web Conferencing Server network elements.




8. Repeat the above steps to move any other Web Conferencing Server clusters.






Chapter 7: Migrating the Web ConferencingManagement Server (WCMS) tothe enterprise

Note:

This procedure only applies if you have a large deployment that uses a Demilitarized Zone(DMZ). It applies to deployments that have redundancy and also to deployments that do nothave redundancy (simplex layouts).

For the Avaya Aura® Conferencing 7.0 release, the WCMS resided on a separate server in theDMZ. From the Avaya Aura® Conferencing 7.2+ release onwards, Avaya moved the WCMS fromthe separate server in the DMZ to the Element Manager (EM) server in the enterprise. If you havean SMB or medium deployment that uses a DMZ, the WCMS is already on the EM server.

After you move the WCMS to the enterprise, you must update the synchronization between the twoWCMS instances. For more information, see Updating the Web Conferencing Management Serverresync on page 154.



Figure 3: Avaya Aura® Conferencing deployment layout prior to the 7.2 timeframe

Figure 4: Avaya Aura® Conferencing deployment layout from 7.2 onwards (including 8.0)

About this taskUse this task to move the WCMS from a separate server in the DMZ to the EM server in theenterprise.

Migrating the Web Conferencing Management Server (WCMS) to the enterprise



Procedure1. Stop all running WCMS, Web Conferencing Server (WCS), Personal Agent (PA), and

Provisioning Agent (PROV) network element instances.

See Stopping a network element instance on page 43.

2. Undeploy all WCMS network element (NE) instances.

See Undeploying a network element instance on page 154.

3. Change the servers for WCMS network element instances to EM servers.

For example, in the case of a standalone simplex layout, the new value will be EMServer1.

a. In the EM graphic user interface (GUI), navigate to Feature Server Elements > WebConferencing Management Servers > <WCMS NE> > Instance.

b. Select the WCMS NE instance.

c. Click +/- (Edit).

d. On the resulting dialog, select the EM server and click Apply.

4. Deploy all WCMS NE instances.

See Deploying a Network Element instance on page 82.

5. Change the certificate required for the WCMS in accordance with the guidances forcertificate configuration.

For more information about security and Avaya Aura® Conferencing, see Deploying AvayaAura® Conferencing, which is available on https://support.avaya.com/.

6. Change the meeting event processor to Provisioning Manager.

See Configuring the meeting event processor for the Web conferencing managementserver on page 156.

7. Ensure that TCP port 8444 is open between the DMZ and the enterprise to allow connectivitybetween the Collaboration Agent and the WCMS.


8. Start all stopped WCMS, WCS, PA, and PROV network element instances.

See Starting a network element instance on page 156.

Related LinksUpdating the Web Conferencing Management Server (WCMS) Rsync configuration on page 154Undeploying a network element instance on page 154Deploying a network element instance on page 82Configuring the meeting event processor for the Web conferencing management server onpage 156Starting a network element instance on page 156Cleaning up the library files on page 157





Updating the Web Conferencing Management Server(WCMS) Rsync configuration

About this taskUse this task to update Web Conferencing Management Server (WCMS) rsync configuration.

Procedure1. Log on to the secondary Element Manager server as a user with the SSA role (for example,

ntsysadm) through ssh or directly at the server console.



4. At the prompt, type su – rsyncappsw and press Enter.

5. At the prompt, type ssh-keygen -R XXX.XXX.XXX.XXX, where XXX.XXX.XXX.XXX is IPaddress of the secondary Element Manager server, and press Enter.

6. At the prompt, type ssh-keyscan -t rsa XXX.XXX.XXX.XXX >> /home/rsyncappsw/.ssh/known_hosts, where XXX.XXX.XXX.XXX is IP address of thesecondary Element Manager server, and press Enter.

ResultWeb Conferencing Management Server rsync configuration is updated.


Related LinksMigrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151

Undeploying a network element instanceAbout this taskUse this procedure to undeploy a network element instance.


<network element type> > <network element instance you want to stop> > NEMaintenance.





3. Click Undeploy.

The Maint state changes from None to Undeploying, indicating that the undeploy operationis in progress. When the undeploy operation is complete, the Maint state changes back toNone.


ResultThe network element instance is undeployed.



Deploying a network element instanceAbout this taskUse this procedure to deploy a network element instance.


<Network Element type> > <Network Element instance you want to deploy > NEMaintenance.


3. Click Deploy.

The Maint state changes from None to Deploying, indicating that the deploy operation is inprogress. When the deploy operation is complete, the Maint state changes back to None,and the Admin state changes from Configured to Offline.


ResultThe Network Element instance is deployed.



Deploying a network element instance



Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151

Configuring the meeting event processor for the Webconferencing management server

About this taskUse the following procedure to configure the meeting event processor.


Web Conferencing > Web Conferencing Management Servers > <Web conferencingmanagement server name> > Meeting Event Processing.

2. From the Meeting Event Processor box, select the Provisioning Manager or CollaborationAgent for managing meeting events.

3. Click Apply.


Starting a network element instanceAbout this taskUse this procedure to start a network element instance.


2. 1. In the navigation pane of Element Manager Console, select Feature Server Elements ><network element type> > <network element instance you want to start> > NEMaintenance.


4. Click Start.

The Maint state changes from None to Starting, indicating that the restart operation is inprogress. When the restart operation is complete, the following state changes occur:

• The Maint state changes back to None.• The Admin state changes from Offline to Online.• The Link state changes from Down to Up.




• The Oper state changes from Unavailable to either Active or Hot Standby, based on theinstance of the component.


ResultThe network element instance is up and running.



Cleaning up the library filesBefore you beginEnsure that you have completed the resync. For more information, see Updating the WebConferencing Management Server resync on page 154.

About this taskUse this task to remove (or move) the old library files from the DMZ server.

Procedure1. Log on to the Web Conferencing server in the DMZ using an account with the AA role

(ntappadm).

2. Enter rm -rf /var/mcp/app/run/webcollab/library/*.

ResultThis command removes the old library files from the server.



Cleaning up the library files



Chapter 8: Adding redundancy to yoursolution

Expanding from a medium non-redundant deployment to amedium redundant deployment

If you have an SMB or a medium Avaya Aura® Conferencing solution without any redundancy, youcan add redundancy by following the procedures in this section.

A deployment without redundancy is also called a simplex deployment.

These procedures are relevant for SMB or medium-sized deployments.

Related LinksReference configurations for medium enterprises on page 158Checklist for expanding an SMB or medium non-redundant deployment to a redundantdeployment on page 160Adding secondary Element Manager server and secondary media and Web conferencing serverhosts on page 162Adding secondary Element Manager server hosts on page 163Installing and configuring a secondary database instance on page 164

Reference configurations for medium enterprisesThere are two configurations for Avaya Aura® Conferencing:

• Medium simplex

• Medium with redundancy

A redundant configuration incurs additional costs, which the simplex solution does not incur.Medium enterprises require the following to support redundancy:

• A second server

• An ADC, which provides load-balancing



Figure 5: Medium Simplex Configuration

Figure 6: Medium Redundant Configuration

Related LinksExpanding from a medium non-redundant deployment to a medium redundant deployment onpage 158

Expanding from a medium non-redundant deployment to a medium redundant deployment



Checklist for expanding an SMB or medium non-redundantdeployment to a redundant deployment



Conferencing server ifthey are used



Conferencing platform onthe secondary ElementManager server

Installing the platform onpage 49

3 Install the Avaya MediaServer (MS) platform onthe secondary ElementManager server


4 Add the secondaryElement Managerserver host

Adding secondary ElementManager server hosts onpage 163

5 Stop all the networkelement instances exceptthe Element Manager


6 Add and deploysecondary networkelement instances on thesecondary ElementManager server:

• Provisioning Manager

• Web ConferencingManagement Server

• Document ConversionServer

• Web ConferencingServer

• Media Server

• Element Manager

• Accounting Manager

• Application Server

For more information, seeDeploying Avaya Aura®

Conferencing andAdministering Avaya Aura®

Conferencing, which areavailable from the AvayaSupport website:http://www.avaya.com/support

Adding redundancy to your solution






7 Create and assign newcertificates to all newnetwork elementinstances


Conferencing, which isavailable from the AvayaSupport website:http://www.avaya.com/support

8 Add and configure newMedia Server to existingMedia Server cluster

For more information, seeAdministering Avaya Aura®


9 Add and configure newWeb ConferencingServer to existing WebConferencing Servercluster



10 Stop an ElementManager instance


11 Install and configuresecondary databaseinstance

Installing and configuring asecondary databaseinstance on page 164

12 Start all the networkelement instances


Starting an ElementManager instance from theserver console onpage 125

13 Configuring WebConferencingManagement ServerRsync



14 Configure Audio/Video inCollaboration Agent onthe Secondary ElementManager Server



15 Configure ACL rules onAvaya Aura®

Conferencing server to
















reflect network topologychanges if they wereused

16 Verify that the AvayaAura® Conferencingsystem is operatingcorrectly



Adding secondary Element Manager server and secondary mediaand Web conferencing server hosts

About this taskUse this task to add a secondary Element Manager server and secondary media and Webconferencing server hosts.

Procedure1. In the navigation pane of Element Manager Console, select Addresses.


3. In the Add IPv4 Address dialog box, enter the logical name EMSvr2IntOAMAddr and IPaddress of the secondary Element Manager server.

4. Click Apply.

5. Repeat these steps to add new IP addresses for the secondary media and Webconferencing server with the logical name MWCSvr2IntOAMAddr.

6. Repeat the steps again to add a service IP address for the secondary Webconferencing server with the logical name WCS2SvcAddr.

7. Repeat the steps once again to add a media IP address for the secondary media server withthe logical name MWCSrv2MediaAddr.

8. In the navigation pane of Element Manager Console, select Servers.

9. In the Servers window, click Add (+).

10. In the Add Server dialog box, complete the following fields:

• Short Name: EMS2

• Long Server Name: EMServer2

• Physical Site:




• Internal OAM (Default) Address: EMSvr2IntOAMAddr• Operating System: linux.

11. Click Apply .



• Short Name: MWCS2• Long Server Name: MWCServer2• Physical Site:• Internal OAM (Default) Address: MWCSvr2IntOAMAddr• IPv4 Media Address: MWCSrv2MediaAddr• Operating System: linux

14. Click Apply.



Adding secondary Element Manager server hostsAbout this taskUse this task to add a secondary Element Manager server host.



3. In the Add IPv4 Address dialog box, enter the logical name EMSvr2IntOAMAddr and IPaddress of the secondary Element Manager server.

4. Click Apply.

5. Repeat the steps to add a service IP address for the secondary Webconferencing server with the logical name WCS2SvcAddr.

6. Repeat the steps again to add a media IP address for the secondary media server with thelogical name MWCSrv2MediaAddr.







• Short Name: EMS2

• Long Server Name: EMServer2

• Physical Site:

• Internal OAM (Default) Address: EMSvr2IntOAMAddr• IPv4 Media Address: MWCSrv2MediaAddr• Operating System: linux.

10. Click Apply .



Installing and configuring a secondary database instanceAbout this taskUse this task to install and configure a secondary database instance.

Procedure1. Login to the Primary EM server as the ntappadm user via SSH.

2. Change the directory: cd to the /var/mcp/install directory.

3. Run the ./populateInstallpropsFile.pl script.

4. Leave all properties unchanged except the following:

• Database Type: REPLICATED

• Secondary Database Host Address: IP address of the secondary server

5. Run mcpDbSwInstall –secondary to install the database software to the secondaryserver.

6. Run the ./setupDBReplication.pl script.

7. In the navigation pane of Element Manager Console, select Feature Server Elements >Database > mcpdb > Configuration.

8. In the mcpdb Configuration window, click Add (+).

9. In the Add Database Instance dialog box, complete the following field:

• Server: Your secondary server






Expanding from a large non-redundant deployment to alarge redundant deployment

If you have a large Avaya Aura® Conferencing solution without any redundancy, you can addredundancy by following the procedures in this section.


These procedures are relevant for large-sized deployments.

Related LinksReference configurations for large enterprises on page 165Checklist for expanding a large non-redundant deployment to a redundant deployment on page 167

Reference configurations for large enterprisesThere are two configurations for Avaya Aura® Conferencing:

• Large simplex

• Large with redundancy

A redundant configuration incurs additional costs, which the simplex solution does not incur. Largeenterprises require the following to support redundancy:

• A second server

• An ADC, which provides load-balancing

Additionally, customers have the option of expanding their system to support up to 30,000 users,running 3000 concurrent sessions, by adding additional servers. This expansion can continue up toa maximum of 150,000 users.

Expanding from a large non-redundant deployment to a large redundant deployment



Figure 7: Large Simplex Configuration




Figure 8: Large Redundant Configuration

Related LinksExpanding from a large non-redundant deployment to a large redundant deployment on page 165

Checklist for expanding a large non-redundant deployment to aredundant deployment






Conferencing platform onthe secondary ElementManager server and onthe secondary Media and

Installing the platform onpage 49





Web Conferencingserver

3 Install Avaya MediaServer (MS) platform onthe secondary Media andWeb Conferencingserver


4 Add the secondaryElement Managerserver & secondaryMedia and WebConferencing serverhosts

Adding secondary ElementManager server andsecondary media and Webconferencing serverhosts on page 162

5 Stop all the networkelement instances exceptthe Element Manager


6 Add and deploysecondary networkelement instances on thesecondary ElementManager server:

• Provisioning Manager

• Web ConferencingManagement Server

• Document ConversionServer

• Element Manager

• Accounting Manager

• Application Server


Conferencing andAdministering Avaya Aura®

Conferencing, which areavailable from the AvayaSupport website:http://www.avaya.com/support

7 Add and deploysecondary networkelement instances on thesecondary Media andWeb conferencingserver:

• Web ConferencingServer

• Media Server



8 Create and assign newcertificates to all newnetwork elementinstances


Conferencing, which isavailable from the Avaya









Support website:http://www.avaya.com/support

9 Add and configure newMedia Server to existingMedia Server cluster



10 Add and configure newWeb ConferencingServer to existing WebConferencing Servercluster



11 Stop an ElementManager instance


12 Install and configure thesecondary databaseinstance

Installing and configuring asecondary databaseinstance on page 164

13 Start all the networkelement instances


Starting an ElementManager instance from theserver console onpage 125

14 Configuring WebConferencingManagement ServerRsync



15 Configure Audio/Video inCollaboration Agent onthe Secondary ElementManager Server




Conferencing server toreflect network topologychanges if they wereused


















Related LinksExpanding from a large non-redundant deployment to a large redundant deployment on page 165




Chapter 9: Upsizing your solution

Expanding from a medium to a large deployment (withoutredundancy)

If you have an SMB or a medium Avaya Aura® Conferencing solution without any redundancy, youcan expand your system to a large solution by following the procedures in this section.



Figure 9: Medium Simplex Configuration



Figure 10: Large Simplex Configuration

Related LinksChecklist for expanding a medium simplex deployment to a large simplex deployment on page 173Adding media and Web conferencing servers on page 174Adding media and Web conferencing server hosts on page 174Changing engineering parameters for a network element instance on page 175Changing engineering parameters in the database on page 176Moving an Avaya Media Server (MS) network element to a new server on page 177Moving a Web conferencing Server network element to a new server on page 178

Upsizing your solution



Checklist for expanding a medium simplex deployment to a largesimplex deployment





2 Back up conferencingrecordings



3 Add the Media and WebConferencing servers

Adding media and Webconferencing servers onpage 174

4 Change the engineeringparameters in thedatabase

Changing engineeringparameters in thedatabase on page 176

5 Change the engineeringparameters for all theremaining networkelement instances

Changing engineeringparameters for a networkelement instance onpage 175

6 Restore conferencingrecordings








Related LinksExpanding from a medium to a large deployment (without redundancy) on page 171

Expanding from a medium to a large deployment (without redundancy)







Adding media and Web conferencing serversAbout this taskUse the following checklist to configure and deploy additional media and Web conferencing servers.

Table 5: Checklist for adding additional media and Web conferencing servers

Number Task Description1 Install the Avaya Aura® Conferencing platform

on the additional server.Installing the platform on page 49

2 Install the Avaya Media Server (MS) platformon the additional server.

Installing Avaya Media Server on page 64

3 Add the additional media and Webconferencing server host.

Adding media and Web conferencing serverhosts on page 174

4 Move a Web conferencing server networkelement to the new server.

Moving a Web conferencing Server networkelement to a new server on page 178

5 Move an Avaya Media Server (MS) networkelement to the new server.

Moving an Avaya media server networkelement to a new server on page 177

6 Uninstall the Avaya Media Server (MS)platform software from the Element Managerserver.

See Deploying Avaya Aura® Conferencing8.0, which is available from https://support.avaya.com/.



Adding media and Web conferencing server hostsAbout this taskUse this task to add additional media and Web conferencing server hosts.



3. In the Add IPv4 Address dialog box, enter the logical name and IP address for the serveron which the media and Web conferencing server software will be installed.

4. Click Apply.

5. Repeat the steps to add a service IP address for the Web conferencing server.






6. Repeat the steps again to add a media IP address for the media server.




• Short Name:

• Long Server Name:

• Physical Site:

• Internal OAM (Default) Address: Select the IP address you specified in step 3.

• IPv4 Media Address: Select the IP address you specified in step 6.

• Operating System: linux.

10. Click Apply .



Changing engineering parameters for a network element instanceAbout this taskUse this task to change the engineering parameters for a network element instance.

Procedure1. Stop the network element instance.


2. Undeploy the network element instance.


3. Change the engineering parameters for the network element instance:

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > <Network Element type> > <Network Element> > Instances.

b. In the <NE> Instance dialog, select the network element instance.


d. In the Edit <NE> Instance dialog , update the engineering parameters in theEngineering list.

e. Click Apply.




4. Deploy and start the media server network element instance.




Changing engineering parameters in the databaseAbout this taskUse this task to update the engineering parameters in the database.

Procedure1. Log on to the primary Element Manager as a user with the AA role (for example, ntappadm)

through SSH or directly at the server console.



The list of available loads is displayed.

Avaya Aura® Conferencing 8.0 loads have the filename MCP_18.x.x.xx_2013-xx-xx-xxxx.zip.

4. Select the load you want to use and press Enter.

The list of available engineering parameters is displayed.

5. Select the engineering parameters you want to use and press Enter.

6. At the prompt, type mcpUpgradeMR.pl and press Enter.

The list of available loads is displayed.

7. Select the load you want to use and press Enter.

8. Type the number of the load you want to use, and press Enter.

The following message is displayed and the upgrade starts for the MCP database andElement Manager:––- Invoking mcpUpgrade => to upgrade the EM & Database –––

Note:

If the upgrade message is not displayed, stop and contact Avaya support.




Once the upgrade of the MCP database and Element Manager is complete, the followingmessage is displayed:––- EM & DataBase Upgrade Complete –––



Moving an Avaya Media Server (MS) network element to a newserver

About this taskUse this task to move an Avaya Media Server (MS) network element to a new server.

Procedure1. Stop the Avaya Media Server (MS) network element instance.


2. Undeploy the Avaya Media Server (MS) network element instance.


3. Change the server for the media server instance:

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Media Servers and Clusters > Media Servers > <Media server networkelement> > Instances.

b. In the <Media server network element> Instance dialog, select the media servernetwork element instance.


d. In the Edit <Media server network element> Instance dialog, select the new mediaand Web conferencing server from the Server list.

e. In the Edit <Media server network element> Instance dialog, update the engineeringparameters in the Engineering list.

f. Click Apply.

4. Change the certificate configured for the Avaya Media Server (MS) HTTPS Certificate inaccordance with the guidelines for certificate configuration.


5. Deploy and start the Avaya Media Server (MS) network element.







Moving a Web conferencing Server network element to a newserver

About this taskUse this task to move a Web conferencing server network element to a new server.

Procedure1. Stop the Web Conferencing Servers (WCS) network element instance.


2. Undeploy the WCS network element instance.


3. Change the server for the WCS instance:

a. In the navigation pane of the Element Manager Console, select Feature ServerElements > Web Conferencing > Web Conferencing Servers and Clusters > WebConferencing Servers > <Web Conferencing network element> > Instances.

b. In the <Web Conferencing network element> Instance dialog, select the WCSnetwork element instance.

c. Click Edit (-/+).d. In the Edit <Web Conferencing network element> Instance dialog, select the new

media and Web conferencing server from the Server list.e. In the Edit <Web Conferencing network element> Instance dialog, update the

engineering parameters in the Engineering list.f. Click Apply.

4. Update the WCS server address for the WCS instance.

a. In the navigation pane of the Element Manager Console, select Addresses.b. Select the row from the Addresses frame for the current WCS sService address.c. Click Edit (-/+).d. Modify the IPv4 address to be the new IPv4 address for the WCS service address.e. Click Apply.




5. Change the certificate configured for the WCS HTTPS Certificate in accordance with theguidelines for certificate configuration.


6. Deploy and start the WCS network element.


Additionally, see Deploying Avaya Aura® Conferencing 8.0, which is available on http://support.avaya.com/.



Expanding from a medium to a large deployment (withredundancy)

If you have an SMB or a medium Avaya Aura® Conferencing solution with redundancy, you canexpand your system to a large solution by following the procedures in this section.


Expanding from a medium to a large deployment (with redundancy)





Figure 11: Medium Redundant Configuration

Figure 12: Large Redundant Configuration




Related LinksChecklist for expanding a medium redundant deployment to a large redundant deployment onpage 181

Checklist for expanding a medium redundant deployment to alarge redundant deployment





2 Back up conferencingrecordings



3 Add primary Media andWeb Conferencingservers


4 Add secondary Mediaand Web Conferencingservers


5 Change the engineeringparameters in thedatabase

Changing engineeringparameters in thedatabase on page 176

6 Change the engineeringparameters for all theremaining networkelement instances

Changing engineeringparameters for a networkelement instance onpage 175

7 Restore conferencingrecordings






Expanding from a medium to a large deployment (with redundancy)










Related LinksExpanding from a medium to a large deployment (with redundancy) on page 179




Appendix A: Overview of automaticdisaster recovery

Avaya Aura® Conferencing supports automatic disaster recovery (ADR). Typically, ADR meanshaving a second, replica system to which you can switch operations in the event of a failure on theprimary, main system. Typically, the secondary system is geographically separated from the primarysystem. The ADR feature operates using the following simple layout:

• A primary Avaya Aura® Conferencing system is installed and operates normally.

• A secondary Avaya Aura® Conferencing system is installed. It is a replica of the primarysystem, with the exception of IP addresses, hostnames, and so on. In certain configurations,the Avaya Media Server (MS) resources can be shared across the two sites.

• The primary system sends regular updates to the secondary system, to ensure datasynchronization. This time interval is configurable and varies according to system size.

In the event of a failure at the primary site, the following occurs:

• All current calls/sessions are dropped.

• The secondary system takes over.

• Users must restart their calls/sessions.

• Administrators must investigate the failure at the primary site and manually reinstate theprimary site when it is repaired.

To ensure a smooth, automatic transition to the secondary site, you must perform someconfiguration tasks on Avaya Aura® Session Manager and the Avaya Media Server (MS) resourcesin advance. In addition, you must add the secondary site URL addresses to the users’ DomainName Server (DNS). Automatic transition is not supported on Avaya Aura® System Manager.System Manager handles a more fixed type of data and an automatic transition is not required fornormal service to resume. However, if you intend to switch to the secondary system for a prolongedperiod of time, you must manually configure the details of the secondary servers on the SystemManager interface.



Example layouts

Figure 13: An example of an installation of ADR

Overview of automatic disaster recovery



Figure 14: An example of ADR under normal operations

Related LinksImplications of virtualization for automatic disaster recovery on page 185System service state on page 186

Implications of virtualization for automatic disasterrecovery

If you are using virtualization (VMWare) to deploy Avaya Aura® Conferencing, there are implicationsfor automatic disaster recovery (ADR). ADR deployments on VMWare need to use platform OVAsfor all deployment models.

Related LinksOverview of automatic disaster recovery on page 183

Implications of virtualization for automatic disaster recovery



System service stateThe concept of a system service state is a key concept to automatic disaster recovery (ADR). Thereare two system service states:

• Locked

• Unlocked

These two states equate to concepts such as online/offline, functional/not functional, or active/inactive. When Avaya Aura® Conferencing is unlocked, it is operational and providing aconferencing service. When Avaya Aura® Conferencing is locked, it is not operational and is notproviding a conferencing service.

Related LinksOverview of automatic disaster recovery on page 183

Overview of automatic disaster recovery



Appendix B: Fixing remote host SSH keys

About this taskWhen an SSH session is created for the first time, the remote servers public key is stored in /root/.ssh/known_hosts. If this key changes for any reason (a server reinstall is the primaryreason), then SSH will not allow a connection to continue until that key is manually removed fromthe known_hosts file.

If the following warning is displayed when running the mcpInstIntACLConf scripts, the file /root/.ssh/known_hosts must be modified before the SSH connection to the remote server willsucceed:WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IT IS POSSIBLE THATSOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on youright now (man-in-the-middle attack)! It is also possible that the RSAhost key has just been changed. The fingerprint for the RSA key sent bythe remote host is 60:75:7a:9e:af:88:85:e7:c7:3d:82:d6:c5:7e:a8:a8.Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message.To modify the file /root/.ssh/known_hosts, perform this task on the server where the script isbeing run.

Procedure1. Log onto the server as an SSA user.

2. At the command prompt, enter su - and press Enter.

3. Enter the root password and press Enter.

4. Edit the file /root/.ssh/known_hosts.

Each line in this file has an IP address followed by the public key for that IP address.

5. Delete the line for the remote server.

6. Save the file.

7. Once the file has been modified, retry the script from the same server.



Index

AAAC-hosted licensing

install ............................................................................ 67ACL ....................................................................................108

configuring .................................................................... 99ACL rules ............................................. 99–101, 103, 105, 108adding new servers ............................................................163adding redundancy ............................................................ 158additional server hosts .......................................................174additional servers ...............................................................174administration

related documentation .................................................. 10ADR

overview ..................................................................... 183state ............................................................................186VMWare ......................................................................185

allow bandwidth management ........................................... 135Apple Safari ......................................................................... 18application bundle ................................................................61automatic disaster recovery

overview ..................................................................... 183state ............................................................................186

AViCA ............................................................................ 36, 80

Bbacking up

conference recordings .................................................. 37database .................................................................39, 79flash media gateways ............................................. 36, 80FMG ........................................................................36, 80media server .................................................................36servers ..........................................................................40

bandwidth management ...................................................... 98BIOS

modifying clock ............................................................. 52

Ccertificate configuration ......................................................114certificates ..................................................................124, 125

application server ....................................................... 121Avaya Media Server ................................................... 122Collaboration Agent Manager .....................................120Element Manager ....................................................... 118network elements ....................................................... 116Provisioning Manager .................................................119WCS ........................................................................... 123

checklistadding redundancy ............................................. 160, 167

Chrome ................................................................................ 18cleaning up .......................................................................... 41

Collaboration Agent Manager ............................................ 147components ......................................................................... 30conference recordings ......................................................... 37configurations ............................................................ 158, 165

Ddatabase .................................................................. 39, 63, 79

replication ............................................................... 71, 91single ...................................................................... 90, 91

database software ............................................................... 62DCS

certificates .................................................................. 125disaster recovery ............................................................... 183

state ............................................................................186DMZ ................................................................... 138, 140, 146

EElement Manager ................................................................ 44End Entity .......................................................................... 133engineering parameters .............................................175, 176enrollment password ..........................................................116enterprise solution ............................................................. 145extracting ............................................................................. 61

FFirefox ..................................................................................18Fixing remote host SSH keys ............................................ 187Flash Media Gateway

configuring a secure SIP TLS connection to SessionManager ..................................................................... 134

flash media gateways .................................................... 36, 80FMG ...............................................................................36, 80

restoring ........................................................................68

GGoogle Chrome ................................................................... 18growing your system ..................................................171, 179

Hhardware environment ......................................................... 52HP Proliant DL360 G8 ......................................................... 19

Iidentity certificate

Flash Media Gateway .................................................133



implementationrelated documentation .................................................... 9

import.dat ...........................................................................113installing

database .......................................................................63Element Manager ......................................................... 64

installing WebLM ................................................................. 67intelligent workbook ....................................................... 15, 49Internet Explorer .................................................................. 18

Kkilling

network element ........................................................... 81

LLinux

installing ........................................................................49

MMAC OS ...............................................................................18media server .......................................................... 36, 64, 102medium to large ......................................................... 173, 181move media server ............................................................ 177moving web conferencing server ....................................... 178Mozilla Firefox ......................................................................18

Nnetwork element instance ...................................... 43, 65, 154

deploying .............................................................. 82, 155Network Element instance

starting ..........................................................................83NTP clock

configuration ................................................................. 56

Oonline help ........................................................................... 12overview .................................................................................8

related documentation .................................................... 9

Pplatform ................................................................................45PostgreSQL ......................................................................... 42

Rrecordings ............................................................................ 67redundant

Element Manager ......................................................... 26non-primary Element Manager ..................................... 28

related documentationadministration ............................................................... 10implementation ............................................................... 9overview ......................................................................... 9supporting .....................................................................10

related resourcestraining ..........................................................................11

remote backup parameters ..................................................42replication errors .................................................................. 71restoring ...............................................................................60restoring server ....................................................................59resync ................................................................................ 154re-syncing the database ...................................................... 70

SSafari ................................................................................... 18secondary database instance ............................................ 164secondary EM ....................................................................163secondary media servers ...................................................162server migration ................................................................... 30server replacement .............................................................. 63

introduction ................................................................... 21redundant ..................................................................... 26requirements .................................................................21simplex ......................................................................... 22

servers ................................................................................. 40Session Manager .................................................................97simplex

Element Manager ......................................................... 22non-Element Manager .................................................. 24

single sign-on .....................................................................129SSH keys ............................................................................. 38starting

network element ......................................................... 156support .................................................................................14supporting

related documentation .................................................. 10syslog server

configuration ................................................................. 58system configuration

configuration ................................................................. 53system default settings ...................................................... 135System Manager ..................................................................96

Ttesting .................................................................................. 68TLS

configuring for the Flash Media Gateway ................... 134guidelines ................................................................... 114

tools package .......................................................................80training

related resources ..........................................................11turnkey ................................................................................. 93

Index



Uunneeded files ..................................................................... 41unneeded installers ..............................................................42USB restore ......................................................................... 47user password owned locally .............................................135

Vverification ............................................................................68videos .................................................................................. 11virtualization

ADR ............................................................................ 185VMware ................................................................................73

WWCMS ............................................................................... 151

resync ......................................................................... 154WCS .................................................................................. 142web browser ........................................................................ 18web conferencing

modifying the meeting event processor for amanagement server ....................................................156

Web Conferencing Server ................................................. 149WebLM ................................................................................ 98

install ............................................................................ 67Windows 7.0 ........................................................................ 18Windows XP ........................................................................ 18

Index



Date post:	03-Dec-2015
Category:	Documents
Upload:	octavio-puente
View:	30 times
Download:	1 times

Migrating Avaya Aura® Conferencing 8

Documents