Transcript
Migrating Avaya Aura® Conferencing
Release 8.0
04-604403
Issue 1
August 2014
© 2014 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this
document without the obligation to notify any person or organization
of such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating
instructions and performance specifications that Avaya may generally
make available to users of its products and Hosted Services.
Documentation does not include marketing materials. Avaya shall not
be responsible for any modifications, additions, or deletions to the
original published version of documentation unless such
modifications, additions, or deletions were performed by Avaya. End
User agrees to indemnify and hold harmless Avaya, Avaya's agents,
servants and employees against all claims, lawsuits, demands and
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the
extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or documentation provided by
Avaya. Avaya is not responsible for the accuracy of any information,
statement or content provided on these sites and does not
necessarily endorse the products, services, or information described
or offered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked
pages.
Warranty
Avaya provides a limited warranty on Avaya hardware and software.
Refer to your sales agreement to establish the terms of the limited
warranty. In addition, Avaya’s standard warranty language, as well as
information regarding support for this product while under warranty is
available to Avaya customers and other parties through the Avaya
Support website: http://support.avaya.com or such successor site as
designated by Avaya. Please note that if you acquired the product(s)
from an authorized Avaya Channel Partner outside of the United
States and Canada, the warranty is provided to you by said Avaya
Channel Partner and not by Avaya.
MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
SERVICE. YOUR USE OF THE HOSTED SERVICE SHALL BE
LIMITED BY THE NUMBER AND TYPE OF LICENSES
PURCHASED UNDER YOUR CONTRACT FOR THE HOSTED
SERVICE, PROVIDED, HOWEVER, THAT FOR CERTAIN HOSTED
SERVICES IF APPLICABLE, YOU MAY HAVE THE OPPORTUNITY
TO USE FLEX LICENSES, WHICH WILL BE INVOICED
ACCORDING TO ACTUAL USAGE ABOVE THE CONTRACT
LICENSE LEVEL. CONTACT AVAYA OR AVAYA’S CHANNEL
PARTNER FOR MORE INFORMATION ABOUT THE LICENSES
FOR THE APPLICABLE HOSTED SERVICE, THE AVAILABILITY
OF ANY FLEX LICENSES (IF APPLICABLE), PRICING AND
BILLING INFORMATION, AND OTHER IMPORTANT
INFORMATION REGARDING THE HOSTED SERVICE.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS
APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
AND ANYONE ELSE USING OR SELLING THE SOFTWARE
WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
THESE TERMS AND CONDITIONS AND CREATE A BINDING
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
“Hosted Service” means a hosted service subscription that you
acquire from either Avaya or an authorized Avaya Channel Partner
(as applicable) and which is described further in Hosted SAS or other
service description documentation regarding the applicable hosted
service. If you purchase a Hosted Service subscription, the foregoing
limited warranty may not apply but you may be entitled to support
services in connection with the Hosted Service as described further
in your service description documents for the applicable Hosted
Service. Contact Avaya or Avaya Channel Partner (as applicable) for
more information.
Avaya grants you a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
applicable license will be a Designated System License. The
applicable number of licenses and units of capacity for which the
license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the documentation or other
materials available to you. “Software” means Avaya’s computer
programs in object code, provided by Avaya or an Avaya Channel
Partner, whether as stand-alone products, pre-installed , or remotely
accessed on hardware products, and any upgrades, updates, bug
fixes, or modified versions thereto. “Designated Processor” means a
single stand-alone computing device. “Server” means a Designated
Processor that hosts a software application to be accessed by
multiple users. “Instance” means a single copy of the Software
executing at a particular time: (i) on one physical machine; or (ii) on
one deployed software virtual machine (“VM”) or similar deployment.
Hosted Service
License types
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO UNDER
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR
IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
Designated System(s) License (DS). End User may install and use
each copy or an Instance of the Software only on a number of
Designated Processors up to the number indicated in the order.
Avaya may require the Designated Processor(s) to be identified in
the order by type, serial number, feature key, Instance, location or
other specific designation, or to be provided by End User to Avaya
through electronic means established by Avaya specifically for this
purpose.
Named User License (NU). You may: (i) install and use the Software
on a single Designated Processor or Server per authorized Named
User (defined below); or (ii) install and use the Software on a Server
so long as only authorized Named Users access and use the
Software. “Named User”, means a user or device that has been
expressly authorized by Avaya to access and use the Software. At
Avaya’s sole discretion, a “Named User” may be, without limitation,
designated by name, corporate function (e.g., webmaster or
helpdesk), an e-mail or voice mail account in the name of a person or
corporate function, or a directory entry in the administrative database
utilized by the Software that permits one user to interface with the
Software.
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, Hosted Service,
or hardware provided by Avaya. All content on this site, the
documentation, Hosted Service, and the Product provided by Avaya
including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
and other intellectual property laws including the sui generis rights
relating to the protection of databases. You may not modify, copy,
reproduce, republish, upload, post, transmit or distribute in any way
any content, in whole or in part, including any code and software
unless expressly authorized by Avaya. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express
written consent of Avaya can be a criminal, as well as a civil offense
under the applicable law.
Virtualization
Each product has its own ordering code and license types. Note that
each Instance of a product must be separately licensed and ordered.
For example, if the end user customer or Avaya Channel Partner
would like to install two Instances of the same type of products, then
two products of that type must be ordered.
Third Party Components
“Third Party Components” mean certain software programs or
portions thereof included in the Software or Hosted Service may
contain software (including open source software) distributed under
third party agreements (“Third Party Components”), which contain
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed
Linux OS source code (for those Products that have distributed Linux
OS source code) and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply is available
in the Documentation or on Avaya’s website at: http://
support.avaya.com/Copyright or such successor site as designated
by Avaya. You agree to the Third Party Terms for any such Third
Party Components
THIS PRODUCT IS LICENSED UNDER THE AVC PATENT
PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG
LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.
Note to Service Provider
The Product or Hosted Service may use Third Party Components
subject to Third Party Terms that do not allow hosting and require a
Service Provider to be independently licensed for such purpose. It is
your responsibility to obtain such licensing.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If you suspect that you are being victimized by Toll Fraud and you
need technical assistance or support, call Technical Service Center
Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
States and Canada. For additional support telephone numbers, see
the Avaya Support website: http://support.avaya.com or such
successor site as designated by Avaya. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to:
[email protected].
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and Product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, or other third parties. Users are not permitted to use such
Marks without prior written consent from Avaya or such third party
which may own the Mark. Nothing contained in this site, the
Documentation, Hosted Service(s) and Product(s) should be
construed as granting, by implication, estoppel, or otherwise, any
license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: http://support.avaya.com, or such successor site as
designated by Avaya.
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com for Product
or Hosted Service notices and articles, or to report a problem with
your Avaya Product or Hosted Service. For a list of support telephone
numbers and contact addresses, go to the Avaya Support website:
http://support.avaya.com (or such successor site as designated by
Avaya), scroll to the bottom of the page, and select Contact Avaya
Support.
Contents
Chapter 1: An Introduction to Avaya Aura® Conferencing................................................... 8
About this document................................................................................................................ 8
Related resources................................................................................................................... 8
Documentation.................................................................................................................. 8
Training.......................................................................................................................... 11
Viewing Avaya Mentor videos........................................................................................... 11
Deploying online help...................................................................................................... 12
Support................................................................................................................................ 14
Audience.............................................................................................................................. 14
How to use this document...................................................................................................... 15
®
Preparing your data using the Avaya Aura Conferencing 8.0 Intelligent Workbook.............. 15
Administrative user roles and preconfigured accounts.............................................................. 16
Supported Web browsers....................................................................................................... 18
Supported hardware.............................................................................................................. 19
Chapter 2: Migrating servers................................................................................................. 21
Server replacement............................................................................................................... 21
Prerequisites for server replacement....................................................................................... 21
Server replacement for simplex deployments........................................................................... 22
Element Manager server replacement for simplex deployments.......................................... 22
Non-Element Manager server replacement for simplex deployments................................... 24
Server replacement for redundant deployments....................................................................... 26
Primary Element Manager server replacement for redundant deployments.......................... 26
Non-primary Element Manager server replacement for redundant deployments.................... 28
Determining which components are hosted on the server ........................................................ 30
®
Backing up Avaya Aura Conferencing for server replacement.................................................. 35
Backing up the Flash Media Gateway(s) for a feature pack................................................. 36
Backing up the Avaya Media Server (MS)......................................................................... 36
Backing up conference recordings.................................................................................... 37
Backing up the database for a feature pack, a service pack, or a patch................................ 39
®
Backing up the Avaya Aura Conferencing servers............................................................ 40
Stopping a network element instance...................................................................................... 43
Stopping an Element Manager instance.................................................................................. 44
Restoring the platform following server replacement................................................................. 44
Restoring the platform from a remote backup server.......................................................... 45
Restoring the platform from a USB drive........................................................................... 47
Installing the AAC Platform............................................................................................... 49
®
Restoring an Avaya Aura Conferencing server following server replacement............................ 59
®
Restoring an Avaya Aura Conferencing server................................................................. 60
Extracting the application bundle contents............................................................................... 61
Installing the database software.............................................................................................. 62
4
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Contents
Installing the database........................................................................................................... 63
Restoring the database following server replacement............................................................... 63
Installing Element Manager.................................................................................................... 64
Installing Avaya Media Server................................................................................................ 64
Restoring a network element instance during server replacement.............................................. 65
Restoring the recordings following server replacement............................................................. 67
Installing WebLM................................................................................................................... 67
Verifying the system.............................................................................................................. 68
Restoring a Flash Media Gateway (FMG)................................................................................ 68
Re-syncing the database data from the secondary instance...................................................... 70
Verifying that the secondary database is running and has no replication errors..................... 71
Setting up the database replication......................................................................................... 71
Chapter 3: Migrating from a bare metal solution to a virtualized solution........................ 73
Introduction........................................................................................................................... 73
Prerequisites......................................................................................................................... 73
Migrating from bare metal to VM for a medium simplex deployment........................................... 74
Backing up the database.................................................................................................. 79
Backing up the Flash Media Gateway(s)........................................................................... 80
Manually installing the VMware tools package................................................................... 80
Killing a network element instance.................................................................................... 81
Deploying a network element instance.............................................................................. 82
Starting a Network Element instance................................................................................. 83
Migrating from bare metal to VM for a medium redundant deployment....................................... 83
Setting the database type to single................................................................................... 90
Setting the database type to replicated.............................................................................. 91
Setting up the database replication................................................................................... 91
Chapter 4: Migrating from a turnkey solution to an Aura® solution.................................. 93
®
®
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full
®
Avaya Aura platform............................................................................................................. 93
®
Adding Avaya Aura System Manager to the Element Manager GUI................................... 96
®
Adding Avaya Aura Session Manager to the Element Manager GUI................................... 97
®
Changing the WebLM location to use Avaya Aura System Manager .................................. 98
Configuring Session Manager as the bandwidth management ASM for the application
server............................................................................................................................. 98
Configuring the access control list (ACL)........................................................................... 99
Guidelines for certificate configuration............................................................................. 114
Obtaining enrollment password from System Manager..................................................... 116
Creating Network Element certificates signed by System Manager.................................... 116
Assigning a new certificate to the Element Manager......................................................... 118
Assigning a new certificate to the Provisioning Manager................................................... 119
Assigning a new certificate to the Collaboration Agent Manager........................................ 120
Assigning a new certificate to the Application Server........................................................ 121
Assigning a new certificate to the Avaya Media Server..................................................... 122
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
5
Contents
Assigning a new certificate to the Web Conferencing Server............................................. 123
Assigning a new certificate to the Web Conferencing Management Server......................... 124
Assigning a new certificate to the DCS............................................................................ 125
Starting an Element Manager instance from the server console........................................ 125
Configuring single sign-on for Element Manager Console and Provisioning Client.............. 126
®
Configuring the route to Avaya Aura Conferencing on System Manager........................... 130
Creating a System Manager- signed certificate for the Flash Media Gateway IP address.... 133
®
Configuring a secure SIP TLS connection from the Flash Media Gateway to Avaya Aura
Session Manager.......................................................................................................... 134
®
Changing the system default settings to use Avaya Aura Conferencing (AAC).................. 135
Removing the dialing rules in Provisioning Client............................................................. 135
Removing all SIP entities for PBXs in Element Manager................................................... 136
Removing all the old certificates on Turnkey.................................................................... 136
Chapter 5: Migrating from a DMZ solution to an enterprise solution.............................. 138
®
Migrating Avaya Aura Conferencing components from the DMZ to the Enterprise................... 138
Migrating the Collaboration Agent Manager from the DMZ ..................................................... 140
Migrating the Web Conferencing Server from the DMZ........................................................... 142
Chapter 6: Migrating from an enterprise solution to a DMZ solution.............................. 145
Migrating from an enterprise solution to a DMZ solution.......................................................... 145
Adding a new DMZ server in the Element Manager GUI......................................................... 146
Migrating the Collaboration Agent Manager to the DMZ ......................................................... 147
Migrating the Web Conferencing Server to the DMZ .............................................................. 149
Chapter 7: Migrating the Web Conferencing Management Server (WCMS) to the
enterprise............................................................................................................................... 151
Updating the Web Conferencing Management Server (WCMS) Rsync configuration................. 154
Undeploying a network element instance............................................................................... 154
Deploying a network element instance.................................................................................. 155
Configuring the meeting event processor for the Web conferencing management server.......... 156
Starting a network element instance..................................................................................... 156
Cleaning up the library files.................................................................................................. 157
Chapter 8: Adding redundancy to your solution............................................................... 158
Expanding from a medium non-redundant deployment to a medium redundant deployment...... 158
Reference configurations for medium enterprises............................................................. 158
Checklist for expanding an SMB or medium non-redundant deployment to a redundant
deployment................................................................................................................... 160
Adding secondary Element Manager server and secondary media and Web conferencing
server hosts.................................................................................................................. 162
Adding secondary Element Manager server hosts ........................................................... 163
Installing and configuring a secondary database instance................................................. 164
Expanding from a large non-redundant deployment to a large redundant deployment............... 165
Reference configurations for large enterprises................................................................. 165
Checklist for expanding a large non-redundant deployment to a redundant deployment...... 167
Chapter 9: Upsizing your solution...................................................................................... 171
6
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Contents
Expanding from a medium to a large deployment (without redundancy)................................... 171
Checklist for expanding a medium simplex deployment to a large simplex deployment....... 173
Adding media and Web conferencing servers.................................................................. 174
Adding media and Web conferencing server hosts........................................................... 174
Changing engineering parameters for a network element instance.................................... 175
Changing engineering parameters in the database........................................................... 176
Moving an Avaya Media Server (MS) network element to a new server............................. 177
Moving a Web conferencing Server network element to a new server................................ 178
Expanding from a medium to a large deployment (with redundancy)........................................ 179
Checklist for expanding a medium redundant deployment to a large redundant deployment
.................................................................................................................................... 181
Appendix A: Overview of automatic disaster recovery..................................................... 183
Implications of virtualization for automatic disaster recovery.................................................... 185
System service state............................................................................................................ 186
Appendix B: Fixing remote host SSH keys........................................................................ 187
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
7
Chapter 1: An Introduction to Avaya Aura®
Conferencing
About this document
This 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 as
moving your deployment to or from a Demilitarized Zone (DMZ)1 or switching your deployment from
a bare metal solution2 to a virtualized solution3.
Related resources
Documentation
Download the following related documents at http://support.avaya.com.
The Avaya Support website also includes the latest information about product compatibility, ports
and Avaya Aura® Conferencing releases.
Related Links
Overview on page 9
Implementation on page 9
Administration on page 10
Supporting on page 10
1
2
3
8
DMZ or Demilitarized Zone is a physical or logical subnetwork that contains and exposes an organization's externalfacing services to a larger and untrusted network, usually the Internet.
A bare metal solution is a computer system or network in which a virtual machine is installed directly on hardware rather
than within the host operating system (OS).
A virtualized solution refers to the process of masking server resources with the aim of centralizing administrative tasks.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Related resources
Overview
Document
number
Title
Use this document to:
Audience
04-604343
Avaya Aura® Conferencing
Overview and Specification for
Avaya Aura®
Understand the high-level features
and functionality of the product
Customers,
Partners,
Services, and
Support
personnel
04-604344
Avaya Aura® Conferencing
Overview and Specification for
Turnkey
Understand the high-level features
and functionality of the product
Customers,
Partners,
Services, and
Support
personnel
04-604323
Avaya Aura® Conferencing
Solution Description for SME
Understand the high-level features
and functionality of the solution
Customers,
Partners,
Services, and
Support
personnel
04-604328
Avaya Aura® Conferencing
Solution Description for
Medium Enterprises
Understand the high-level features
and functionality of the solution
Customers,
Partners,
Services, and
Support
personnel
04-604333
Avaya Aura® Conferencing
Solution Description for Large
Enterprises
Understand the high-level features
and functionality of the solution
Customers,
Partners,
Services, and
Support
personnel
Related Links
Documentation on page 8
Implementation
Document
number
Title
Use this document to:
Audience
04-604418
Deploying Avaya Aura®
Conferencing: Basic
Installation
Perform installation and configuration
tasks
Partners,
Services, and
Support
personnel
04-604363
Deploying Avaya Aura®
Conferencing: Advanced
Installation and Configuration
Perform installation and configuration
tasks
Partners,
Services, and
Support
personnel
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
9
An Introduction to Avaya Aura® Conferencing
Document
number
Title
Use this document to:
Audience
04-604353
Upgrading Avaya Aura®
Conferencing
Perform upgrading and configuration
tasks
Partners,
Services, and
Support
personnel
Related Links
Documentation on page 8
Administration
Document
number
Title
Use this document to:
Audience
04-604378
Administering Avaya Aura®
Conferencing
Perform system-wide administration
tasks
System
administrators
04-604403
Migrating Avaya Aura®
Conferencing
Perform system-wide security
administration and backup/restore
tasks
System
administrators
04-604398
Maintaining and
Troubleshooting Avaya Aura®
Conferencing
Perform maintenance and
troubleshooting tasks.
System
administrators
Understand logs and fault tracking.
Partners,
Services, and
Support
personnel
Related Links
Documentation on page 8
Supporting
Document
number
Title
Use this document to:
Audience
04–604423
Avaya Aura® Conferencing
Accounting Records Reference
Collect information about accounting
records
System
administrators
Customers,
Partners,
Services, and
Support
personnel
04-604443
10
Avaya Aura® Conferencing
Alarms and Logs Reference
Collect information about alarms and
logs, including the alarms and logs
families
Migrating Avaya Aura® Conferencing
System
administrators
Customers,
Partners,
August 2014
Comments?
[email protected]
Related resources
Document
number
Title
Use this document to:
Audience
Services, and
Support
personnel
04-604444
Avaya Aura® Conferencing
Operational Measurements
Reference
Collect information about operational
measurements
System
administrators
Customers,
Partners,
Services, and
Support
personnel
Related Links
Documentation on page 8
Training
The following courses are available on http://www.avaya-learning.com. In the Search field, type the
course code, and click Go to search for the course.
Course code
Course title
2U00110O
Selling Avaya Aura® Conferencing Solution Learning Bytes
2U00325O
Avaya Aura® Conferencing 7 L1 Customer Scenario
3U00260W
Designing Avaya Aura® Conferencing
5U00120E
Avaya Aura® Conferencing
3204
Avaya Aura® Conferencing Implementation and Maintenance Exam
Viewing Avaya Mentor videos
Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya
products.
About this task
Videos are available on the Avaya Support website, listed under the video document type, and on
the 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.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
11
An Introduction to Avaya Aura® Conferencing
• In Search, type the product name. On the Search Results page, select Video in the
Content Type column on the left.
• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and
perform one of the following actions:
• Enter a key word or key words in the Search Channel to search for a specific product or
topic.
• Scroll down Playlists, and click the name of a topic to see the available list of videos posted
on the website.
Note:
Videos are not available for all products.
Deploying online help
Avaya Aura® Conferencing contains a number of online help files and online manuals to guide you
through the process of installing, configuring, and maintaining your conferencing system. These
online 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 it
describes. So, for example, if you view help on Element Manager, you can access the Element
Manager online help. The Element Manager online help file describes each of the Element Manager
fields and describes many of the common procedures that you can perform using the Element
Manager interface.
12
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Related resources
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 help
into several languages. The list of available languages conforms with the i18n and L10n
(internationalization and localization standards). When users install the Collaboration Agent
application, it chooses which language to display based on the computer's locale.
The online help files are packaged within the Avaya Aura® Conferencing software application
bundle.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
13
An Introduction to Avaya Aura® Conferencing
Support
Go to the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Audience
The 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 logged
in 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
14
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
How to use this document
• 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 presented
by 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 document
You must complete a given task successfully before beginning the next one. If you encounter issues
while performing a step, contact the Avaya Support Web site at http://support.avaya.com to open a
service request.
Use the Avaya Aura® Conferencing 8.0 Intelligent Workbook together with this document to guide
you 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 Links
Preparing your data using the Avaya Aura Conferencing 8.0 Intelligent Workbook on page 15
Preparing your data using the Avaya Aura® Conferencing 8.0
Intelligent Workbook
The Avaya Aura® Conferencing 8.0 Intelligent Workbook is a data collection tool. It is in the
Microsoft 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 the
Design tab, so they might not be listed as they are listed below. This is an example of typical tabs
that might be visible:
• Instructions
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
15
An Introduction to Avaya Aura® Conferencing
• 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 Links
How to use this document on page 15
Administrative user roles and preconfigured accounts
Roles define operational boundaries (access permissions) for administrators. Administrators can
have more than one role, depending on their duties. You assign roles to new administrators when
you create their accounts. During server installation, the installation software creates the following
user accounts:
Preconfigured/
Admin accounts
Default
password
Preassigned role
Description
ntsysadm
password
System Security
Administrator (SSA) role.
The SSA can perform system
configuration and specify security
attributes such as:
• Password configuration
• User management
• Certificate management
16
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Administrative user roles and preconfigured accounts
Preconfigured/
Admin accounts
Default
password
Preassigned role
Description
• Access control
• Antivirus
• File System Integrity tools
• Network configuration
• System backup and restore
ntappadm
password
Application Administrator
(AA) role
The AA can install the Avaya Aura®
Conferencing application software and
manage components related to the
application. The AA is responsible for
installing, maintaining, patching, and
upgrading Avaya Aura® Conferencing
software only.
ntsecadm
password
Security Auditor (SA) role
The SA can collect and view security
audit logs and syslogs at the platform
level. The SA can also transfer the
security logs off the server.
ntbackup
password
Backup Administrator (BA)
role
The BA can perform only system
backups. A BA cannot perform:
• any operation on the server except
backups.
• a system restore—only the SSA or
root user can perform a system
restore.
ntdbadm
password
Database Administrator
(DBA) role
The DBA can manage the database
schemas and database tools on
servers where the database resides.
The server must host the database for
this role to be relevant.
ntossadm
password
Operational Support System
Administrator (OSS) role
Downstream processors can use the
ntossadm account with this role to
connect to the server and collect OSS
logs.
admin
admin
Unlimited privileges
admin1
admin1
For expert mode login to Avaya Aura®
Conferencing, Element Manager, and
Provisioning Manager.
admin2
admin2
admin3
admin3
admin4
admin4
admin5
admin5
init
Not applicable
System Security
SSA and DBA account for Avaya
Administrator (SSA) role and Services access.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
17
An Introduction to Avaya Aura® Conferencing
Preconfigured/
Admin accounts
Default
password
Preassigned role
Description
Database Administrator
(DBA) role
craft
Not applicable
Application Administrator
(AA) role
AA account for Avaya Services access
Supported Web browsers
Avaya Aura® Conferencing supports the following browsers for Collaboration Agent users and
Avaya Aura® Conferencing administrators. Administrators use the following applications to
administer and maintain Avaya Aura® Conferencing:
• Element Manager Console
• Provisioning Client
• Avaya Conferencing Reports & Monitors
Browsers
Operating System
Collaboration
Agent
Administration
Applications
Microsoft Internet
Explorer 7.0 and 8.0
Windows 7
yes
yes
Microsoft Internet
Explorer 9.0 and 10.0
Windows 7
yes
yes
Mozilla Firefox
Windows 7
yes
yes
Google Chrome (latest
version)
Windows 7
yes
-
Apple Safari (latest
version)
Apple OS X
yes
-
version 10 and later
Possible limitations in relation to the Audio/Video in Collaboration Agent feature
When running the Audio/Video in Collaboration Agent feature, Google Chrome may demonstrate
poor 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 to
inform them of this possible limitation.
In addition, users running Google Chrome for the Mac operating system may experience issues
when sharing their desktop. Avaya recommends using Apple Safari or Mozilla Firefox for desktop
sharing instead.
Specific requirements in relation to the Avaya Web Collaboration audio and video
plug-in
The new Avaya Web Collaboration audio and video plug-in has a particular set of operating system
and browser requirements. These requirements are separate to the limitations that Avaya has
18
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Supported hardware
identified with the existing (Flash-based) Audio/Video in Collaboration Agent feature. The following
table 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 (Flashbased) Audio/Video in Collaboration Agent and the new (browser-based) Avaya Web
Collaboration audio and video plug-in.
Supported Operating Systems
Supported Browsers
Microsoft Windows Vista, 7, and 8. (32 and 64 bit)
Mozilla Firefox (latest version)
Apple OS X 10.9, 10.8, and 10.7
Google Chrome (latest version)
Microsoft Internet Explorer 8, 9, 10, and 11 for
Windows
Apple Safari (latest version) for Apple OS X
Note:
For each of these browsers, the Avaya Web
Collaboration audio and video plug-in requires
the 32–bit versions.
The Avaya Web Collaboration audio and video plug-in does not operate successfully with the
following operating systems and browsers:
Unsupported Operating Systems
Unsupported Browsers
Older Microsoft Windows operating systems, such as Any 64–bit version of a browser
Microsoft Windows XP
Microsoft Metro (Internet Explorer)
Google Android and Apple iOS
Opera
Google Chrome
Any other mobile browsers
Linux
Microsoft Windows Mobile
Supported hardware
Avaya Aura® Conferencing 8.0 supports the HP ProLiant DL360p G8 for all deployment
configurations. Alternatively, if you have an existing HP ProLiant DL360 G7, you can reuse it. If you
have existing Dell 610 or IBM S8800 servers, you may be able to reuse them as cascading Avaya
Media Server (MS)’s. However, you cannot reuse the Dell 610 or IBM S8800 servers as Avaya
Aura® Conferencing 8.0 core servers.
The hardware requirements for Avaya Aura® Conferencing 8.0 are the same whether you are
installing the product in an Avaya Aura® deployment or a Turnkey deployment. In both cases, it is
the HP ProLiant DL360p G8 server.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
19
An Introduction to Avaya Aura® Conferencing
4
5
20
Server type
Supported use
HP ProLiant
DL360p G8
Used for new installations of Avaya Aura® Conferencing 8.0.
HP ProLiant
DL360 G7
Can be reused when upgrading existing Avaya Aura® Conferencing 7.2 deployments to
Avaya Aura® Conferencing 8.0.4
Dell 610
Can only be used as cascading media servers within Avaya Aura® Conferencing 8.0
deployments.5
IBM S8800
Can only be used as cascading media servers within Avaya Aura® Conferencing 8.0
deployments.5
For Large deployments (previously known as Standalone in the Avaya Aura® Conferencing 7.x releases) the server
hosting the Element Manager and Database must have more than 12GB of RAM. If your server only has 12GB of RAM
please contact Avaya for a memory expansion kit and apply this kit prior to the upgrade to Avaya Aura® Conferencing
8.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/.
For more information on cascading media servers, see Configuring cascading.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Chapter 2: Migrating servers
Server replacement
This document describes the procedure for replacing an Avaya Aura® Conferencing 8.0 server. The
procedure 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 was
recommended for use for the 7.0 and 7.2 releases to the HP ProLiant DL360p G8 server which
is 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 Avaya
Aura® Conferencing software on this server to Avaya Aura® Conferencing 8.0. This section only
covers replacement and migration of the Avaya Aura® Conferencing 8.0 server to the new
hardware, but does not cover upgrades from older Avaya Aura® Conferencing releases. For
more information about the upgrade procedures, see Upgrading Avaya Aura® Conferencing
which 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.0
server. 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 be
available.
Prerequisites for server replacement
Store 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.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
21
Migrating servers
Server replacement for simplex deployments
This section describes the procedure for Avaya Aura® Conferencing server replacement for SMB
simplex, medium simplex and large simplex deployments.
• If the server you want to replace is the primary Element Manager server, see Element Manager
server replacement for simplex deployments on page 22.
• If the server you want to replace is a non-primary Element Manager server, see Non-Element
Manager server replacement for simplex deployments on page 24.
Related Links
Element Manager server replacement for simplex deployments on page 22
Non-Element Manager server replacement for simplex deployments on page 24
Element Manager server replacement for simplex deployments
The following checklist shows the procedure for replacing the Element Manager server for simplex
deployments.
No.
Task
Description
1
Review the prerequisites
Prerequisites for server
replacement on page 21
2
Determine which Avaya
Aura® Conferencing
components are hosted
on this server
Determining which
components are hosted on
the server on page 30
3
Backup Avaya Aura®
Conferencing if the
server is in stable state
Backing up Avaya Aura®
Conferencing for server
replacement on page 35
Notes
If you successfully backup the Avaya Aura® Conferencing server in step 3 or you have previously backed up
the 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 Avaya
Aura® Conferencing completely. For more information, see Deploying Avaya Aura® Conferencing, which is
available 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 on
the backup are identical to the software versions that you use for the restore steps, below. For
example, if you backed up the system when it was AAC 8.0 FP1 SP2 version (MCP 18.1.2.X), then you
must use the same version in the steps below.
4
22
Stop the network
element instances
hosted on this server if
Stopping a network
element instance on
page 43
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Server replacement for simplex deployments
No.
Task
Description
Notes
the server is in stable
state
5
Stop the Element
Manager instance if the
server is in stable state
Stopping an Element
Manager Instance on
page 44
6
Restore the Avaya Aura® Restoring the platform
Conferencing platform on following server
the server
replacement on page 44
7
Restore the Avaya Aura®
Conferencing application
data on the server
8
Extract the Avaya Aura® Extracting the application
Conferencing Application bundle contents on
Bundle contents to the
page 61
Element Manager server
9
Install the Avaya Aura®
Conferencing application
database to the Element
Manager server
Installing the database
software on page 62
10
Install the Avaya Aura®
Conferencing database
to the primary Element
Manager server
Installing the database on
page 63
11
Restore the database
from backup
Restoring the database
following server
replacement on page 63
12
Install the Element
Manager
Installing Element
Manager on page 64
13
If the server hosts a
media server then install
Avaya Media Server
(MS)
Installing Avaya Media
Server on page 64
14
Restore all the network
element instances on
this server except
Element Manager
Restoring a network
element instance following
server replacement on
page 65
15
If the server hosts a
recording media server
then restore the
recordings
Restoring the recordings
following server
replacement on page 67
16
If the server hosts Flash Restoring the Flash Media
Media
Gateway on page 68
Gateway then Install Flas
Restoring an Avaya Aura®
Conferencing server
following server
replacement on page 59
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
23
Migrating servers
No.
Task
Description
Notes
h Media Gateway and
restore its configuration
17
If this system is
standalone AAC then
install WebLM service
Installing WebLM on
page 67
18
Verify that the Avaya
Aura® Conferencing
system is operating
correctly for users in the
main location
Verifying the system on
page 68
Related Links
Server replacement for simplex deployments on page 22
Non-Element Manager server replacement for simplex
deployments
The following checklist shows the procedure for replacing a non-Element Manager server for
simplex deployments.
No.
Task
Description
1
Review the prerequisites
Prerequisites for server
replacement on page 21
2
Determine which Avaya
Aura® Conferencing
components are hosted
on this server
Determining which
components are hosted on
the server on page 30
3
Backup Avaya Aura®
Conferencing if the
server is in stable state
Backing up Avaya Aura®
Conferencing for server
replacement on page 35
Notes
Note:
If you are restoring the system from a previously made backup, ensure that the software versions on
the backup are identical to the software versions that you use for the restore steps, below. For
example, if you backed up the system when it was AAC 8.0 FP1 SP2 version (MCP 18.1.2.X), then you
must use the same version in the steps below.
4
24
Stop the network
element instances
hosted on this server if
the server is in stable
state
Stopping a network
element instance on
page 43
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Server replacement for simplex deployments
No.
Task
Description
6
Restore the Avaya Aura® If you have a backed up
Conferencing platform on server, see Restoring the
the server
platform following server
replacement. on
page 44 If not, see
Restoring the platform on
page 45
7
Restore the Avaya Aura®
Conferencing application
data on the server
If you have a backed up
server, see Restoring an
Avaya Aura® Conferencing
server following server
replacement on page 59.
If not, skip this step.
13
If the server hosts a
media server then install
Avaya Media Server
(MS)
Installing Avaya Media
Server on page 64
14
Restore all the network
element instances on
this server
Restoring a network
element instance following
server replacement on
page 65
15
If the server hosts a
recording media server
then restore the
recordings
Restoring the recordings
following server
replacement on page 67
16
If the server hosts Flash Restoring the Flash Media
Media
Gateway on page 68
Gateway then Install Flas
h Media Gateway
19
Verify that the Avaya
Aura® Conferencing
system is operating
correctly for users in the
main location
Notes
Verifying the system on
page 68
Related Links
Server replacement for simplex deployments on page 22
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
25
Migrating servers
Server replacement for redundant deployments
This section describes the procedure for Avaya Aura® Conferencing server replacement for SMB
redundant, medium redundant and large redundant deployments.
• If the server you want to replace is the primary Element Manager server, see Primary Element
Manager server replacement for redundant deployments on page 26.
• If the server you want to replace is a non-primary Element Manager server, see Non-primary
Element Manager server replacement for redundant deployments on page 28.
Related Links
Primary Element Manager server replacement for redundant deployments on page 26
Non-primary Element Manager server replacement for redundant deployments on page 28
Primary Element Manager server replacement for redundant
deployments
The following checklist shows the procedure for replacing the primary Element Manager server for
redundant deployments.
No.
Task
Description
1
Review the prerequisites
Prerequisites for server
replacement on page 21
2
Determine which Avaya
Aura® Conferencing
components are hosted
on this server
Determining which
components are hosted on
the server on page 30
3
Backup Avaya Aura®
Conferencing if the
server is in stable state
Backing up Avaya Aura®
Conferencing for server
replacement on page 35
Notes
Note:
If you are restoring the system from a previously made backup, ensure that the software versions on
the backup are identical to the software versions that you use for the restore steps, below. For
example, if you backed up the system when it was AAC 8.0 FP1 SP2 version (MCP 18.1.2.X), then you
must use the same version in the steps below.
4
26
Stop the network
element instances
hosted on this server if
the server is in stable
state
Stopping a network
element instance on
page 43
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Server replacement for redundant deployments
No.
Task
Description
5
Stop the Element
Manager instance if the
server is in stable state
Stopping an Element
Manager Instance on
page 44
6
Restore the Avaya Aura® If you have a backed up
Conferencing platform on server, see Restoring the
the server
platform following server
replacement. on
page 44 If not, see
Restoring the platform on
page 45
7
Restore the Avaya Aura®
Conferencing application
data on the server
8
Extract the Avaya Aura® Extracting the application
Conferencing Application bundle contents on
Bundle contents to the
page 61
Element Manager server
9
Install the Avaya Aura®
Conferencing application
database to the Element
Manager server
Installing the database
software on page 62
10
Install the Avaya Aura®
Conferencing database
to the primary Element
Manager server
Installing the database on
page 63
11
Restore the database
from backup
If you have backed up the
server, seeRestoring the
database following server
replacement on page 63.
If not, see Re-syncing the
database data from the
secondary instance on
page 70.
12
Set up database
replication
Setting up the database
replication on page 71
13
Install the Element
Manager
Installing Element
Manager on page 64
14
If the server hosts a
media server then install
Avaya Media Server
(MS)
Installing Avaya Media
Server on page 64
Notes
If you have a backed up
server, see Restoring an
Avaya Aura® Conferencing
server following server
replacement on page 59.
If not, skip this step.
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
27
Migrating servers
No.
Task
Description
15
Restore all the network
element instances on
this server except
Element Manager
Restoring a network
element instance following
server replacement on
page 65
16
If the server hosts a
recording media server
then restore the
recordings
Restoring the recordings
following server
replacement on page 67
17
If the server hosts Flash Restoring the Flash Media
Media
Gateway on page 68
Gateway then Install Flas
h Media Gateway
18
If this system is
standalone AAC then
install WebLM service
Installing WebLM on
page 67
19
Verify that the Avaya
Aura® Conferencing
system is operating
correctly for users in the
main location
Verifying the system on
page 68
Notes
Related Links
Server replacement for redundant deployments on page 26
Non-primary Element Manager server replacement for redundant
deployments
The following checklist shows the procedure for replacing the non-primary Element Manager servers
for redundant deployments.
28
No.
Task
Description
1
Review the prerequisites
Prerequisites for server
replacement on page 21
2
Determine which Avaya
Aura® Conferencing
components are hosted
on this server
Determining which
components are hosted on
the server on page 30
3
Backup Avaya Aura®
Conferencing if the
server is in stable state
Backing up Avaya Aura®
Conferencing for server
replacement on page 35
Migrating Avaya Aura® Conferencing
Notes
August 2014
Comments?
[email protected]
Server replacement for redundant deployments
No.
Task
Description
Notes
Note:
If you are restoring the system from a previously made backup, ensure that the software versions on
the backup are identical to the software versions that you use for the restore steps, below. For
example, if you backed up the system when it was AAC 8.0 FP1 SP2 version (MCP 18.1.2.X), then you
must use the same version in the steps below.
4
Stop the network
element instances
hosted on this server if
the server is in stable
state
Stopping a network
element instance on
page 43
6
Restore the Avaya Aura® If you have a backed up
Conferencing platform on server, see Restoring the
the server
platform following server
replacement. on
page 44 If not, see
Restoring the platform on
page 45
7
Restore the Avaya Aura®
Conferencing application
data on the server
If you have a backed up
server, see Restoring an
Avaya Aura® Conferencing
server following server
replacement on page 59.
If not, skip this step.
9
If the server hosts the
secondary database,
install the Avaya Aura®
Conferencing application
database
Installing the database
software on page 62
12
If the server hosts the
secondary database, set
up database replication
Setting up the database
replication on page 71
14
If the server hosts a
media server then install
Avaya Media Server
(MS)
Installing Avaya Media
Server on page 64
15
Restore all the network
element instances on
this server
Restoring a network
element instance following
server replacement on
page 65
16
If the server hosts a
recording media server
then restore the
recordings
Restoring the recordings
following server
replacement on page 67
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
29
Migrating servers
No.
Task
Description
Notes
17
If the server hosts Flash Restoring the Flash Media
Media
Gateway on page 68
Gateway then Install Flas
h Media Gateway
19
Verify that the Avaya
Aura® Conferencing
system is operating
correctly for users in the
main location
Verifying the system on
page 68
Related Links
Server replacement for redundant deployments on page 26
Determining which components are hosted on the server
About this task
Use 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 the
appropriate information in the table below. The table has four columns:
1. Component name: Contains the names of the components. Each component is either a
network 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
Element Manager
ElementManager
Accounting Manager
AM1
Instance number
Provisioning Manager
0
Collaboration Agent
0
Application Server
30
Network Element name
AS1
Document Conversion
Server
0
Media Server
0
Web Conferencing
Management Server
0
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
Determining which components are hosted on the server
Component name
Deployed on server
Network Element name
Web Conferencing
Server
Instance number
0
Database
mcpdb
Flash 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 as
Provisioning Manager have pre-defined instance numbers. If the value is 0 then the component can
only have one instance. If the value is - then, the instance number is not applicable for the
component.
Procedure
1. 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 Server
Elements > Element Manager > Element Manager > Instance.
b. In the Element Manager Instance window, check if the long server name of the server
is displayed in the Server column.
c. If the long server name of the server is displayed, then find the corresponding ID and fill
the 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 Server
Elements > Accounting Managers > AM1 > Instance.
b. In the AM1 Instance window, check if the long server name of the server is displayed in
the Server column.
c. If the long server name of the server is displayed, then find the corresponding ID and fill
the following cells in the Accounting Manager row of the table above:
Type YES in the Deployed on server column
Migrating Avaya Aura® Conferencing
August 2014
Comments?
[email protected]
31
Migrating servers
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 Server
Elements > Provisioning Managers. For each network element listed in the
Provisioning Managers window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Provisioning Managers >
> Instance.
c. In the Instance window, check to see if the long
server 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 fill
the following cells in the Provisioning Manager row of the table above:
Type YES in the Deployed on server column
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 Server
Elements > Collaboration Agents. For each network element listed in the
Collaboration Agents window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Collaboration Agents > > Instance.
c. In the Instance window, check to see if the long server
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 fill
the following cells in the Collaboration Agent row of the table above:
Type YES in the Deployed on server column
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 Server
Elements > Application Servers > AS1 > Instance.
b. In the AS1 Instance window, check if the long server name of the server is displayed in
the Server column.
c. If the long server name of the server is displayed, then find the corresponding ID and fill
the following cells in the Application Server row of the table above:
Type YES in the Deployed on server column
Type the Application Server in the Instance number column
32
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Determining which components are hosted on the server
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 Server
Elements > Document Conversion Servers. For each network element listed in the
Document Conversion Servers window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Document Conversion Servers > >
Instance.
c. In the Instance window, check to see if the long
server 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 fill
the following cells in the Document Conversion Server row of the table above:
Type YES in the Deployed on server column
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 Server
Elements > Media Servers and Clusters > Media Servers. For each network element
listed in the Media Servers window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Media Servers and Clusters > Media Servers > >
Instance.
c. In the Instance window, check to see if the long server 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 fill
the following cells in the Media Server row of the table above:
Type YES in the Deployed on server column
Type the Media Server name in the Network Element name column
11. Enter the appropriate information in the Web Conferencing Management Server row in the
table above.
a. In the navigation pane of Element Manager Console, select Feature Server
Elements > Web Conferencing > Web Conferencing Management > Web
Conferencing Management Servers. For each network element listed in the Web
Conferencing Management Servers window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Web Conferencing > Web Conferencing Management > Web
Conferencing Management Servers > > Instance.
c. In the Instance window, check to see if
the long server name of the server is displayed in the Server column.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
33
Migrating servers
d. If the long server name of the server is displayed, then find the corresponding ID and fill
the following cells in the Media Server row of the table above:
Type YES in the Deployed on server column
Type the Web Conferencing Manager Server name in the Network Element name
column
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 Server
Elements > Web Conferencing > Web Conferencing Servers and Clusters > Web
Conferencing Servers. For each network element listed in the Web Conferencing
Servers window, perform the following sub-steps.
b. In the navigation pane of Element Manager Console, select Feature Server
Elements > Web Conferencing > Web Conferencing Servers and Clusters > Web
Conferencing Servers > > Instance.
c. In the Instance window, check to see if the long
server 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 fill
the following cells in the Web Conferencing Server row of the table above:
Type YES in the Deployed on server column
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 Server
Elements > Database > mcpdb > Configuration.
b. In the mcpdb Configuration window check if the short name of the server is displayed in
the Server column.
c. If the short name of the server is displayed, then find the corresponding Instance
Number 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.
Result
You have now determined which components are hosted on the server.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
34
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Backing up Avaya Aura® Conferencing for server replacement
Backing up Avaya Aura® Conferencing for server
replacement
About this task
Use 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 any
data. In such a case, you can use any previously made backups. If you are unable to backup a
particular component and there are no previously made backups, then you need to configure
the component manually.
Procedure
1. 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 up
conference recordings on page 37.
4. If this server hosts the database, see Backing up the database for a feature/service pack or
a patch on page 39.
5. Backup the server:
a. If this server is in Demilitarized Zone (DMZ) or if the networking issues are observed on
the 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 the
servers on page 40.
Result
The Avaya Aura® Conferencing server is backed up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up the Flash Media Gateway(s) for a feature pack on page 36
Backing up the Avaya Media Server (MS) on page 36
Backing up conference recordings on page 37
Backing up the database for a feature pack, a service pack, or a patch on page 39
Backing up the Avaya Aura Conferencing servers on page 40
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
35
Migrating servers
Backing up the Flash Media Gateway(s) for a feature pack
About this task
Use this procedure to backup Flash Media Gateway (FMG). The FMG is the server which enables
the Audio/Video in Collaboration Agent functionality for Avaya Aura® Conferencing. The Audio/Video
in Collaboration Agent feature enables users to receive audio, video, and data content through a
single device.
Procedure
1. 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.
Result
The Flash Media Gateway is backed up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up Avaya Aura Conferencing for server replacement on page 35
Backing up the Avaya Media Server (MS)
About this task
Use this procedure to backup the Avaya Media Server (MS).
Procedure
1. Log on to the server which hosts Avaya Media Server (MS) 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 msBackup.pl and press Enter.
36
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Backing up Avaya Aura® Conferencing for server replacement
Result
A backup summary report is displayed. The backup file is stored in the /var/mcp/ma/MAS/
platdata/EAM/Backups/latest folder.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up Avaya Aura Conferencing for server replacement on page 35
Backing up conference recordings
About this task
Use this procedure to backup conference recordings.
Procedure
1. Configure the SSH keys for conference recordings backup for all recording media server
clusters servers. For more information, see Configuring SSH keys for conference recordings
backup 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.
10. When finished, click Apply.
11. In the navigation pane of Element Manager Console, select Recording > Backup
Locations.
12. In the Backup Locations window, click Add.
13. In the Add Backup Locations dialog box, complete the fields as described below:
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
37
Migrating servers
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 backup
server.
14. When finished, click Apply.
15. In the navigation pane of Element Manager Console, select Feature Server Elements >
Media Servers and Clusters > Media Server Clusters > > 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 > > 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 is
complete, the Status column displays the word, Completed.
20. (Optional) If you want to view the detailed status of the backup, click Details.
Result
Conference recordings are backed up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up Avaya Aura Conferencing for server replacement on page 35
Configuring SSH keys for conference recordings backup on page 38
Configuring SSH keys for conference recordings backup
About this task
Use this procedure to configure SSH keys for conference recordings backup.
38
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Backing up Avaya Aura® Conferencing for server replacement
Procedure
1. 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 -backupuser and press
Enter.
3. At the [sudo] password for ntsysadm prompt type sudo password and press Enter.
4. At the @’s password prompt type the backup server user's
password and press Enter.
Result
SSH keys for conference recordings backup are configured.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up conference recordings on page 37
Backing up the database for a feature pack, a service pack, or a
patch
Note:
The default name for the database is mcpdb. The example commands in this procedure use
mcpdb for the database name. If mcpdb is NOT the name of the database (the value for the
db.neName parameter from the installprops.txt file), replace mcpdb_0 with your
_0 in the command.
About this task
Use this procedure to backup the database.
Procedure
1. 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 and press Enter.
Result
The backup file is created and stored in the /var/mcp/db/backup/latest folder. The backup
file name is .tar.gz. The previous manual backup file is moved to
the /var/mcp/db/backup folder. If the/var/mcp/db/backup/latest folder contains a
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
39
Migrating servers
scheduled automatic backup file, the automatic backup file is moved to the /var/mcp/db/
backup/AUTO_history folder.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up Avaya Aura Conferencing for server replacement on page 35
Backing up the Avaya Aura® Conferencing servers
About this task
Use this procedure to backup an Avaya Aura® Conferencing server.
Procedure
1. 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 of
PostgreSQL from the Element Manager server on page 42.
2. Configure the remote backup parameters. For more information, see Configuring remote
backup 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 press
Enter.
5. Enter the password (if required).
Result
After the backup is complete, a summary report displays the results of the backup. It is important to
check 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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up Avaya Aura Conferencing for server replacement on page 35
Cleaning up unneeded files from the server on page 41
Removing unneeded installers of PostgreSQL from the Element Manager server on page 42
40
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Backing up Avaya Aura® Conferencing for server replacement
Configuring remote backup parameters on page 42
Cleaning up unneeded files from the server
The /var/mcp/loads folder should contain three or fewer loads. When an MR with multiple patch
loads 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 Element
Manager simultaneously because the primary Element Manager and the secondary Element
Manager monitor the loads. If the load is on one server but not on the other server, the Element
Manager copies the loads back to the other Element Manager server.
About this task
Use this procedure to remove old and unneeded loads from the Element Manager servers.
Procedure
1. 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 with
the 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 the
ENTER key: rm –rf .
6. On the secondary Element Manager server, enter the following command, but do not press
the ENTER key: rm –rf .
7. As close together as possible, press the ENTER key in both the primary Element Manager
window and the secondary Element Manager window.
Result
The specified load is removed from the primary Element Manager server and the secondary
Element Manager server.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up the Avaya Aura Conferencing servers on page 40
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
41
Migrating servers
Removing unneeded installers of PostgreSQL from the Element Manager
server
The file name format for installers of PostgreSQL is installer-mcp-postgresqlx.x.xxx.LINUX64.zip.
About this task
Use this procedure to remove old and unneeded installers of PostgreSQL from the Element
Manager server with the primary database.
Procedure
1. 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 .
4. Repeat Step 3 for each installer you want to remove.
Result
The specified installers of PostgreSQL are removed from the Element Manager server.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up the Avaya Aura Conferencing servers on page 40
Configuring remote backup parameters
About this task
Use this procedure to configure remote backup parameters
Procedure
1. 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 press
Enter.
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 operation
prompt and press Enter.
5. Type Y at Enable remote backup/transfer for listed BackupSets (Y/N)? prompt and press
Enter.
42
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Stopping a network element instance
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 of
the 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.x
prompt and press Enter.
9. Press Enter at the Please enter a passphrase for the bkrstr-all private key (or
for no passphrase) prompt.
10. Type N at the Would you like to protect it with a passphrase (Y/N)? prompt and press
Enter.
11. Type Y at the Are you sure you want to continue connecting (yes/no)? prompt and press
Enter.
12. Type the password of the backup user on the backup server at the Please enter
[email protected]'s password prompt and press Enter.
Result
Remote backup parameters are configured.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Backing up the Avaya Aura Conferencing servers on page 40
Stopping a network element instance
About this task
Use this procedure to stop a network element instance.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
> NE
Maintenance.
2. In the Maintenance window, select the row that has a value of the target instance in the ID
column.
3. Click Stop.
The Maint state changes from None to Stopping, indicating that the stop operation is in
progress. When the stop operation is complete, the following state changes occur:
• The Maint state changes back to None.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
43
Migrating servers
• The Admin state changes from Online to Offline.
4. Close the Maintenance window.
Result
The network element instance is stopped.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Stopping an Element Manager instance
About this task
Use this procedure to stop a network element instance of Element Manager.
Procedure
1. 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 the
active Element Manager.
4. In the Confirmation dialog box, click OK.
5. Close the Maintenance window.
Result
The network element instance is stopped.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Restoring the platform following server replacement
About this task
Use this task to restore the Avaya Aura® Conferencing platform
44
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
Procedure
1. 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 USB
drive on page 47.
3. If you do not have the backup of this server, see Installing the platform on page 49.
Result
The Avaya Aura® Conferencing platform is restored
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Restoring the platform from a remote backup server on page 45
Restoring the platform from a USB drive on page 47
Installing the AAC Platform on page 49
Restoring the platform from a remote backup server
Avaya supplies a tool called upgradePrepKit to help you with this task. This tool is not part of the
Avaya 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 the
restore procedure. The manual restore steps are included here for your reference.
About this task
Use this procedure to restore the Avaya Aura® Conferencing platform from a remote backup server.
Procedure
1. 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 Installer
2. 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 go
undetected and result in an installation failure.
If you receive a message indicating that the integrity check has failed, follow the
recommendations to clean or replace DVD-ROM, or replace the optical drive.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
45
Migrating servers
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. The
data 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 next
step.
• 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 the
following:
• 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 hardware
environment.
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.
46
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
11. At the Enter this machine's IP address prompt type the IP address of server and
press Enter.
12. At the Enter the default gateway IP address prompt type the gateway IP address
of 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 the
backup server and press Enter.
15. At the Enter the SFTP user id prompt type the name of backup user on backup server
and press Enter.
16. At the Enter the SFTP password prompt type the password of the backup user on the
backup server and press Enter.
17. At the Enter the remote SFTP directory prompt type the path to the directory where
backup file is stored and press Enter.
18. At the Is this information correct (Y/N) prompt of the Secure FTP Configuration
Validation 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 server
listed above and press Enter.
20. At the Continue [c], Abort [a] prompt of the Configuration Validation screen check
the information, type c and press Enter.
21. At the Continue [c], Abort [a] prompt of the The following User Accounts will be
restored screen check the information, type c and press Enter.
22. At the Press the Enter Key to continue with the installation... prompt of
the System Configuration Complete screen press Enter.
23. Wait until the installation is completed and the server will reboot.
Result
The Avaya Aura® Conferencing platform is restored
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Restoring the platform following server replacement on page 44
Restoring the platform from a USB drive
About this task
Use this procedure to restore the Avaya Aura® Conferencing platform from a USB drive.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
47
Migrating servers
Procedure
1. 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 Installer
2. 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 go
undetected and result in an installation failure.
If you receive a message indicating that the integrity check has failed, follow the
recommendations to clean or replace DVD-ROM, or replace the optical drive.
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. The
data 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 next
step.
• Type n to change the system date and time from the BIOS clock, and press Enter.
Proceed to Modifying the BIOS clock.
48
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
7. The installer attempts to identify the hardware type of the target server, perform one of the
following:
• 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 hardware
environment.
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 3 and press Enter.
10. At the Enter Tar File prompt type the number of the correct backup file for this server
listed above and press Enter.
11. At the Continue [c], Abort [a] prompt of the Configuration Validation screen check
the information, type c and press Enter.
12. At the Continue [c], Abort [a] prompt of the The following User Accounts will be
restored screen check the information, type c and press Enter.
13. At the Press the Enter Key to continue with the installation... prompt of
the 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.
Result
The Avaya Aura® Conferencing platform is restored
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Restoring the platform following server replacement on page 44
Installing the AAC Platform
This section provides the procedures for installing the Avaya Aura® Conferencing platform operating
system 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. Before
undertaking any advanced procedures, you must complete the required Avaya Aura®
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
49
Migrating servers
Conferencing training, as listed in Training on page 11. Avaya recommends that you download
all 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 Application
Bundle 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 task
Avaya Aura® Conferencing must be installed on a Linux platform. Use the following procedure to
install the Avaya Aura® Conferencing platform operating system and base level packages on the HP
ProLiant DL360p G8 server.
Procedure
1. 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 Installer
2. At the boot prompt, type install-kvm, and press Enter.
3. To check the integrity of the system, type y, and press Enter.
Important:
If you do not check the integrity, a defective DVD-ROM or optical drive can go
undetected and result in an installation failure.
If you receive a message indicating that the integrity check has failed, follow the
recommendations to clean or replace DVD-ROM, or replace the optical drive.
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 on page 51.
OR
• Type y to acknowledge the licensing attributes, and press Enter.
50
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
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 attached disk drives.
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 next
step.
• 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.
7. The installer attempts to identify the hardware type of the target server, perform one of the
following:
• If the installer has detected your target server as a known reference server:
Type A to accept and proceed to Step 9 on page 51 or type O and proceed to Classifying
the hardware environment on page 52.
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 1 to select Manual Install, and press Enter.
10. On the System Configuration screen, at the prompt, Press the Enter Key to begin
configuration, 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 Links
Restoring the platform following server replacement on page 44
Modifying the BIOS clock on page 52
Classifying the hardware environment on page 52
Configuring the system on page 53
Configuring the NTP clock on page 56
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
51
Migrating servers
Configuring the Syslog Server on page 58
Modifying the BIOS clock
During the software installation of the target server, you can modify the BIOS clock.
Before you begin
The procedure for Installing the license attributes is completed.
Procedure
1. 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 represents
December.
2. At the prompt Enter the day (1-xx) [x] type the value for the current date, and press
Enter.
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 using
the 24–hour clock, and press Enter. For example, the first hour of the day is 0 and the last
hour of the day is 23.
5. At the prompt Enter the minutes (0-59) [xx], type the minutes using the 24–hour
clock, and press Enter. For example, the first minute of the day is 0 and the last minute of
the day is 59.
6. At the prompt Do you want to keep this date and time (Y/N) [Y] ?, type y to
save your changes, and press Enter.
Result
The 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 steps
Refer back to Step 7 on page 51 in Installing the AAC Platform on page 49 to continue with the
installation process.
Related Links
Installing the AAC Platform on page 49
Classifying the hardware environment
During the software installation of the target server, you can classify the server hardware as either a
known reference server or as a non-reference server. The installer usually determines this
classification 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
52
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
been detected and the reference server requires two disks for RAID-1 disk mirroring, the
installation aborts.
About this task
Configure the target server as a reference or non-reference server and to change the default
hardware.
Procedure
1. 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 HP
DL360 G8.
2. If the installer does not detect the server as a reference server, a list of hardware options
appears, 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:
, 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 disk
configuration 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 the
prompt, 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.
Result
The 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.
Next steps
Refer back to Step 9 on page 51 in Installing the AAC Platform on page 49 to continue with the
installation process.
Related Links
Installing the AAC Platform on page 49
Configuring the system
During 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 task
Configure the system.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
53
Migrating servers
Procedure
1. 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 the
server or press Enter to accept the default value.
4. At the prompt Enter the second slave [eth1], type the Bond0 Slave1 value for the
server 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 press
Enter.
8. At the prompt, Enter subnet prefix length (1-32), type the Network Prefix of the
server, and press Enter.
9. At the prompt Enter gateway IP address, type the Network Default Gateway, and
press Enter.
10. At the prompt Do you want to configure DNS Client? (Y/N) [Y], type y and
press 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 press
Enter.
14. At the prompt You entered “”. Is this correct? (Y/N) [N],
verify the IP address.
15. If the IP address is correct, type y and press Enter.
54
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
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 installation
as the default, and press Enter.
17. The Timezone Selection screen appears. At the prompt Enter Region (1-62), type the
number 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, type
the 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 to
reenter the information. Press Enter.
Result
The 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, VLAN
ID, subnet name, server IP, Network Prefix and Network Default Gateway are configured
correctly.
Run ifconfig and check that bond name, slave names, subnet name, server IP, and
Network Default Gateway are configured correctly.
Run ping 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 servers
are present at displayed list.
Run cat /etc/resolv.conf | grep search and check that all configured Domain
Suffix are present at displayed list.
Run nslookup `hostname` and check that the DNS hostname name was resolved
successfully.
Run nslookup 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 the
same as it was entered during installation. Press ENTER in order to complete working with
tzConfig.pl.
Next steps
Refer back to Step 11 on page 51 in Installing the AAC Platform on page 49 to continue with the
installation process.
Related Links
Installing the AAC Platform on page 49
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
55
Migrating servers
Configuring the NTP clock
During 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 more
information about the NTP server IP addresses, see the Avaya Aura® Conferencing Intelligent
Workbook.
About this task
Configure the NTP clock settings.
Procedure
1. At the prompt, Please indicate the Clock Source function of this server:
• 1. Primary Clock Source server (primary Element Manager server
machine). For example, EMServer1.
• 2. Secondary Clock Source server (secondary Element Manager server
machine). For example, EMServer2.
• 3. This server is NOT a Clock Source server (all other server
machines). 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 Element
Manager, type 1, and press Enter.
2. The primary clock source server requires an external clock. At the prompt, Select
External 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 to
reference (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, type
2, 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 the
external clock source.
If you have more than one clock source, a second prompt appears.
56
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the platform following server replacement
5. At the prompt, Enter IP Address of Primary Clock Source, type the IP address
for 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 address
for the Secondary Clock Source, and press Enter.
Note:
For non-redundant layouts, you can use the same IP address for primary and secondary
clock source.
7. At the prompt, Is this information correct? Y/N [N], type y to continue or n to
correct.
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 an
external 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 to
reference (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.
Result
The 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 are
configured correctly and time is synchronized with NTP server.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
57
Migrating servers
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]:, enter
q 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 stop
ntpdate
service ntpd start
Next steps
Refer back to Step 12 on page 51 in Installing the AAC Platform on page 49 to continue with the
installation process.
Related Links
Installing the AAC Platform on page 49
Configuring the Syslog Server
During the Linux operating system installation, you are prompted to configure the Syslog Server.
About this task
Configure the settings for the Syslog Server, if required.
Procedure
1. 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. Proceed
to 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. Proceed
to the next step.
2. At the prompt Enter the Syslog Server IP address, type the value for the Syslog IP
address, and press Enter.
3. On the Configuration Validation screen, if the values are correct, type y, and press Enter to
accept and continue or type n, and press Enter to reenter the data.
Result
The 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 Server
IP Address? Enter 'c' to configure, 'u' to unconfigure, 'd' to
display, or 'q' to quit [c/u/d/q]: prompt, enter d in order to see if the syslog is
configured correctly.
3. At the Do you wish to configure/unconfigure/display the SysLog Server
IP Address? Enter 'c' to configure, 'u' to unconfigure, 'd' to
display, or 'q' to quit [c/u/d/q]: prompt, enter q to complete working with the
syslogConfig.pl script.
58
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring an Avaya Aura® Conferencing server following server replacement
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, enter
c in order to emulate the ntp changing. This is required in order to send a message to the
syslog.
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 update
appeared.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Installing the AAC Platform on page 49
Restoring an Avaya Aura® Conferencing server following
server replacement
About this task
Use this task to restore the Avaya Aura® Conferencing server. Skip this task if you do not have any
backups.
Procedure
1. 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 the
restoreSvr -usbdrive command. For more information, see Restoring an Avaya Aura®
Conferencing server on page 60.
Result
The Avaya Aura® Conferencing server is restored.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Restoring an Avaya Aura Conferencing server on page 60
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
59
Migrating servers
Restoring an Avaya Aura® Conferencing server
The restore of a server's operating system and configuration data (that is, “server” data) consists of
re-installing and commissioning the server and utilizing the previously backed up server
configuration data to restore the server. For instructions on installation and commissioning an Avaya
Aura® 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 administration
data (or any Platform data or Application data) for a server other than the server from which the
data was originally backed up.
This procedure contains the details regarding the execution of the restoreSvr script, which
restores the server data. This server data includes the Avaya Aura® Conferencing data for
EMServer1 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 remote
administration date.
About this task
Use this procedure to restore the Avaya Aura® Conferencing server.
Procedure
1. 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 and
press Enter.
4. Type ntsysadm's password at [sudo] password for ntsysadm prompt and press
Enter.
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.
Result
The Avaya Aura® Conferencing server is restored.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
60
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Extracting the application bundle contents
Related Links
Restoring an Avaya Aura Conferencing server following server replacement on page 59
Extracting the application bundle contents
Before 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 ISO
images 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. Before
undertaking any advanced procedures, you must complete the required Avaya Aura®
Conferencing training, as listed in Training on page 11. Avaya recommends that you download
all available Avaya Aura® Conferencing documentation, as listed in Documentation on page 8.
About this task
Use this procedure to extract the Avaya Aura® Conferencing 8.0 application bundle contents to the
primary Element Manager server.
Procedure
1. 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 and
place 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 to
extract or the number of Optical drive option, if you want to extract contents from DVD-ROM.
Press Enter.
Result
All required installation files are present on the primary Element Manager server.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
61
Migrating servers
Installing the database software
About this task
Use this procedure to install the database software.
Procedure
1. 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 server
console.
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 configuration
summary is presented.
4. If database type is replicated then you will be prompted to select the primary or the
secondary 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 zip
file, stop and contact Avaya support.
Depending on the server hardware and the target server receiving the installation, the
installation 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.
Result
The database installation is completed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
62
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Installing the database
Installing the database
About this task
Use this procedure to install the Avaya Aura® Conferencing database
Procedure
1. Log into the primary Element Manager server as ntappadm user.
2. At the prompt, type cd /var/mcp/install and press Enter.
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.
Result
The Avaya Aura® Conferencing database is installed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Restoring the database following server replacement
Before you begin
If the backup file you want to restore is stored in a remote location, retrieve the backup file and place
it in the /var/mcp/db/backup folder. If needed, you can restore the database backup from the
server backup.
About this task
Use 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 personnel
should perform this procedure.
Procedure
1. 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 press
Enter.
3. At the prompt, type ./dbRestore.pl where is the name
of the tar.gz file (with or without the tar.gz extension) and press Enter.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
63
Migrating servers
Note:
If mcpdb is not the name of the database (the value for the db.neName parameter from
the installprops.txt file), replace mcpdb_0 with _0 in the command.
Ignore all of the compiler warning messages. These messages do not impact service.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Installing Element Manager
About this task
Use these steps to install the Element Manager instance.
Procedure
1. 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.
2. At the prompt, type cd /var/mcp/install and press Enter.
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.
Result
Once the installation is complete, the following message is displayed:
Upgrade successful.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Installing Avaya Media Server
About this task
Use this procedure to install Avaya Media Server.
64
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring a network element instance during server replacement
Procedure
1. Log on to the server which hosts Avaya Media Server 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 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@:/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@'s password prompt, type the ntappadm password for
the 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.
Result
The Installation completed SUCCESSFULLY message is displayed. The Avaya Media
Server load is now installed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Restoring a network element instance during server
replacement
About this task
Use this task to restore a network element instance.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
network element type > network element you want to upgrade > NE Maintenance.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
65
Migrating servers
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 ID
column.
6. Click Edit.
7. From the Load or Patch box in the Edit Instance dialog box, select the target value, and
click 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 the
ID column.
10. Click Deploy.
11. The Maint state changes from None to Deploying, indicating that the deploy operation is in
progress. When the deploy operation is complete, the following state changes occur:
• The Maint state changes back to None.
• 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 in
progress. When the start operation is complete, the following state changes occur:
• The Maint state changes back to None.
• The Admin state is Online.
• The link status is Up.
• The Oper state is Active or Hot Standby.
Result
The network element instance is restored.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
66
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring the recordings following server replacement
Restoring the recordings following server replacement
About this task
Use this task to restore your conference recordings.
Procedure
1. 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 > > 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 is
complete, the Status column displays Completed.
5. (Optional) If you want to view the detailed status of the backup, click Details.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Installing WebLM
About this task
Use these steps to install WebLM.
Procedure
1. 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.pl
The 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.zip
Please select which weblm load you wish to install [1..2]: 2
Do you want to install "WebLM service" (Y/N)?[Y]: Y
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
67
Migrating servers
Installing WebLM service...
Installation of WebLM service completed successfully
Verifying the system
You can verify the successful operation of Avaya Aura® Conferencing by conducting a test
conference and testing the various features.
About this task
Use this procedure to verify the system is operating properly for the main location.
Procedure
Verify 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.
Result
The system is operating correctly for the main location.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Restoring a Flash Media Gateway (FMG)
The Flash Media Gateway (FMG) powers the Audio/Video in Collaboration Agent functionality.
Before you begin
If the backup file you want to restore is stored in a remote location, retrieve that backup file and
place it in the /var/mcp/db/backup folder.
68
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Restoring a Flash Media Gateway (FMG)
About this task
Use this procedure to restore Flash Media Gateway (FMG).
Procedure
1. Log on to the Element Manager server as a ntappadm user.
2. At the prompt, type scp ntappadm@:/var/mcp/media/avica/* ntappadm@:/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@’s password prompt, type the ntappadm password for
the 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 (for
example, ntsysadm) through SSH or directly at the server console
6. At the prompt, type su – and press Enter.
7. Type the root password, and then press Enter to become the root user.
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 the
configuration 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 of
support.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
69
Migrating servers
Re-syncing the database data from the secondary
instance
Before you begin
Ensure that the secondary database is running and there are no replication errors. See Verifying
that the secondary database is running and there are no replication errors on page 71.
About this task
Use this task to re-sync the database data from the secondary database instance to the primary
one.
This procedure can cause possible loss of data and interruption of service. Only trained personnel
should perform this procedure.
Procedure
1. 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 press
Enter.
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 from
the installprops.txt file), replace mcpdb_1 with _1 in the
command.
Note:
Ignore all of the compiler warning messages. These messages are not
service impacting.
Result
The database is restored.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Verifying that the secondary database is running and has no replication errors on page 71
70
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Setting up the database replication
Verifying that the secondary database is running and has no
replication errors
About this task
Use this task to verify that the secondary database instance is running and has no replication errors.
Procedure
1. Log in to Element manager Console.
2. In the navigation pane of Element Manager Console, select Feature Server Elements >
Database > > 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 Errors
column.
Note:
If the Errors column value is not 0 then you cannot re-sync the database data from the
secondary instance. Instead, you must configure the system manually.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Re-syncing the database data from the secondary instance on page 70
Setting up the database replication
In a redundant deployment, a database on the primary side is replicated to the secondary side. This
replication process means that the database is copied so that, in the unlikely event of the primary
server going offline, Avaya Aura® Conferencing maintains a copy of all conferencing account
information.
Previously, you stopped the replication process. Now, in this procedure, you must restart it again, to
ensure redundancy functionality on the new system.
About this task
Use the following procedure to set up database replication.
Procedure
1. Log on to the server hosting Element Manager instance 0 as ntappadm or an account with
the AA role.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
71
Migrating servers
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 DB
Deploying 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 clear
within a couple of minutes.
Result
The database replication is set up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium redundant deployment on page 83
72
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Chapter 3: Migrating from a bare metal
solution to a virtualized solution
Introduction
This section describes how to migrate an Avaya Aura® Conferencing (AAC) bare metal system to a
VMware 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 the
system component network configuration information. Network configuration information includes IP,
FQDN, gateway, subnet details, and so on. The same network configuration is used for the vAAC
VM on VMware hosts.
Avaya supports the following deployment models for migration from an AAC bare metal system to a
vAAC Virtual Machine:
• Medium simplex
• Medium redundant
Prerequisites
The 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) system
and 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, gateway
IP, 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 accessible
for the deployed VM.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
73
Migrating from a bare metal solution to a virtualized solution
Migrating from bare metal to VM for a medium simplex
deployment
Table 1: Checklist
Number
Task
References
Notes
®
Backup 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 Avaya
Media Server (MS).
Backing up the Avaya
media servers on
page 36
2
On the bare metal Avaya Aura®
Conferencing system, backup the
database.
Backing up the
database on page 79
3
On the bare metal Avaya Aura®
Conferencing system, backup the Flash
Media Gateway (FMG).
See the Backup and
Restore tab in the AACAViCA-IntelligentWorkbook, which is
available from https://
support.avaya.com/
Backing up the flash
media gateways on
page 80
4
On the bare metal Avaya Aura®
Conferencing system, backup the
conference recordings.
Backing up conference
recordings on page 37
5
On the bare metal Avaya Aura®
Conferencing system, backup the Avaya
Aura® Conferencing server
Backing up the
servers on page 40
Note:
You must use the remote method.
(bkupSvr -remote)
6
Shutdown the bare metal Avaya Aura®
Conferencing server
Deploy the vAAC platform VM and restore the platform data
7
Deploy vAAC Platform VM (do not Power
On).
8
Configure the Avaya Aura® Conferencing
platform ISO access from the VM and the
VM Boot BIOS Setup
1. In vSphere Client, select the
deployed VM, right-click on it and
select Edit Settings...
74
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium simplex deployment
Number
Task
2. In the Edit Settings popup window,
display the Hardware tab and select
CD/DVD drive 1.
References
Notes
3. In the Device Type panel, select
Datastore ISO File. Click
Browse ....
4. Select the Platform ISO file from the
shared storage and click Open.
5. In the Edit Settings popup window, in
the Device Status panel, check
Connect at power on.
6. From the Edit Settings popup
window, navigate to Options >
Advanced > Boot Options.
7. In the Force BIOS Setup panel,
check The next time the virtual
machine boots, force entry into
the BIOS setup panel.
8. Click OK on the Edit Settings popup
window.
9
Start the VM and configure the VM BIOS
1. Power on the VM.
2. Right click the VM and select Open
Console.
3. In the BIOS Setup Utility screen,
press the right arrow key to the Boot
tab.
4. Move down the arrow key to CDROM Drive and enter +.
5. Press the right arrow key to the Exit
tab.
6. Save the change.
The Initial platform ISO installation
process screen displays.
10
Restore the Platform using the remote
backup option.
11
After the Platform has restored and
configured successfully, power off the
VM.
Restoring the platform
from a remote backup
server on page 45
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
75
Migrating from a bare metal solution to a virtualized solution
Number
Task
References
12
Reconfigure the VM ISO access and the
VM Boot BIOS Setup.
Notes
1. In vSphere Client, select the
deployed VM, right-click on it and
select Edit Settings...
2. In the Edit Settings popup window,
display the Hardware tab and select
CD/DVD drive 1.
3. In the Edit Settings popup window, in
the Hardware tab, in the Device
Status panel, uncheck Connect at
power on.
4. From the Edit Settings popup
window, navigate to Options >
Advanced > Boot Options.
5. In the Force BIOS Setup panel,
check The next time the virtual
machine boots, force entry into
the BIOS setup panel.
6. Click OK on the Edit Settings popup
window.
13
Power on the VM and reconfigure the VM
BIOS
1. Power on the VM.
2. Right click on the VM and select
Open Console.
3. In the BIOS Setup Utility screen,
press the right arrow key to the Boot
tab.
4. Move down the arrow key to CDROM Drive and enter - .
5. Press the right arrow key to the Exit
tab.
6. Save the change.
The VM boots up normally.
14
Install the VMware tools package
Manually install the
VMware tools
package on page 80
Restore and start up vAAC components
76
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium simplex deployment
Number
Task
References
15
Configure the remote backup
parameters.
Configuring remote
backup parameters on
page 42
16
Restore theAvaya Aura® Conferencing
server by executing the command
restoreSvr -remote as a ntsysadm
user.
Restoring an Avaya
Aura® Conferencing
server on page 60
17
Install the database software by
executing the command
mcpDbSwInstall.pl in /var/mcp/
install as a ntappadm user.
Installing the database
software on page 62
18
Install the database by executing the
command dbInstall.pl
in /var/mcp/install as a ntappadm
user.
Installing the database on
page 63
19
Restore the database by executing the
command /var/mcp/run/MCP_18.0/
mcpdb_0/bin/util/dbRestore.pl
as the
ntdbadm user.
Restoring the database
following server
replacement on page 63
20
Install the Avaya Media Server (MS)
software by executing the command
mcpMsInstall.pl as a root user.
Installing Avaya Media
Server on page 64
21
Deploy the Element Manager by
executing the command emDeploy.pl
in /var/mcp/install as a ntappadm
user.
22
Starting the Element Manager by
executing the command /var/mcp/
install/emStart.pl as a ntappadm
user.
23
Kill, deploy, and start each of the network
elements from the Element Manager
Console.
Notes
Killing a network element
instance on page 81
Deploying a Network
Element instance on
page 82
Starting a Network
Element instance on
page 83
24
Restore the recordings:
1. Configure the recording backup
server but do not use the existing
SSH key from the restore process.
Configuring SSH keys for
conference recordings
backup on page 38
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
77
Migrating from a bare metal solution to a virtualized solution
Number
Task
2. Login to the Element Manager
Console and navigate to Media
Servers and Clusters > Media
Server Clusters >
MediaServerCluster1 >
Recording > Restore >
Maintenance > Start.
References
25
Install the FMG software by following the
steps in the Flash Media Gateway (FMG)
worksheet (AViCA I&C1–FMG
Installation).
See the AViCA I&C > 1–
FMG Installation tab in
the AAC-AViCAIntelligent-Workbook,
which is available from
https://
support.avaya.com/
1. Execute the command /var/mcp/
media/avica/AccWeb-3.1_AACNIGHTLY.
2014xxxx#xxx.i386.rpm.bin as
a root user.
2. At the Do you agree to the
above license terms? [yes
or no] prompt, enter yes.
Notes
Restoring the Flash
Media Gateway on
page 68
3. At the Do you want to run the
configuration tool now?
[yes or no] prompt, enter no.
Note:
You only need to run the
configuration tool when you are
installing the FMG.
26
Restore the FMG:
Restoring the Flash
Media Gateway on
1. Copy the backup file from the remote
page 68
site to /var/mcp/fmg/backup/.
2. Login to the FMG server as a root
user.
3. Run the
command /var/mcp/run/fmg/bi
n/restoreConfig and select the
backup you want to restore.
4. Execute the command service
red5 start to start the service.
5. Verify that the /var/mcp/media/
prov_pa_installs/otv/
AccWebCustomerConfig.xml file
is the proper configuration file. If
required, copy the backup file
AccWebCustomerConfig.xml
78
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium simplex deployment
Number
Task
References
from the remote site to /var/mcp/
media/prov_pa_installs/otv/.
Notes
Note:
If the FMG is not working properly,
select the FMG and click the
Restart button.
Related Links
Backing up the database on page 79
Backing up the Flash Media Gateway(s) on page 80
Manually installing the VMware tools package on page 80
Killing a network element instance on page 81
Deploying a network element instance on page 82
Starting a Network Element instance on page 83
Backing up the database
Note:
The default name for the database is mcpdb. The example commands in this procedure use
mcpdb for the database name. If mcpdb is NOT the name of the database (the value for the
db.neName parameter from the installprops.txt file), replace mcpdb_0 with your
_0 in the command.
About this task
Use this procedure to backup the database.
Procedure
1. 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 and press Enter.
Result
The backup file is created and stored in the /var/mcp/db/backup/latest folder. The backup
file name is .tar.gz. The previous manual backup file is moved to
the /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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
79
Migrating from a bare metal solution to a virtualized solution
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Backing up the Flash Media Gateway(s)
About this task
Use this procedure to backup Flash Media Gateway (FMG). The FMG is the server which enables
the Audio/Video in Collaboration Agent functionality for Avaya Aura® Conferencing. The Audio/Video
in Collaboration Agent feature enables users to receive audio, video, and data content through a
single device.
Procedure
1. 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.
Result
The Flash Media Gateway is backed up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Manually installing the VMware tools package
Before you begin
The deployed vAAC VM must be powered on and running. It must have access to the current
VMware host’s datastore.
About this task
Use this task to manually install a compatible VMware tools package to the deployed vAAC VM.
Procedure
1. In vSphere Client, select the deployed VM, right-click on it and click Edit Settings...
80
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium simplex deployment
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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Killing a network element instance
About this task
Use this procedure to kill a network element instance.
Procedure
1. Log on to the Element Manager Console.
2. In the navigation pane of Element Manager Console, select Feature Server Elements >
> > NE
Maintenance.
3. In the Maintenance window, select the row that has a value of the target instance in the ID
column.
4. Click Kill.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
81
Migrating from a bare metal solution to a virtualized solution
The Maint state changes from None to Killing, indicating that the kill operation is in
progress. When the kill operation is complete, the following state changes occur:
• The Maint state changes back to None.
• The Admin state changes from Online to Offline.
5. Close the Maintenance window.
Result
The network element instance is up and running.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Deploying a network element instance
About this task
Use this procedure to deploy a network element instance.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements>
> NE
Maintenance.
2. In the Maintenance dialog box, select the row that has a value of the target instance in the ID
column.
3. Click Deploy.
The Maint state changes from None to Deploying, indicating that the deploy operation is in
progress. When the deploy operation is complete, the Maint state changes back to None,
and the Admin state changes from Configured to Offline.
4. Close the Maintenance window.
Result
The Network Element instance is deployed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
82
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium redundant deployment
Starting a Network Element instance
About this task
Use this procedure to start a Network Element instance.
Procedure
1. Log on to Element Manager Console.
2. In the navigation pane of Element Manager Console, select Feature Server Elements>
> > NE
Maintenance.
3. In the Maintenance dialog box, select the row that has a value of the target instance in the ID
column.
4. Click Start.
The Maint state changes from “None” to “Starting,” indicating that the start operation is in
progress. 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 on
the instance of the component.
Result
The Network Element instance is up and running.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
Migrating from bare metal to VM for a medium redundant
deployment
Table 2: Checklist
Number
Task
References
Notes
®
Backup 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 the
Avaya Media Server (MS).
Backing up the Avaya
media servers on
page 36
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
83
Migrating from a bare metal solution to a virtualized solution
Number
Task
References
2
On the primary server bare metal Avaya
Aura® Conferencing system, backup the
database.
Backing up the
database on page 79
Notes
Note:
This step does not apply for medium
redundant secondary server
deployment.
3
On the primary server bare metal Avaya
Aura® Conferencing system, backup the
Flash Media Gateway (FMG).
See the Backup and
Restore tab in the AACAViCA-IntelligentWorkbook, which is
available from https://
support.avaya.com/
Backing up the flash
media gateways on
page 80
4
On the primary server bare metal Avaya
Aura® Conferencing system, backup the
conference recordings.
Backing up conference
recordings on page 37
5
On the primary server bare metal Avaya
Aura® Conferencing system, backup the
Avaya Aura® Conferencing server
Backing up the
servers on page 40
Note:
You must use the remote method.
(bkupSvr -remote)
6
Repeat steps 1–5 for the secondary
server.
7
Shutdown the bare metal Avaya Aura®
Conferencing secondary server
8
Shutdown the bare metal Avaya Aura®
Conferencing primary server
Deploy the vAAC platform VM and restore the platform data
9
On the primary VM, deploy vAAC
Platform VM (do not Power On).
10
On the primary VM:
Configure the Avaya Aura® Conferencing
platform ISO access from the VM and the
VM Boot BIOS Setup.
1. In vSphere Client, select the
deployed VM, right-click on it and
select Edit Settings...
84
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium redundant deployment
Number
Task
2. In the Edit Settings popup window,
display the Hardware tab and select
CD/DVD drive 1.
References
Notes
3. In the Device Type panel, select
Datastore ISO File. Click
Browse ....
4. Select the Platform ISO file from the
shared storage and click Open.
5. In the Edit Settings popup window, in
the Device Status panel, check
Connect at power on.
6. From the Edit Settings popup
window, navigate to Options >
Advanced > Boot Options.
7. In the Force BIOS Setup panel,
check The next time the virtual
machine boots, force entry into
the BIOS setup panel.
8. Click OK on the Edit Settings popup
window.
11
On the primary VM:
Start the VM and configure the VM BIOS.
1. Power on the VM.
2. Right click the VM and select Open
Console.
3. In the BIOS Setup Utility screen,
press the right arrow key to the Boot
tab.
4. Move down the arrow key to CDROM Drive and enter +.
5. Press the right arrow key to the Exit
tab.
6. Save the change.
The Initial platform ISO installation
process screen displays.
12
On the primary VM:
Restore the Platform using the remote
backup option.
13
Restoring the platform
from a remote backup
server on page 45
On the primary VM:
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
85
Migrating from a bare metal solution to a virtualized solution
Number
Task
After the Platform has restored and
configured successfully, power off the
VM.
14
On the primary VM:
References
Notes
Reconfigure the VM ISO access and the
VM Boot BIOS Setup.
1. In vSphere Client, select the
deployed VM, right-click on it and
select Edit Settings...
2. In the Edit Settings popup window,
display the Hardware tab and select
CD/DVD drive 1.
3. In the Edit Settings popup window, in
the Hardware tab, in the Device
Status panel, uncheck Connect at
power on.
4. From the Edit Settings popup
window, navigate to Options >
Advanced > Boot Options.
5. In the Force BIOS Setup panel,
check The next time the virtual
machine boots, force entry into
the BIOS setup panel.
6. Click OK on the Edit Settings popup
window.
15
On the primary VM:
Power on the VM and reconfigure the VM
BIOS
1. Power on the VM.
2. Right click on the VM and select
Open Console.
3. In the BIOS Setup Utility screen,
press the right arrow key to the Boot
tab.
4. Move down the arrow key to CDROM Drive and enter - .
5. Press the right arrow key to the Exit
tab.
6. Save the change.
The VM boots up normally.
86
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium redundant deployment
Number
Task
References
16
On the primary VM:
Manually install the
VMware tools
package on page 80
Install the VMware tools package
17
Notes
Repeat steps 10–16 for the secondary
VM.
Restore and start up vAAC components
18
Configure the remote backup parameters
on the primary.
Configuring remote
backup parameters on
page 42
19
Configure the remote backup parameters
on the secondary.
Configuring remote
backup parameters on
page 42
20
On the primary, restore theAvaya Aura®
Conferencing server by executing the
command restoreSvr -remote as a
ntsysadm user.
Restoring an Avaya
Aura® Conferencing
server on page 60
21
On the secondary, restore theAvaya
Restoring an Avaya
Aura® Conferencing server by executing
Aura® Conferencing
the command restoreSvr -remote as server on page 60
a ntsysadm user.
22
Install the primary database software on
the primary by executing the command
mcpDbSwInstall.pl in /var/mcp/
install as a ntappadm user.
Installing the database
software on page 62
23
Change the database type to SINGLE on
the primary, by executing the command
populateInstallpropsFile.pl
in /var/mcp/install as a ntappadm
user.
Setting the database type
to single on page 90
24
Install the database on the primary by
executing the command dbInstall.pl
in /var/mcp/install as a ntappadm
user.
Installing the database on
page 63
25
Restore the database on the primary by
executing the
command /var/mcp/run/MCP_18.0/
mcpdb_0/bin/util/dbRestore.pl
as the
ntdbadm user.
Restoring the database
following server
replacement on page 63
26
Change the database type to
REPLICATED on the primary, by
executing the command
populateInstallpropsFile.pl
Setting the database type
to replicated on
page 91
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
87
Migrating from a bare metal solution to a virtualized solution
Number
Task
in /var/mcp/install as a ntappadm
user.
References
27
Install the secondary database software
on the primary by executing the
command mcpDbSwInstall.pl
in /var/mcp/install as a ntappadm
user.
Installing the database
software on page 62
28
Replicate the database from the primary
to the secondary by executing this
command on the Primary
setupDBReplication.pl
in /var/mcp/install as ntappadm.
Setting up the database
replication on page 71
Notes
Wait until database replication is
configured.
29
Install the Avaya Media Server (MS)
software on the primary by executing the
command mcpMsInstall.pl as a
root user.
Installing Avaya Media
Server on page 64
30
Install the Avaya Media Server (MS)
software on the secondary by executing
the command mcpMsInstall.pl as a
root user.
Installing Avaya Media
Server on page 64
31
Deploy the Element Manager on the
primary by executing the command
emDeploy.pl in /var/mcp/install
as a ntappadm user.
32
Starting the Element Manager on the
primary by executing the
command /var/mcp/install/
emStart.pl as a ntappadm user.
33
Kill, deploy, and start each of the network
elements from the Element Manager
Console.
Killing a network element
instance on page 81
Deploying a Network
Element instance on
page 82
Starting a Network
Element instance on
page 83
34
Restore the recordings:
1. Configure the recording backup
server but do not use the existing
SSH key from the restore process.
Configuring SSH keys for
conference recordings
backup on page 38
2. Login to the Element Manager
Console and navigate to Media
88
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium redundant deployment
Number
Task
Servers and Clusters > Media
Server Clusters >
MediaServerCluster1 >
Recording > Restore >
Maintenance > Start.
References
35
On the primary VM:
See the AViCA I&C > 1–
FMG Installation tab in
the AAC-AViCAIntelligent-Workbook,
which is available from
https://
support.avaya.com/
Install the FMG software by following the
steps in the Flash Media Gateway (FMG)
worksheet (AViCA I&C1–FMG
Installation).
1. Execute the command /var/mcp/
media/avica/AccWeb-3.1_AACNIGHTLY.
2014xxxx#xxx.i386.rpm.bin as
a root user.
Notes
Restoring the Flash
Media Gateway on
page 68
2. At the Do you agree to the
above license terms? [yes
or no] prompt, enter yes.
3. At the Do you want to run the
configuration tool now?
[yes or no] prompt, enter no.
Note:
You only need to run the
configuration tool when you are
installing the FMG.
36
On the primary VM:
Restoring the Flash
Media Gateway on
page 68
Restore the FMG:
1. Copy the backup file from the remote
site to /var/mcp/fmg/backup/.
2. Login to the FMG server as a root
user.
3. Run the
command /var/mcp/run/fmg/bi
n/restoreConfig and select the
backup you want to restore.
4. Execute the command service
red5 start to start the service.
5. Verify that the /var/mcp/media/
prov_pa_installs/otv/
AccWebCustomerConfig.xml file
is the proper configuration file. If
required, copy the backup file
AccWebCustomerConfig.xml
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
89
Migrating from a bare metal solution to a virtualized solution
Number
Task
References
from the remote site to /var/mcp/
media/prov_pa_installs/otv/.
Notes
Note:
If the FMG is not working properly,
select the FMG and click the
Restart button.
37
Repeat steps 35–36 for the secondary.
Related Links
Setting the database type to single on page 90
Setting the database type to replicated on page 91
Setting up the database replication on page 71
Setting the database type to single
In a redundant deployment, a database on the primary side is replicated to the secondary side. This
replication process means that the database is copied so that, in the unlikely event of the primary
server going offline, Avaya Aura® Conferencing maintains a copy of all conferencing account
information.
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 task
Use this procedure to set the database type to single.
Procedure
1. Log into the primary Element Manager server as ntappadm user.
2. At the prompt, type populateInstallpropsFile.pl and press Enter.
3. At all the prompts with the exception of Database Type (SINGLE/REPLICATED)?, retain
the existing values.
4. At the Database Type (SINGLE/REPLICATED)? prompt, type SINGLE and press Enter.
Result
The database type is set to single.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium redundant deployment on page 83
90
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from bare metal to VM for a medium redundant deployment
Setting the database type to replicated
In a redundant deployment, a database on the primary side is replicated to the secondary side. This
replication process means that the database is copied so that, in the unlikely event of the primary
server going offline, Avaya Aura® Conferencing maintains a copy of all conferencing account
information.
About this task
Use this procedure to set the database type to single.
Procedure
1. Log into the primary Element Manager server as ntappadm user.
2. At the prompt, type populateInstallpropsFile.pl and press Enter.
3. At all the prompts with the exception of Database Type (SINGLE/REPLICATED)?, retain
the existing values or enter values that were used during initial Avaya Aura® Conferencing
installation.
4. At the Database Type (SINGLE/REPLICATED)? prompt, type REPLICATED and press
Enter.
Result
The database type is set to replicated.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium redundant deployment on page 83
Setting up the database replication
In a redundant deployment, a database on the primary side is replicated to the secondary side. This
replication process means that the database is copied so that, in the unlikely event of the primary
server going offline, Avaya Aura® Conferencing maintains a copy of all conferencing account
information.
Previously, you stopped the replication process. Now, in this procedure, you must restart it again, to
ensure redundancy functionality on the new system.
About this task
Use the following procedure to set up database replication.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
91
Migrating from a bare metal solution to a virtualized solution
Procedure
1. 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 DB
Deploying 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 clear
within a couple of minutes.
Result
The database replication is set up.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium redundant deployment on page 83
92
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Chapter 4: Migrating from a turnkey
solution to an Aura® solution
Migrating from Avaya Aura® Conferencing turnkey to
Avaya Aura® Conferencing with the full Avaya Aura®
platform
Use the following checklist to migrate your deployment from an Avaya Aura® Conferencing turnkey
solution 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.
No.
Task
Description
Notes
1
Disable the Access Control List
(ACL) rules on Avaya Aura®
Conferencing servers if they are
used.
Configuring the access control
list on page 99
2
Add Avaya Aura® System Manager Adding System Manager to the
to the Element Manager GUI.
Element Manager GUI on
page 96
3
Add Avaya Aura® Session
Manager to the Element Manager
GUI.
4
Change the WebLM location to use Changing the WebLM location to
Avaya Aura® System Manager.
use System Manager on page 98
5
Configure Avaya Aura® Session
Manager as the bandwidth
management ASM for the
application server
Configuring Session Manager as
the bandwidth management ASM
for the application server on
page 98
6
Stop all network element instances
except Element Manager
Stopping a network element
instance on page 43
7
Create network element
certificates signed by Avaya Aura®
System Manager.
See Creating Network Element
certificates signed by the System
Manager on page 116.
8
Assign new certificates to all
network element instances.
Assigning a new certificate to the
Element Manager on page 118
Adding Session Manager to the
Element Manager GUI on
page 97
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
93
Migrating from a turnkey solution to an Aura® solution
No.
Task
Description
Notes
Assigning a new certificate to the
Provisioning Manager on
page 119
Assigning a new certificate to the
Collaboration Agent Manager on
page 120
Assigning a new certificate to the
Application Server on page 121
Assigning a new certificate to the
Avaya Media Server on page 122
Assigning a new certificate to the
Web Conferencing Server on
page 123
Assigning a new certificate to the
Web Conferencing Management
Server on page 124
Assigning a new certificate to the
DCS on page 125
9
Remove all of the old certificates
on the Turnkey solution.
Removing all the old certificates on
Turnkey on page 136
10
Stop Element Manager
Stopping an Element Manager
Instance on page 44
11
Restart all network element
instances.
Stopping a network element
instance on page 43
Stopping an Element Manager
Instance on page 44
Starting a network element
instance on page 156
Starting an Element Manager
instance from the server
console on page 125
94
12
Configure single sign-on for
Element Manager Console and
Provisioning Client.
Configuring single sign-on on
page 126
13
Configure ACL rules on the Avaya
Aura® Conferencing server to
reflect network topology changes if
they were used.
Configuring the access control
list on page 99
14
Create a SIP entity for Avaya
Aura® Conferencing on Avaya
Aura® System Manager.
Configuring the route to Avaya
Aura Conferencing on System
Manager on page 130
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
No.
Task
Description
Notes
15
Create a certificate for the Flash
Media Gateway (FMG) IP address
that is signed by Avaya Aura®
System Manager.
Creating a System Manager signed
certificate for the FMG IP
address on page 133
16
Configure a SIP TLS connection
from the Flash Media Gateway
(FMG) to the Avaya Aura® Session
Manager.
Configuring a secure SIP TLS
connection from the FMG to
Session Manager on page 134
17
In Provisioning Client, enable
Allow bandwidth management
and disable User Password
Owned Locally.
Changing the system default
settings to use Avaya Aura
Conferencing (AAC) on page 135
18
Remove the dialing rules in
Provisioning Client.
Removing the dialing rules in
Provisioning Client on page 135
19
Remove all SIP entities for PBXs in Removing all SIP entities for PBXs
Element Manager.
in Element Manager on page 136
20
Verify that the Avaya Aura®
Conferencing system is operating
correctly.
Verifying the system on page 68
Related Links
Adding Avaya Aura System Manager to the Element Manager GUI on page 96
Adding Avaya Aura Session Manager to the Element Manager GUI on page 97
Changing the WebLM location to use Avaya Aura System Manager on page 98
Configuring Session Manager as the bandwidth management ASM for the application server on
page 98
Configuring the access control list (ACL) on page 99
Guidelines for certificate configuration on page 114
Obtaining enrollment password from System Manager on page 116
Creating Network Element certificates signed by System Manager on page 116
Assigning a new certificate to the Element Manager on page 118
Assigning a new certificate to the Provisioning Manager on page 119
Assigning a new certificate to the Collaboration Agent Manager on page 120
Assigning a new certificate to the Application Server on page 121
Assigning a new certificate to the Avaya Media Server on page 122
Assigning a new certificate to the Web Conferencing Server on page 123
Assigning a new certificate to the Web Conferencing Management Server on page 124
Assigning a new certificate to the DCS on page 125
Starting an Element Manager instance from the server console on page 125
Configuring the route to Avaya Aura Conferencing on System Manager on page 130
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
95
Migrating from a turnkey solution to an Aura® solution
Creating a System Manager- signed certificate for the Flash Media Gateway IP address on
page 133
Configuring a secure SIP TLS connection from the Flash Media Gateway to Avaya Aura Session
Manager on page 134
Changing the system default settings to use Avaya Aura Conferencing (AAC) on page 135
Removing the dialing rules in Provisioning Client on page 135
Removing all SIP entities for PBXs in Element Manager on page 136
Removing all the old certificates on Turnkey on page 136
Adding Avaya Aura® System Manager to the Element Manager
GUI
About this task
Use this task to add and configure System Manager in the Element Manager GUI.
Procedure
1. 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 IP
address of the System Manager that is being used.
4. Click Apply.
5. In the navigation pane of Element Manager Console, select External Nodes.
6. In the External Nodes window, click Add (+).
7. In the Add External Node dialog box, enter the logical name SMGRExtNode and select IP
address you specified in Step 3.
8. Click Apply.
9. In the navigation pane of Element Manager Console, select Avaya Aura Core > System
Manager.
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.
96
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Adding Avaya Aura® Session Manager to the Element Manager
GUI
About this task
Use this task to add and configure Session Manager in the Element Manager GUI.
Procedure
1. 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 ASM1ExtOAMSvcAddr and IP
address of the Session Manager that is being used.
4. Click Apply.
5. In the navigation pane of Element Manager Console, select External Nodes.
6. In the External Nodes window, click Add (+).
7. In the Add External Node dialog box, enter the logical name ASM1ExtNode and select IP
address you specified in Step 3.
8. Click Apply.
9. In the navigation pane of Element Manager Console, select Avaya Aura Core > Session
Manager.
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.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
97
Migrating from a turnkey solution to an Aura® solution
12. Click Apply.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Changing the WebLM location to use Avaya Aura® System
Manager
About this task
Use this task to enable the System Manager WebLM.
Procedure
1. 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 WebLM
instance location.
3. Click OK.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring Session Manager as the bandwidth management
ASM for the application server
About this task
Use this task to configure Session Manager as the bandwidth management ASM for the application
server.
Procedure
1. In the navigation pane of the Element Manager Console, select Feature Server Elements >
Application Servers > > Bandwidth Management ASM.
98
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
2. In the Bandwidth Management ASM dialog box, select the Session
Manager you want to use as the primary Session Manager.
3. If you want to use two Session Managers, select the second Session Manager as the
Secondary Session Manager.
4. Click Apply.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring the access control list (ACL)
There are two parts to the ACL configuration: internal ACL rules and external ACL rules. The
internal rules pertain to connections that are used within the system and are auto-generated from
the Avaya Aura® Conferencing database. The external rules pertain to restricting external access to
Avaya Aura® Conferencing. You must configure the external rules manually. The following sections
describe 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. The
internal ACL rules will be applied only when the external ACL rules are configured and
committed.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring internal ACL rules on page 99
Configuring external ACL rules on page 101
Configuring internal ACL rules
About this task
Use the following procedure to configure internal ACL rules.
Procedure
1. 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 on
page 100.
Migrating Avaya Aura® Conferencing
August 2014
Comments? [email protected]
99
Migrating from a turnkey solution to an Aura® solution
3. Install an internal ACL configuration file on all other servers. See Installing an internal ACL
configuration file on all other servers on page 101.
Related Links
Configuring the access control list (ACL) on page 99
Generating an internal ACL configuration file on page 100
Installing an internal ACL configuration file on the primary Element Manager server on page 100
Installing an internal ACL configuration file on all other servers on page 101
Generating an internal ACL configuration file
Before you begin
You must be able to log onto the primary Element Manager server a user with the Application
Administrator (AA) role.
About this task
Use the following procedure to generate an internal ACL configuration file.
Procedure
1. 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 primary
Element Manager server. You must now install the internal ACL configuration file on all
servers in the system (including the primary Element Manager server).
Related Links
Configuring internal ACL rules on page 99
Installing an internal ACL configuration file on the primary Element Manager server
Before you begin
You must be able to log onto the primary Element Manager server as a user the System Security
Administrator (SSA) role.
About this task
Use the following procedure to install an internal ACL configuration file on the primary Element
Manager server.
Procedure
1. 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.
Related Links
Configuring internal ACL rules on page 99
100
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Installing an internal ACL configuration file on all other servers
Before you begin
You must be able to log onto the primary Element Manager server a user with the System Security
Administrator (SSA) role.
About this task
Use 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 audio
and video.
Procedure
1. 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 server
internal OAM IP address and press Enter.
4. At the prompt SFTP user id, enter the SSA user name defined on the primary Element
Manager 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 password
and 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 via
the iptcfg tool. See Importing an external ACL configuration file on page 103.
Related Links
Configuring internal ACL rules on page 99
Configuring external ACL rules
About this task
There are multiple methods available for configuring external ACL rules. The iptcfg tool provides an
interactive menu that enables you to
• configure the settings for an individual node
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
101
Migrating from a turnkey solution to an Aura® solution
• 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 the
import 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 (previously
installed) is used by the iptcfg tool to create firewall rules for the internal nodes. No further action is
required to include the internal ACL rules.
Use the following procedure to configure external ACL rules.
Procedure
1. 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 an
external ACL configuration file on page 103.
• Configure the rules manually using the iptcfg tool. See Configuring external ACL rules
manually (using the iptcfg tool) on page 105.
3. Verify the ACL configuration. See Verifying the ACL configuration on page 108.
Related Links
Configuring the access control list (ACL) on page 99
Preparing the Avaya Media Server on page 102
Importing an external ACL configuration file on page 103
Configuring external ACL rules manually (using the iptcfg tool) on page 105
Verifying the ACL configuration on page 108
External ACL configuration settings on page 108
Example of import.dat file on page 113
Preparing the Avaya Media Server
Before 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 task
Perform this procedure on all servers where the Avaya Media Server is deployed, regardless of the
layout type (that is, SMB, medium, or lrage)).
Procedure
1. Log onto the server as a user with the SSA role.
2. At the prompt, enter su - and press Enter.
102
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
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 Links
Configuring external ACL rules on page 101
Importing an external ACL configuration file
Before you begin
You must be able to log onto the server as a user with the System Security Administrator (SSA)
role.
About this task
Use the following procedure to import an external ACL configuration file. The import files are server
specific. As a result, each server in the Avaya Aura® Conferencing system will require its own import
file containing IP addresses that are specific to that server. The Element Manager server import file
and the Avaya Media Server import file differ slightly.
The Avaya Media Server ACL import file has additional syntax that is not present in the Element
Manager Server import file. For more information, see the Avaya Media Server-specific ACL import
example file, which is located in the directory /opt/mcp/ipt/example on an Avaya Media
Server. 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 on
how to configure the file. This example file is located in the directory /opt/mcp/ipt/example on
the 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 differ
slightly, 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 import
file:
• 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 on
page 113.
To see the lists of trusted nodes, trusted ports, and DSCP settings that you must configure on each
server according to your deployment layout, see External ACL configuration settings on page 108.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
103
Migrating from a turnkey solution to an Aura® solution
Note:
You must perform this procedure on all servers in the Avaya Aura® Conferencing system.
Procedure
1. Log onto the server as a user with the SSA role.
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 the
directory /opt/mcp/ipt/example on the Avaya Aura® Conferencing server.
The Avaya Media Server-specific ACL import example file is located in the
directory /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 the
administrator PC from which you log onto the server. If the administrator PC is not
configured as a trusted node, you will be unable to access this server once the ACL
rules 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 press
Enter.
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 file
name for this server and press Enter.
The following warning appears:
WARNING: Trusted nodes must include those from which the user logs
into the current server to perform the maintenance tasks. If you
have not specified them as trusted nodes in the import file, you
will not be able to log in to the server again after the importing
has completed.
10. At the prompt Proceed (Y or N), enter y and press Enter.
Related Links
Configuring external ACL rules on page 101
104
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Configuring external ACL rules manually (using the iptcfg tool)
Before you begin
You must be able to log onto the server as a user with the System Security Administrator (SSA)
role.
About this task
Use this procedure to configure the external ACL rules using the iptcfg tool. See External ACL
configuration settings on page 108 to determine the list of trusted nodes, trusted ports, and DSCP
settings 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 integrated
audio and video.
Procedure
1. Log onto the server as a user with the SSA role.
2. At the command prompt, enter iptcfg and press Enter.
The IPTables Configurations Options menu appears.
3. At the prompt Selection [1 to 9], enter 1 to select Configure Trusted Nodes, and
press 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 node
configuration, 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 to
the 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.
The IPTables Configurations Options menu appears.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
105
Migrating from a turnkey solution to an Aura® solution
Note:
The list of trusted nodes is not added to the IPTables rules yet. The changes will be
committed to the IPTables rules after you complete this procedure.
7. At the prompt Selection [1 to 9], enter 2 to select Configure Trusted Ports, and
press 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 port
configuration, 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 port
configuration, 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 disable
the 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.
10. Enter y and press Enter to confirm your action.
The IPTables Configurations Options menu appears.
Note:
The list of trusted ports is not added to the IPTables rules yet. The changes will be
committed 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 marking
configuration, and press Enter.
The DSCP marking configuration is displayed.
106
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
b. At the prompt Selection [1 to 4], enter 2 to select Modify DSCP values, and
press Enter.
c. At the prompt Enter ID of the DSCP category to be modified, enter the ID
of 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.
18. Enter y and press Enter to confirm your action.
The IPTables Configurations Options menu appears.
Note:
The DSCP configuration changes are not added to the IPTables rules yet. The changes
will 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, and
press Enter.
20. At the prompt Proceed (Y or N), enter y and press Enter.
The following warning appears:
WARNING: Trusted nodes must include those from which the user logs
into the current server to perform the maintenance tasks. If you
have not configured these as trusted nodes, you will not be able to
log in to the server again after the configuration changes are
committed.
21. At the prompt Proceed (Y or N), enter y and press Enter.
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 correctly
and users will not be able to start or join a Web collaboration.
Related Links
Configuring external ACL rules on page 101
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
107
Migrating from a turnkey solution to an Aura® solution
Verifying the ACL configuration
Before you begin
You must be able to log onto the server as a user with the System Security Administrator (SSA)
role.
About this task
Use the following procedure to verify the ACL configuration.
Note:
You must perform this procedure on all Avaya Aura® Conferencing core servers and Avaya
Media Servers.
Procedure
1. Log onto the server as a user with the SSA role.
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 in
the import file or manually.
Note:
The full list of trusted nodes contains internal ACL trusted nodes as well as external
trusted nodes that you configured either in the import file or manually. The list of external
trusted 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 the
import 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 in
the 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.
Related Links
Configuring external ACL rules on page 101
External ACL configuration settings
The following table shows how you should configure the trusted ports, trusted nodes, and DSCP
marking on each server on the Avaya Aura® Conferencing system for each deployment layout.
108
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Table 3: External ACL configuration settings
Deployment
layout
Servers
Trusted Ports
Trusted Nodes
DSCP Marking
SMB and
medium
(simplex and
redundant)
Element Manager
servers
6000 - 42599
• DNS server
Disabled
• remote NTP servers
• remote syslog server
• remote backup server
• FTP server
• administrator PC
• Element Manager
Service address
Note:
If you do not add
the Element
Manager Service
address as a
trusted node, the
administrator
cannot launch
MCP Element
Manager.
• If you plan on
implementing automatic
disaster recovery (ADR)
in your deployment,
then you must make the
primary and secondary
Element Managers
trusted nodes of each
other. For more
information, see
Configuring ADR.
SMB and
medium with
DMZ (simplex
and redundant)
Element Manager
servers
6000–42599
• DNS server
Disabled
• remote NTP servers
• remote syslog server
• remote backup server
• FTP server
• administrator PC
• Element Manager
Service address
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
109
Migrating from a turnkey solution to an Aura® solution
Deployment
layout
Servers
Trusted Ports
Trusted Nodes
DSCP Marking
Note:
If you do not add
the Element
Manager Service
address as a
trusted node, the
administrator
cannot launch
MCP Element
Manager.
• If you plan on
implementing automatic
disaster recovery (ADR)
in your deployment,
then you must make the
primary and secondary
Element Managers
trusted nodes of each
other. For more
information, see
Configuring ADR.
Web Conferencing 443
Servers (WCS)
8140–8142
Flash Media
Gateway (FMG)
server
• DNS server
Disabled
• remote NTP servers
Note:
• remote backup server
If you do not
enable 8140–
8142, the Web
Collaboration
Service will not
operate
successfully.
• FTP server
The RTP and RTCP
ports should match
the range of the
media servers.
Enabled
Note:
By default, the
FMG RTP port
range is
40000-60000
and the media
server port
range is
6000-42599.
110
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Deployment
layout
Servers
Trusted Ports
Trusted Nodes
DSCP Marking
• DNS server
Disabled
You must
adjust one of
these range
settings to
ensure that the
FMG ports are
within the
media server
range.
Ensure that the
client configuration
file for the Audio/
Video in
Collaboration Agent
client uses the
following values:
• RTMPT: Port 80
• RTMPS: Port 443
Do not use RTMP
port 1935 or all.
Large (simplex
and redundant)
Element Manager
servers
• remote NTP servers
• remote syslog server
• remote backup server
• FTP server
• administrator PC
• Element Manager
Service address
Note:
If you do not add
the Element
Manager Service
address as a
trusted node, the
administrator
cannot launch
MCP Element
Manager.
• If you plan on
implementing automatic
disaster recovery (ADR)
in your deployment,
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
111
Migrating from a turnkey solution to an Aura® solution
Deployment
layout
Servers
Trusted Ports
Trusted Nodes
DSCP Marking
then you must make the
primary and secondary
Element Managers
trusted nodes of each
other. For more
information, see
Configuring ADR.
Web Conferencing 443
Servers (WCS)
8140–8142
Avaya Media
Servers (MS)
• DNS server
• remote NTP servers
Note:
• remote backup server
If you do not
enable 8140–
8142, the Web
Collaboration
Service will not
operate
successfully.
• FTP server
6000 - 42599
Disabled
• DNS server
Enabled
• remote NTP servers
• remote backup server
• FTP server
Flash Media
Gateway (FMG)
server
The RTP and RTCP
ports should match
the range of the
media servers.
Enabled
Note:
By default, the
FMG RTP port
range is
40000-60000
and the media
server port
range is
6000-42599.
You must
adjust one of
these range
settings to
ensure that the
FMG ports are
within the
media server
range.
112
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Deployment
layout
Servers
Trusted Ports
Trusted Nodes
DSCP Marking
Ensure that the
client configuration
file for the Audio/
Video in
Collaboration Agent
client uses the
following values:
• RTMPT: Port 80
• RTMPS: Port 443
Do not use RTMP
port 1935 or all.
Related Links
Configuring external ACL rules on page 101
Example of import.dat file
The rules for an external ACL configuration file appear in:
/opt/mcp/ipt/example/import.dat
Follow 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 Manager
servers in SMB or medium redundant and SMB or medium simplex layouts:
trusted node 192.168.209.241
192.168.209.212
trusted node 192.168.209.241
192.168.209.10
trusted node 192.168.209.241
192.168.209.20
trusted node 192.168.209.241
192.168.209.13
siptcpport 5060 0
siptcptlsport 5061 0
httpport 80 0
httpsport 443 1
dscpenabled falsed
dscpvalue
1
48
dscpvalue
2
18
dscpvalue
3
16
mediaports 6000 42599 1
Related Links
Configuring external ACL rules on page 101
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
113
Migrating from a turnkey solution to an Aura® solution
Guidelines for certificate configuration
The Certificate Authority that is used to sign certificates and the requirements for the common name
of the certificates, for each Network Element interface, is shown in the following table. The Network
Elements that require certificates to be signed by the System Manager Certificate Authority can also
be signed by another Certificate Authority instead, for example, an intermediate enterprise
Certificate Authority. In this situation, the System Manager CA is configured as an intermediate
Certificate 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 relationship
between 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 as
shown in the following table. Avaya recommends that you deploy the system with TLS enabled
and is enabled by default.
Note:
If you are using a reverse proxy in your deployment, then third party certificates are not installed
on Avaya Aura® Conferencing.
Table 4: Guidelines for certificates
This table lists the configuration guidelines for large deployments. The footnotes show the differences for SMB
and medium enterprises.
Network Element Network Element Certificate
interface
Authority
Logical Name
Common Name
Element Manager
Provisioning
Manager
114
EM Internal OAM
System Manager
EMIntOAMCert
FQDN of service
address
EM External OAM
N/A
N/A
N/A
Prov Internal
OAM HTTPS
System Manager
EMS1-FQDN-CERT
FQDN of server
address
Prov External
OAM HTTPS
N/A
N/A
N/A
CA Directory
Server
System Manager
EMS1-FQDN-Cert
FQDN of server
address
CA HTTPS
Enterprise/Public/
System Manager
EMS1-FQDN-Cert
FQDN of server
address
CA SIP
System Manager
EMS1-IP-Cert
IP address of server
address
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Network Element Network Element Certificate
interface
Authority
Logical Name
Common Name
Collaboration
Agent
CA HTTPS
Enterprise/Public/
System Manager
WCSH1-FQDNCert6
FQDN of server
address
CA Directory
Server
System Manager
WCSH1-FQDN-Cert
FQDN of server
address
CA SIP
System Manager
WCSH1-IP-Cert7
IP address of server
address
Application Server AS SIP
System Manager
ASSIPCert
IP address of the
service address
EMS1-FQDN-Cert
FQDN of server
address
MS1S1-IP-CERT7
MS1S1-IP-CERT7
IP address of server
address
AS Directory
Server
Media Server
Media Server SIP
System Manager
Media Server
SOAP
Document
Conversion
Server
DCS HTTPS
System Manager
WCSH1-FQDNCert6
FQDN of server
address
Web
Conferencing
Management
Server
WCMS HTTPS
System Manager
EMS1-IP-Cert
IP address of server
address
Web
Conferencing
Server8
WCS HTTPS
Enterprise/Public/
System Manager
WCS1Cert
FQDN of service
address or wildcard.
An example wildcard is
*.mydomain.com
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
6
7
8
For SMB and medium size deployments, use the existing EMS1-FQDN-Cert and EMS2-FQDN-Cert.
For SMB and medium size deployments, use the existing EMS1-IP-Cert and EMS2-IP-Cert.
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
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
115
Migrating from a turnkey solution to an Aura® solution
Obtaining enrollment password from System Manager
The trust management services enables auto enrollment for certificates from System Manager. You
are required to know the enrollment password when requesting certificates from the System
Manager. If you already know the enrollment password, you can skip this procedure.
About this task
Use the following procedure to obtain the enrollment password.
Procedure
1. 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 password
for use in the following procedure.
6. On the Security tab, click x to close the Security window.
Next steps
Proceed to Creating Network Element certificates signed by the System Manager on page 116.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Creating Network Element certificates signed by System Manager
The System Manager can be used on your network as a Certificate Signing Authority for Network
Elements that require certificates. Integration with the System Manager Trust Management service
allows 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 begin
You must know the enrollment password as completed in Obtaining enrollment password from
System Manager on page 116.
About this task
Use the following procedure to create X.509 Certificates signed by the System Manager for any
Network Elements created after the initial installation, or to create new certificates when necessary.
Procedure
1. In the Address box of the Web browser, enter the following address: https://:
12121
116
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
where is the EM Internal OAM Service IP address. (This is the logical IP address of
the server running Element Manager Console.)
Note:
This is a secure site. If you get a certificate error message, follow the instructions on
your 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 Element
Manager Console.
3. On the page, click Launch Element Manager Console.
4. From the IPv4 Service Address box on the Element Manager Console window, select the
FQDN/IP address of the server running Element Manager.
5. Click Connect.
6. On the Element Manager Authentication window, click the Accept the certificate for this
session 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 > Certificate
Management > 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 specific
managed network element, for example, Provisioning Manager NE.
• Bit length: Select 1024, 2048, or 4096 from the list. If your security policy does not
specify 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 values
for certificates that use the System Manager as the Certificate Signing Authority.
• Enrollment password: This password must match the current Enrollment Password that
is configured on System Manager.
13. Click Submit.
Result
The certificate is automatically installed on the Element Manager Keystore.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
117
Migrating from a turnkey solution to an Aura® solution
Note:
Prior to certificate expiry, Avaya recommends that you generate a new certificate using a new
logical name and then refresh the certificate by changing the network element to use the new
logical name. The expired certificate can then be removed from the Element Manager Keystore.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Element Manager
Note:
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 an
FQDN 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 task
Use the following procedure to assign a new certificate to the Element Manager.
Procedure
1. Log on to the Element Manager Console.
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 logical
name, for example, EMIntOAMCert.
6. Click Apply.
7. Click File > Exit on the Element Manager Console to exit.
118
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
8. Log on to EMServer with an account using the AA role, such as, ntappadm, through SSH or
directly 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 previously
trusted by the Element Manager Console, an Element Manager Authentication Dialog
window appears. Select Store the certificate’s signing certificate authority as a trusted
certificate for this and future connections
14. Click Apply.
Next steps
Proceed to Assigning a new certificate to the Provisioning Manager on page 119.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Provisioning Manager
Note:
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 an
FQDN change, a certificate expiry, or a certification revocation.
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 Common
Name.
• The certificate has been signed by a CA that the System Manager trusts. This is typically the
System Manager CA.
Note:
If the Provisioning Manager is online, it will require a restart of the Network Element Instance
afterwards.
About this task
Use the following procedure to assign a certificate to the Provisioning Managers.
Procedure
1. Log on to the Element Manager Console.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
119
Migrating from a turnkey solution to an Aura® solution
2. In the navigation pane of Element Manager Console, select Feature Server Elements >
Provisioning Managers.
3. In the Provisioning Managers window, select the PROV1.
4. Click Edit (-/+).
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:
• Enable HTTP Port: Clear the check box.
• 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 SIP
certificate by logical name, for example, PA1SIPCert.
Note:
The certificates in the PA submenus are required only when the PA is co-hosted with the
Provisioning Manager.
6. Click Apply.
7. Repeat this procedure for any additional Provisioning Managers.
Next steps
Proceed to Assigning a new certificate to the Collaboration Agent Manager on page 120.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Collaboration Agent Manager
Note:
This procedure is specific to large deployments with redundancy and large simplex
deployments. If you have an SMB or a medium deployment with redundancy or an SMB or a
medium deployment simplex deployment, you can skip this procedure.
The large deployment layouts make use of independent Collaboration Agent Manager Network
Elements to provide support for physical separation from the Provisioning Manager Network
Element for security and scalability.
120
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Before you begin
Certificates 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 Element
Instance afterwards.
About this task
Use the following procedure to assign a certificate to the Collaboration Agent Manager.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Collaboration Agent.
2. In the Collaboration Agent Managers window, select CA1.
3. Click Edit (-/+).
4. In the Edit Collaboration Agent dialog box, complete the following fields:
• Enable HTTP Port: Clear the check box.
• PA HTTPS Certificate: Select the required HTTPS certificate by logical name, for
example, CA1Cert.
• SIP Certificate: If the Enable SIP TLS Port option is enabled, select the required SIP
certificate by logical name, for example, CA1SIP.
5. Click Apply.
Next steps
Proceed to Assigning a new certificate to the Application Server on page 121.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Application Server
Note:
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 an
FQDN change, a certificate expiry, or a certification revocation.
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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
121
Migrating from a turnkey solution to an Aura® solution
Note:
If the Application Server is online, it will require a restart of the Network Element Instance
afterwards.
About this task
Use the following procedure to assign a certificate to the Application Server.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Application Servers.
2. In the Application Servers window, select AS1.
3. Click Edit (-/+).
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 SIP
certificate by logical name, for example, ASSIPCert
5. Click Apply.
Next steps
Proceed to Assigning a new certificate to the Avaya Media Server on page 122.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Avaya Media Server
Before 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 task
Use the following procedure to assign a new certificate the Avaya Media Server.
Procedure
1. 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.
3. Click Edit (-/+).
122
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
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 from
the 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 appropriate
certificate 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 steps
Proceed to Assigning a new certificate to the Web Conferencing Server on page 123.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Web Conferencing Server
Before you begin
A new certificate with a common name using the FQDN of the Web Conferencing Server must exist
in the Element Manager Keystore.
Note:
If the Web Conferencing Server is online, it will require a restart of the Network Element
Instance afterwards.
About this task
Use the following procedure to assign a new certificate to the Web Conferencing Server.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Web Conferencing > Web Conferencing Servers.
2. In the Web Conferencing Server window, select WCS1.
3. Click Edit (-/+).
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 steps
Proceed to Assigning a new certificate to the Web Conferencing Management Server on page 124.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
123
Migrating from a turnkey solution to an Aura® solution
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Assigning a new certificate to the Web Conferencing Management
Server
Note:
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 an
FQDN change, a certificate expiry, or a certification revocation.
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 task
Use the following procedure to assign a new certificate to the Web Conferencing Management
Server.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Web Conferencing > Web Conferencing Management Servers.
2. In the Web Conferencing Manager Servers window, select WCMS1.
3. Click Edit (-/+).
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 the
logical names in the Keystore, for example, EMS1-IP-Cert.
5. Click Apply.
Next steps
Proceed to Assigning a new certificate to the DCS on page 125.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
124
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
Assigning a new certificate to the DCS
Before you begin
• A new certificate for the Document Conversion Server (DCS) 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 task
Use the following procedure to assign a new certificate to the DCS.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Document Conversion Servers > Document Conversion Servers.
2. In the Document Conversion Servers window, select the DCS, for example, DCS1.
3. Click Edit (-/+).
4. In the Edit DCS dialog box, complete the following field:
• HTTPS Certificate: Select the required certificate from the list. This list corresponds to the
logical 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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Starting an Element Manager instance from the server console
About this task
Use the following procedure to start the primary Element Manager, database, and other network
elements.
Procedure
1. 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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
125
Migrating from a turnkey solution to an Aura® solution
2. Type cd /var/mcp/install, and press Enter.
3. Type ./emStart.pl, and press Enter.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring single sign-on for Element Manager Console and
Provisioning Client
Introduction
System Manager is a central management system that delivers a set of shared management
services and a common console across multiple products. With single sign-on (SSO) enabled for
Avaya Aura® Conferencing, you can administer all the components using System Manager. This
chapter provides the procedures to configure SSO, configure System Manager to recognize each
network element, and configure the administrator PC.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring time on System Manager and network elements
About this task
To use single sign-on (SSO), System Manager and all the network elements must have
synchronized clocks. A clock skew of a few seconds results in SSO to fail. If the Home portlet is
missing menus or functions, logon access to the Element Manager Console or Provisioning Client
can fail.
Note:
Ensure your servers use the Network Time Protocol (NTP) time sources.
Procedure
1. 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 NTP
server in the Manage Time Servers area. If only Local Clock displays, add at least one NTP
server and in the Added Servers field, and click start ntpd. Use the Primary Clock Source
and Secondary Clock Source values, and check the Local Time value.
Warning:
Clicking start ntpd causes the system platform and server to restart.
126
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
4. Open an SSH connection and log into EMServer1 as ntsysadm to verify the time on the
server.
5. Type date, and press Enter.
6. Compare the time on the System Platform Console with the time on the application server. If
the time difference between the System Platform Console and the application server is
greater 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 the
time difference between the System Platform Console and the application server is still
greater than 60 seconds, perform Steps G through K to correct the date and time
manually 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 ntpd
service.
i. Run /usr/sbin/ntpdate to update the
system 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 steps
Proceed to configuring network element FQDNs in System Manager.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring the application server network elements on System Manager
About this task
Details of each Network Element must be added in the System Manager inventory so that it is
possible to launch the Network Elements directly from System Manager. To configure details of
each Element Manager, use the following procedure.
Note:
System Manager must have only PROVs from one Avaya Aura® Conferencing system in your
inventory. If you have another Avaya Aura® Conferencing system, and you enter the PROV
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
127
Migrating from a turnkey solution to an Aura® solution
elements in the System Manager inventory, you can encounter problems. System Manager
always sends conferencing profile data to one PROV. The data is sent to the first available
PROV in the inventory.
Note:
To use single sign-on (SSO), the System Manager FQDN, Element Manager FQDN, and
Provisioning Client FQDN (if required) must belong to the same root domain.
Procedure
1. 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.
128
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
• 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 steps
Proceed to Launching Element Manager Console and Provisioning Client from System Manager.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Launching Element Manager Console and Provisioning client from System
Manager
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 and
Element Manager and Provisioning Client elements. By default, administrators with either
Network Administrator or System Administrator roles have read, write, and expert mode
permissions. You can change role assignments and configure permissions for access to various
elements. On System Manager home page, click Users > Administrators.
Warning:
If you have Expert mode privileges, you see an Expert mode warning on certain Provisioning
Client 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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
129
Migrating from a turnkey solution to an Aura® solution
About this task
Use the following procedure to launch the Element Manager Console and Provisioning Client from
System Manager.
Procedure
1. Log on to System Manager.
2. On the System Manager console, click Elements > Conferencing.
3. On the Conferencing Dashboard page, in the Name column, select the name of Element
Manager Console.
4. From the IPv4 Service Address box on the Element Manager Console window, select the IP
address 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 Manager
Console.
7. On the Conferencing Dashboard page, in the Name column, select the name of Element
Manager 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.
Result
The Element Manager Console and Provisioning client can now be launched from System Manager.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Configuring the route to Avaya Aura® Conferencing on System
Manager
About this task
Use the following procedure to configure the route to Avaya Aura® Conferencing from System
Manager.
Procedure
1. 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.
130
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
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 Manager
entity.
• 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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
131
Migrating from a turnkey solution to an Aura® solution
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 part
of 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 minimum
number of digits in the dialing number.
22. In the Max box, type the number of digits that match the pattern number. This is the
maximum 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 Avaya
Aura® Conferencing.
26. Click Select.
27. Click Commit.
Result
You have configured the routing policy so that when you dial a number that contains the pattern you
specified, your call goes to the Avaya Aura® Conferencing Application Server.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
132
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
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
About this task
Use the following procedure to create a certificate for the Flash Media Gateway IP address that is
signed by System Manager.
Procedure
1. Log on to 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. For
example, 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.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
133
Migrating from a turnkey solution to an Aura® solution
Configuring a secure SIP TLS connection from the Flash Media
Gateway to Avaya Aura® Session Manager
About this task
Use this procedure to configure a secure SIP TLS connection from the Flash Media Gateway to
Avaya Aura® Session Manager.
Procedure
1. 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://:8443/
fmgadmin/index.html where is the IP address or FQDN
of 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 and
upload the file.
• Key Store Password: Enter the password from Step 3 in Creating a System Managersigned certificate for the Flash Media Gateway IP address on page 133.
134
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
15. Click Save.
16. Go to the Flash Media Gateway on the Management Portal client and restart all Flash Media
Gateways.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Changing the system default settings to use Avaya Aura®
Conferencing (AAC)
About this task
Use this task to enable Allow Bandwidth Management and disable User Password Owned
Locally in the Provisioning Client
Procedure
1. 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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Removing the dialing rules in Provisioning Client
About this task
Use this task to remove the dialing rules in Provisioning Client. Remember, there are two types of
dialing rules: Pretranslation rules and Translation rules.
Procedure
1. 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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
135
Migrating from a turnkey solution to an Aura® solution
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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Removing all SIP entities for PBXs in Element Manager
About this task
Use this task to remove all SIP entities for PBXs in the Element Manager GUI.
Procedure
1. 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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
Removing all the old certificates on Turnkey
About this task
Use this task to remove all the old certificates on the Turnkey solution in the Element Manager GUI.
Procedure
1. 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.
136
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating from Avaya Aura® Conferencing turnkey to Avaya Aura® Conferencing with the full Avaya Aura® platform
4. Repeat steps 1-3 for all the old certificates you want to remove.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from Avaya Aura Conferencing turnkey to Avaya Aura Conferencing with the full Avaya
Aura platform on page 93
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
137
Chapter 5: Migrating from a DMZ solution
to an enterprise solution
Migrating Avaya Aura® Conferencing components from the
DMZ to the Enterprise
This section describes how to move Avaya Aura® Conferencing components from the Demilitarized
Zone (DMZ) back to the enterprise. In the DMZ, Avaya Aura® Conferencing components are
accessible to external users. By moving these components into the enterprise, they are no longer
accessible to external users through the DMZ.
However, Avaya Aura® Conferencing 8.0 now supports Application Delivery Controllers (ADCs). You
can provide external access to Avaya Aura® Conferencing using this new ADC functionality. The
ADC functionality is now the recommended method for the provision of external access. ADCs offer
load balancing capabilities as well as providing a reverse proxy. One of the key benefits of using an
ADC in the solution is that the number of firewall rules required is greatly reduced, simplifying
configuration and maintenance of the solution.
However, if you wish to offer integrated audio and video to external users who reside outside of the
enterprise, using the new Avaya Web Collaboration audio and video plug-in, then you must install
and configure a Session Border Controller (SBC). You cannot continue to offer integrated audio and
video to external users when you move the Avaya Aura® Conferencing components from the DMZ
to the enterprise unless you also install and configure an SBC. In this context, “integrated audio and
video” means that users can receive their audio and their video feeds through the Web. This
functionality 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 other
participants.
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 complete
the migration from the DMZ into the enterprise. Ensure that you have downloaded and opened
these guides before working your way through the migration steps.
138
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating Avaya Aura® Conferencing components from the DMZ to the Enterprise
No.
Task
Description
1
Ensure that you have the
appropriate ADC
hardware configured in
the DMZ.
Avaya recommends using
an Application Delivery
Controller to allow external
access. See Configuring a
reverse proxy in Deploying
Avaya Aura® Conferencing:
Advanced Installation and
Configuration.
2
Ensure that you have the
appropriate hardware
configuration for this
deployment.
See Deployment Options in
Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
3
Install the appropriate
software on the
enterprise server(s) and
ensure that you apply the
appropriate patches.
See Installing software in
Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
4
Migrate the Collaboration Migrating the Collaboration
Agent Manager network
Agent Manager from the
element(s) to an
DMZ on page 140
additional Avaya Aura®
Conferencing Web
Server in the enterprise
or remove and configure
use of the Collaboration
Agent through the
Provisioning Manager in
the enterprise data
center depending on the
appropriate deployment
layout.
5
Configure the virtual
services on the ADC for
the Collaboration Agent.
See Configuring a reverse
proxy in Deploying Avaya
Aura® Conferencing:
Advanced Installation and
Configuration.
6
Migrate the Web
Conferencing network
elements from the
servers in the DMZ to
either the Element
Manager Server(s) or an
additional Avaya Aura®
Conferencing Web
Server(s) in the
Migrating the Web
Conferencing Server from
the DMZ on page 142
August 2014
Notes
Migrating Avaya Aura® Conferencing
Comments? [email protected]
139
Migrating from a DMZ solution to an enterprise solution
No.
Task
Description
Notes
enterprise data center
depending on
appropriate deployment
layout.
7
Configure the virtual
services on the ADC for
the Web Conferencing
server.
See Configuring a reverse
proxy in Deploying Avaya
Aura® Conferencing:
Advanced Installation and
Configuration.
8
If your deployment
supports Audio/Video in
Collaboration Agent,
install it on the identified
server in the enterprise.
See Deploying integrated
audio and video in
Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
If your deployment
supports the new Avaya
Web Collaboration audio
and video plug-in,
configure it on the
identified server in the
enterprise.
9
Uninstall the Audio/Video
in Collaboration Agent
software on the identified
server in the DMZ.
See Uninstalling software
in Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
10
Configure ACL rules on
the Avaya Aura®
Conferencing server to
reflect network topology
changes if they were
used.
Configuring the access
control list on page 99
If you wish to offer the
new Avaya Web
Collaboration audio and
video plug-in to external
users who reside outside
of the enterprise, you
must add and configure a
Session Border Controller
(SBC). An SBC is
essential for external
access to this feature.
The steps for installing
and configuring your SBC
are in Deploying Avaya
Aura® Conferencing:
Advanced Installation and
Configuration.
Migrating the Collaboration Agent Manager from the DMZ
Before you begin
Ensure that you:
• Install and configure an Application Delivery Controller (ADC) in the DMZ.
140
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating the Collaboration Agent Manager from the DMZ
• Acquire a certificate for the virtual server on the ADC that fronts the Collaboration Agent.
About this task
Use 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 Collaboration
Agent services. In this case, you must undeploy and remove the Collaboration Agent network
element instead of moving it into the internal enterprise.
Avaya recommends using an ADC to allow external access. If this is a redundant deployment and is
already using an ADC to load balance and provide high availability, you can move one Collaboration
Agent instance at a time. You can do this by disabling the Collaboration Agent instance that you are
moving at the ADC and then changing the internal address at the ADC prior to enabling the
Collaboration Agent network instance again. This process ensures that the ADC can continue to
route Collaboration Agent traffic to other Collaboration Agent instances during the move. Any
existing connections, however, are lost and userz must reconnect and login again to the other
Collaboration Agent.
Procedure
1. 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 the
new server, otherwise skip to step 4.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Collaboration Agent Managers > > Instance.
b. In the Instance dialog, select the
Collaboration Agent network element instance.
c. Click Edit (-/+).
d. In the Edit Instance dialog, select the Web
Server from the Server list. For example, WCSServer1.
e. Click Apply.
4. If this is an SMB or medium deployment, undeploy and remove the Collaboration Agent
network elements. The Provisioning Manager network element provides Collaboration Agent
functionality as a subsystem of the Provisioning Manager.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Collaboration Agent Managers > > Instance.
b. In the Instance dialog, select the
Collaboration Agent network element instance.
c. Click Delete (-).
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
141
Migrating from a DMZ solution to an enterprise solution
d. Click Yes to confirm.
5. Change the certificate configured for the Collaboration Agent HTTPS Certificate in
accordance 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 a
network element instance on page 156.
7. Configure the Application Delivery Controller (ADC).
See Configuring a reverse proxy in Deploying Avaya Aura® Conferencing: Advanced
Installation 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 is
available on http://support.avaya.com/.
9. Repeat these steps for any additional Collaboration Agent network elements.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Migrating the Web Conferencing Server from the DMZ
Before you begin
Ensure that you:
• Acquire new IPv4 addresses for each Web Conferencing Server service address on the subnet
to 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 Web
Conferencing Server cluster. This virtual server will have the Web Conferencing Server cluster
Fully Qualified Domain Name (FQDN) assigned to it using the Domain Name Server (DNS) and
the certificate must be assigned against this FQDN. Otherwise, there must be a one-to-one
mapping between virtual servers on the ADC and Web Conferencing Servers in the Web
Conferencing Server cluster with a certificate for each virtual server.
142
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating the Web Conferencing Server from the DMZ
About this task
Use this task to move a Web Conferencing Server in the DMZ to the internal enterprise network. In
order to continue to provide external access, Avaya recommends using an Application Delivery
Controller.
Procedure
1. Stop all instances of the Web Conferencing Servers (WCS) in the Web Conferencing Server
cluster.
For more information, see Stopping a network element instance on page 43.
2. Undeploy all Web Conferencing Server instances.
For more information, see Undeploying a network element instance on page 154.
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 simplex
deployment, change the server configuration for the Web Conferencing Server network
element instance to EMServer1.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Web Conferencing > Web
Conferencing Servers > >
Instances.
b. In the Instance dialog, select the Web Conferencing
Server network element instance.
c. Click Edit (-/+).
d. In the Edit 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 the
cluster.
4. Change the Web Conferencing Server address for each Web Conferencing Server in the
cluster.
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 Server
service address.
c. Click Edit (-/+).
d. Modify the IPv4 address to be the new IPv4 address for the Web Conferencing Server
service address.
e. Click Apply.
f. Repeat these steps for any additional Web Conferencing Server instances in the
cluster.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
143
Migrating from a DMZ solution to an enterprise solution
5. Change the certificate configured for the Web Conferencing Server in accordance with the
guidelines for certificate configuration.
For more information, see Guidelines for certificate configuration on page 114.
6. Deploy and start the Web Conferencing Server network elements.
For more information, see Deploying a Network Element instance on page 82 and Starting a
network element instance on page 156.
7. Configure the Application Delivery Controller (ADC).
See Configuring a reverse proxy in Deploying Avaya Aura® Conferencing: Advanced
Installation 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 is
available on http://support.avaya.com/.
9. Repeat these steps for any additional Web Conferencing Server clusters.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
144
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Chapter 6: Migrating from an enterprise
solution to a DMZ solution
Migrating from an enterprise solution to a DMZ solution
This section describes how to move Avaya Aura® Conferencing components from the enterprise to
the Demilitarized Zone (DMZ). In the DMZ, Avaya Aura® Conferencing components are accessible
to external users. In this context, “Avaya Aura® Conferencing components” refers to the Web
Conferencing Server (WCS) and the Collaboration Agent (CA) network element instances.
No.
Task
Description
1
Ensure that you have the
appropriate ADC
hardware configured in
the DMZ.
Avaya recommends using
an Application Delivery
Controller to allow external
access. See Configuring a
reverse proxy in Deploying
Avaya Aura® Conferencing:
Advanced Installation and
Configuration.
2
Install the appropriate
software on the
enterprise server(s) and
ensure that you apply the
appropriate patches.
See Installing software in
Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
Notes
Ensure that you configure
the recommended security
hardening in the DMZ for
deploying Web
Conferencing Server and
Collaboration Agent
network element
instances.
See the Avaya Aura®
Conferencing Port Matrix
Guide.
3
Disable the Access
Control List (ACL) rules
on Avaya Aura®
Conferencing servers.
4
Add a new DMZ server in Adding a new DMZ server
the Element Manager
in the Element Manager
GUI.
GUI on page 146
August 2014
Configuring the access
control list on page 99
Migrating Avaya Aura® Conferencing
Comments? [email protected]
145
Migrating from an enterprise solution to a DMZ solution
No.
Task
Description
5
Migrate the Web
Conferencing Server
(WCS) network element
instance to the DMZ.
Migrating the Web
Conferencing Server to the
DMZ on page 149
6
Migrate the Collaboration Migrating the Collaboration
Agent (CA) network
Agent Manager to the
element instance to the
DMZ on page 147.
DMZ.
7
Uninstall the Audio/Video
in Collaboration Agent
software on the identified
server in the Enterprise.
See Uninstalling software
in Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
8
If your deployment
supports Audio/Video in
Collaboration Agent,
install it on the identified
server in the DMZ.
See Deploying integrated
audio and video in
Deploying Avaya Aura®
Conferencing: Advanced
Installation and
Configuration.
If your deployment
supports the new Avaya
Web Collaboration audio
and video plug-in,
configure it on the
identified server in the
DMZ.
9
Configure ACL rules on
the Avaya Aura®
Conferencing server to
reflect network topology
changes if they were
used.
Notes
Configuring the access
control list on page 99
Adding a new DMZ server in the Element Manager GUI
About this task
Use this task to add a new DMZ server to the Element Manager interface.
Procedure
1. Add a new IP address for the DMZ server:
a. In the navigation pane of the Element Manager Console, select Addresses.
b. In the Addresses window, click Add (+).
146
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating the Collaboration Agent Manager to the DMZ
c. In the Add IPv4 Address dialog, enter the logical name DMZSvrIntOAMAddr and the
IP 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.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Migrating the Collaboration Agent Manager to the DMZ
About this task
Use this task to move the Collaboration Agent to the DMZ.
If this is an SMB or medium deployment, the Provisioning Manager also provides Collaboration
Agent services. In this case, you must create new Collaboration Agent instance on the DMZ server.
Procedure
1. 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 the
new server. If this is an SMB or medium deployment, skip this step.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Collaboration Agent Managers > > Instance.
b. In the Instance dialog, select the
Collaboration Agent network element instance.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
147
Migrating from an enterprise solution to a DMZ solution
c. Click Edit (-/+).
d. In the Edit Instance dialog, select the Web
Server 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 network
element. If this is a large deployment, skip this step.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > 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 Server
Elements > Collaboration Agent Managers > >
Instance.
f. Click Add (+).
g. Enter information in all of the required details.
h. In the Add Instance dialog, select the Web
Server from the Server list. For example, DMZServer.
i. Click Apply to confirm.
4. Change the certificate configured for the Collaboration Agent HTTPS Certificate in
accordance with the guidelines for certificate configuration.
For more information, see Guidelines for certificate configuration on page 114.
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 medium
deployment, start the Collaboration Agent and Provisioning Manager network elements.
For more information, see Starting a network element instance on page 156.
7. Update the firewall rules for the DMZ firewall to reflect these changes.
For more information, see the Avaya Aura® Conferencing Port Matrix Guide, which is
available on http://support.avaya.com/.
8. Repeat this procedure for any additional Collaboration Agent network elements.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
148
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Migrating the Web Conferencing Server to the DMZ
Migrating the Web Conferencing Server to the DMZ
Before you begin
Ensure that you acquire new IPv4 addresses for each Web Conferencing Server service address on
the subnet to which the Web Conferencing Server is moving.
About this task
If you have a deployment that has the Web Conferencing Server in the internal network, use this
task to move the Web Conferencing Server to the DMZ.
Procedure
1. Stop all instances of the Web Conferencing Servers (WCS) in the Web Conferencing Server
cluster.
For more information, see Stopping a network element instance on page 43.
2. Undeploy all Web Conferencing Server instances.
For more information, see Undeploying a network element instance on page 154.
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 the
server configuration for the Web Conferencing Server network element instance to
DMZServer.
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Web Conferencing > Web
Conferencing Servers > >
Instances.
b. In the Instance dialog, select the Web Conferencing
Server network element instance.
c. Click Edit (-/+).
d. In the Edit Instance, select the destination Avaya Aura®
Conferencing server from the Server list. For example, DMZServer.
e. Click Apply.
f. Repeat these steps for any additional Web Conferencing Server instances in the
cluster.
4. Change the Web Conferencing Server address for each Web Conferencing Server in the
cluster.
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 Server
service address.
c. Click Edit (-/+).
d. Modify the IPv4 address to be the new IPv4 address for the Web Conferencing Server
service address.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
149
Migrating from an enterprise solution to a DMZ solution
e. Click Apply.
5. Change the certificate configured for the Web Conferencing Server in accordance with the
guidelines for certificate configuration.
For more information, see Guidelines for certificate configuration on page 114.
6. Deploy and start the Web Conferencing Server network elements.
For more information, see Deploying a Network Element instance on page 82 and Starting a
network element instance on page 156.
7. Update the firewall rules for the DMZ firewall to reflect these changes.
For more information, see the Avaya Aura® Conferencing Port Matrix Guide, which is
available on http://support.avaya.com/.
8. Repeat the above steps to move any other Web Conferencing Server clusters.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
150
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Chapter 7: Migrating the Web Conferencing
Management Server (WCMS) to
the 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 not
have redundancy (simplex layouts).
For the Avaya Aura® Conferencing 7.0 release, the WCMS resided on a separate server in the
DMZ. From the Avaya Aura® Conferencing 7.2+ release onwards, Avaya moved the WCMS from
the separate server in the DMZ to the Element Manager (EM) server in the enterprise. If you have
an 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 two
WCMS instances. For more information, see Updating the Web Conferencing Management Server
resync on page 154.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
151
Migrating the Web Conferencing Management Server (WCMS) to the enterprise
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 task
Use this task to move the WCMS from a separate server in the DMZ to the EM server in the
enterprise.
152
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Procedure
1. 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 > Web
Conferencing Management Servers > > 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 for
certificate configuration.
For more information about security and Avaya Aura® Conferencing, see Deploying Avaya
Aura® 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 management
server on page 156.
7. Ensure that TCP port 8444 is open between the DMZ and the enterprise to allow connectivity
between the Collaboration Agent and the WCMS.
For more information, see the Avaya Aura® Conferencing Port Matrix Guide, which is
available on http://support.avaya.com/.
8. Start all stopped WCMS, WCS, PA, and PROV network element instances.
See Starting a network element instance on page 156.
Related Links
Updating the Web Conferencing Management Server (WCMS) Rsync configuration on page 154
Undeploying a network element instance on page 154
Deploying a network element instance on page 82
Configuring the meeting event processor for the Web conferencing management server on
page 156
Starting a network element instance on page 156
Cleaning up the library files on page 157
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
153
Migrating the Web Conferencing Management Server (WCMS) to the enterprise
Updating the Web Conferencing Management Server
(WCMS) Rsync configuration
About this task
Use this task to update Web Conferencing Management Server (WCMS) rsync configuration.
Procedure
1. 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.
2. At the prompt, type su – and press Enter.
3. Type the root password, and then press Enter to become the root user.
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 IP
address 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 the
secondary Element Manager server, and press Enter.
Result
Web Conferencing Management Server rsync configuration is updated.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
Undeploying a network element instance
About this task
Use this procedure to undeploy a network element instance.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements>
> > NE
Maintenance.
2. In the Maintenance window, select the row that has a value of the target instance in the ID
column.
154
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Deploying a network element instance
3. Click Undeploy.
The Maint state changes from None to Undeploying, indicating that the undeploy operation
is in progress. When the undeploy operation is complete, the Maint state changes back to
None.
4. Close the Maintenance window.
Result
The network element instance is undeployed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
Deploying a network element instance
About this task
Use this procedure to deploy a network element instance.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements>
> NE
Maintenance.
2. In the Maintenance dialog box, select the row that has a value of the target instance in the ID
column.
3. Click Deploy.
The Maint state changes from None to Deploying, indicating that the deploy operation is in
progress. When the deploy operation is complete, the Maint state changes back to None,
and the Admin state changes from Configured to Offline.
4. Close the Maintenance window.
Result
The Network Element instance is deployed.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating from bare metal to VM for a medium simplex deployment on page 74
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
155
Migrating the Web Conferencing Management Server (WCMS) to the enterprise
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
Configuring the meeting event processor for the Web
conferencing management server
About this task
Use the following procedure to configure the meeting event processor.
Procedure
1. In the navigation pane of Element Manager Console, select Feature Server Elements >
Web Conferencing > Web Conferencing Management Servers > > Meeting Event Processing.
2. From the Meeting Event Processor box, select the Provisioning Manager or Collaboration
Agent for managing meeting events.
3. Click Apply.
Related Links
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
Starting a network element instance
About this task
Use this procedure to start a network element instance.
Procedure
1. Log on to the Element Manager Console.
2. 1. In the navigation pane of Element Manager Console, select Feature Server Elements >
> > NE
Maintenance.
3. In the Maintenance window, select the row that has a value of the target instance in the ID
column.
4. Click Start.
The Maint state changes from None to Starting, indicating that the restart operation is in
progress. 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.
156
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Cleaning up the library files
• The Oper state changes from Unavailable to either Active or Hot Standby, based on the
instance of the component.
5. Close the Maintenance window.
Result
The network element instance is up and running.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
Cleaning up the library files
Before you begin
Ensure that you have completed the resync. For more information, see Updating the Web
Conferencing Management Server resync on page 154.
About this task
Use this task to remove (or move) the old library files from the DMZ server.
Procedure
1. 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/*.
Result
This command removes the old library files from the server.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Migrating the Web Conferencing Management Server (WCMS) to the enterprise on page 151
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
157
Chapter 8: Adding redundancy to your
solution
Expanding from a medium non-redundant deployment to a
medium redundant deployment
If you have an SMB or a medium Avaya Aura® Conferencing solution without any redundancy, you
can 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 Links
Reference configurations for medium enterprises on page 158
Checklist for expanding an SMB or medium non-redundant deployment to a redundant
deployment on page 160
Adding secondary Element Manager server and secondary media and Web conferencing server
hosts on page 162
Adding secondary Element Manager server hosts on page 163
Installing and configuring a secondary database instance on page 164
Reference configurations for medium enterprises
There 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
158
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium non-redundant deployment to a medium redundant deployment
Figure 5: Medium Simplex Configuration
Figure 6: Medium Redundant Configuration
Related Links
Expanding from a medium non-redundant deployment to a medium redundant deployment on
page 158
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
159
Adding redundancy to your solution
Checklist for expanding an SMB or medium non-redundant
deployment to a redundant deployment
No.
Task
Description
1
Disable the Access
Control List (ACL) rules
on Avaya Aura®
Conferencing server if
they are used
Configuring the access
control list on page 99
2
Install the Avaya Aura®
Installing the platform on
Conferencing platform on page 49
the secondary Element
Manager server
3
Install the Avaya Media
Server (MS) platform on
the secondary Element
Manager server
Installing Avaya Media
Server on page 64
4
Add the secondary
Element Manager
server host
Adding secondary Element
Manager server hosts on
page 163
5
Stop all the network
Stopping a network
element instances except element instance on
the Element Manager
page 43
6
Add and deploy
secondary network
element instances on the
secondary Element
Manager server:
• Provisioning Manager
• Web Conferencing
Management Server
Notes
For more information, see
Deploying Avaya Aura®
Conferencing and
Administering Avaya Aura®
Conferencing, which are
available from the Avaya
Support website:http://
www.avaya.com/support
• Document Conversion
Server
• Web Conferencing
Server
• Media Server
• Element Manager
• Accounting Manager
• Application Server
160
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium non-redundant deployment to a medium redundant deployment
No.
Task
Description
7
Create and assign new
certificates to all new
network element
instances
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
8
Add and configure new
Media Server to existing
Media Server cluster
For more information, see
Administering Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
9
Add and configure new
Web Conferencing
Server to existing Web
Conferencing Server
cluster
For more information, see
Administering Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
10
Stop an Element
Manager instance
Stopping an Element
Manager Instance on
page 44
11
Install and configure
secondary database
instance
Installing and configuring a
secondary database
instance on page 164
12
Start all the network
element instances
Starting a network element
instance on page 156
Notes
Starting an Element
Manager instance from the
server console on
page 125
13
Configuring Web
Conferencing
Management Server
Rsync
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
14
Configure Audio/Video in
Collaboration Agent on
the Secondary Element
Manager Server
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
15
Configure ACL rules on
Avaya Aura®
Conferencing server to
Configuring the access
control list on page 99
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
161
Adding redundancy to your solution
No.
Task
Description
Notes
reflect network topology
changes if they were
used
16
Verify that the Avaya
Aura® Conferencing
system is operating
correctly
Verifying the system on
page 68
Related Links
Expanding from a medium non-redundant deployment to a medium redundant deployment on
page 158
Adding secondary Element Manager server and secondary media
and Web conferencing server hosts
About this task
Use this task to add a secondary Element Manager server and secondary media and Web
conferencing server hosts.
Procedure
1. In the navigation pane of Element Manager Console, select Addresses.
2. In the Addresses window, click Add (+).
3. In the Add IPv4 Address dialog box, enter the logical name EMSvr2IntOAMAddr and IP
address of the secondary Element Manager server.
4. Click Apply.
5. Repeat these steps to add new IP addresses for the secondary media and Web
conferencing server with the logical name MWCSvr2IntOAMAddr.
6. Repeat the steps again to add a service IP address for the secondary Web
conferencing server with the logical name WCS2SvcAddr.
7. Repeat the steps once again to add a media IP address for the secondary media server with
the 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:
162
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium non-redundant deployment to a medium redundant deployment
• Internal OAM (Default) Address: EMSvr2IntOAMAddr
• Operating System: linux.
11. Click Apply .
12. In the Servers window, click Add (+).
13. In the Add Server dialog box, complete the following fields:
• Short Name: MWCS2
• Long Server Name: MWCServer2
• Physical Site:
• Internal OAM (Default) Address: MWCSvr2IntOAMAddr
• IPv4 Media Address: MWCSrv2MediaAddr
• Operating System: linux
14. Click Apply.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium non-redundant deployment to a medium redundant deployment on
page 158
Adding secondary Element Manager server hosts
About this task
Use this task to add a secondary Element Manager server host.
Procedure
1. In the navigation pane of Element Manager Console, select Addresses.
2. In the Addresses window, click Add (+).
3. In the Add IPv4 Address dialog box, enter the logical name EMSvr2IntOAMAddr and IP
address of the secondary Element Manager server.
4. Click Apply.
5. Repeat the steps to add a service IP address for the secondary Web
conferencing server with the logical name WCS2SvcAddr.
6. Repeat the steps again to add a media IP address for the secondary media server with the
logical name MWCSrv2MediaAddr.
7. In the navigation pane of Element Manager Console, select Servers.
8. In the Servers window, click Add (+).
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
163
Adding redundancy to your solution
9. In the Add Server dialog box, complete the following fields:
• Short Name: EMS2
• Long Server Name: EMServer2
• Physical Site:
• Internal OAM (Default) Address: EMSvr2IntOAMAddr
• IPv4 Media Address: MWCSrv2MediaAddr
• Operating System: linux.
10. Click Apply .
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium non-redundant deployment to a medium redundant deployment on
page 158
Installing and configuring a secondary database instance
About this task
Use this task to install and configure a secondary database instance.
Procedure
1. 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 secondary
server.
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
164
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a large non-redundant deployment to a large redundant deployment
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium non-redundant deployment to a medium redundant deployment on
page 158
Expanding from a large non-redundant deployment to a
large redundant deployment
If you have a large Avaya Aura® Conferencing solution without any redundancy, you can add
redundancy by following the procedures in this section.
A deployment without redundancy is also called a simplex deployment.
These procedures are relevant for large-sized deployments.
Related Links
Reference configurations for large enterprises on page 165
Checklist for expanding a large non-redundant deployment to a redundant deployment on page 167
Reference configurations for large enterprises
There 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. Large
enterprises 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 to
a maximum of 150,000 users.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
165
Adding redundancy to your solution
Figure 7: Large Simplex Configuration
166
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a large non-redundant deployment to a large redundant deployment
Figure 8: Large Redundant Configuration
Related Links
Expanding from a large non-redundant deployment to a large redundant deployment on page 165
Checklist for expanding a large non-redundant deployment to a
redundant deployment
No.
Task
Description
1
Disable the Access
Control List (ACL) rules
on Avaya Aura®
Conferencing server if
they are used
Configuring the access
control list on page 99
2
Install the Avaya Aura®
Installing the platform on
Conferencing platform on page 49
the secondary Element
Manager server and on
the secondary Media and
August 2014
Notes
Migrating Avaya Aura® Conferencing
Comments? [email protected]
167
Adding redundancy to your solution
No.
Task
Description
Notes
Web Conferencing
server
3
Install Avaya Media
Installing Avaya Media
Server (MS) platform on Server on page 64
the secondary Media and
Web Conferencing
server
4
Add the secondary
Element Manager
server & secondary
Media and Web
Conferencing server
hosts
5
Stop all the network
Stopping a network
element instances except element instance on
the Element Manager
page 43
6
Add and deploy
secondary network
element instances on the
secondary Element
Manager server:
• Provisioning Manager
• Web Conferencing
Management Server
Adding secondary Element
Manager server and
secondary media and Web
conferencing server
hosts on page 162
For more information, see
Deploying Avaya Aura®
Conferencing and
Administering Avaya Aura®
Conferencing, which are
available from the Avaya
Support website:http://
www.avaya.com/support
• Document Conversion
Server
• Element Manager
• Accounting Manager
• Application Server
7
Add and deploy
secondary network
element instances on the
secondary Media and
Web conferencing
server:
For more information, see
Administering Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
• Web Conferencing
Server
• Media Server
8
168
Create and assign new
certificates to all new
network element
instances
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a large non-redundant deployment to a large redundant deployment
No.
Task
Description
Notes
Support website:http://
www.avaya.com/support
9
Add and configure new
Media Server to existing
Media Server cluster
For more information, see
Administering Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
10
Add and configure new
Web Conferencing
Server to existing Web
Conferencing Server
cluster
For more information, see
Administering Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
11
Stop an Element
Manager instance
Stopping an Element
Manager Instance on
page 44
12
Install and configure the
secondary database
instance
Installing and configuring a
secondary database
instance on page 164
13
Start all the network
element instances
Starting a network element
instance on page 156
Starting an Element
Manager instance from the
server console on
page 125
14
Configuring Web
Conferencing
Management Server
Rsync
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
15
Configure Audio/Video in
Collaboration Agent on
the Secondary Element
Manager Server
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
16
Configure ACL rules on
Avaya Aura®
Conferencing server to
reflect network topology
changes if they were
used
Configuring the access
control list on page 99
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
169
Adding redundancy to your solution
No.
Task
Description
17
Verify that the Avaya
Aura® Conferencing
system is operating
correctly
Verifying the system on
page 68
Notes
Related Links
Expanding from a large non-redundant deployment to a large redundant deployment on page 165
170
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Chapter 9: Upsizing your solution
Expanding from a medium to a large deployment (without
redundancy)
If you have an SMB or a medium Avaya Aura® Conferencing solution without any redundancy, you
can expand your system to a large solution 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.
Figure 9: Medium Simplex Configuration
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
171
Upsizing your solution
Figure 10: Large Simplex Configuration
Related Links
Checklist for expanding a medium simplex deployment to a large simplex deployment on page 173
Adding media and Web conferencing servers on page 174
Adding media and Web conferencing server hosts on page 174
Changing engineering parameters for a network element instance on page 175
Changing engineering parameters in the database on page 176
Moving an Avaya Media Server (MS) network element to a new server on page 177
Moving a Web conferencing Server network element to a new server on page 178
172
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium to a large deployment (without redundancy)
Checklist for expanding a medium simplex deployment to a large
simplex deployment
No.
Task
Description
1
Disable the Access
Control List (ACL) rules
on Avaya Aura®
Conferencing server if
they are used
Configuring the access
control list on page 99
2
Back up conferencing
recordings
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
3
Add the Media and Web
Conferencing servers
Adding media and Web
conferencing servers on
page 174
4
Change the engineering
parameters in the
database
Changing engineering
parameters in the
database on page 176
5
Change the engineering
parameters for all the
remaining network
element instances
Changing engineering
parameters for a network
element instance on
page 175
6
Restore conferencing
recordings
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
7
Configure ACL rules on
Avaya Aura®
Conferencing server to
reflect network topology
changes if they were
used
Configuring the access
control list on page 99
8
Verify that the Avaya
Aura® Conferencing
system is operating
correctly
Verifying the system on
page 68
Notes
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
173
Upsizing your solution
Adding media and Web conferencing servers
About this task
Use 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
Description
®
1
Install the Avaya Aura Conferencing platform
on the additional server.
Installing the platform on page 49
2
Install the Avaya Media Server (MS) platform
on the additional server.
Installing Avaya Media Server on page 64
3
Add the additional media and Web
conferencing server host.
Adding media and Web conferencing server
hosts on page 174
4
Move a Web conferencing server network
element to the new server.
Moving a Web conferencing Server network
element to a new server on page 178
5
Move an Avaya Media Server (MS) network
element to the new server.
Moving an Avaya media server network
element to a new server on page 177
6
Uninstall the Avaya Media Server (MS)
platform software from the Element Manager
server.
See Deploying Avaya Aura® Conferencing
8.0, which is available from https://
support.avaya.com/.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Adding media and Web conferencing server hosts
About this task
Use this task to add additional media and Web conferencing server hosts.
Procedure
1. In the navigation pane of Element Manager Console, select Addresses.
2. In the Addresses window, click Add (+).
3. In the Add IPv4 Address dialog box, enter the logical name and IP address for the server
on 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.
174
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium to a large deployment (without redundancy)
6. Repeat the steps again to add a media IP address for the media server.
7. In the navigation pane of Element Manager Console, select Servers.
8. In the Servers window, click Add (+).
9. In the Add Server dialog box, complete the following fields:
• 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 .
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Changing engineering parameters for a network element instance
About this task
Use this task to change the engineering parameters for a network element instance.
Procedure
1. Stop the network element instance.
For more information, see Stopping a network element instance on page 43.
2. Undeploy the network element instance.
For more information, see Undeploying a network element instance on page 154.
3. Change the engineering parameters for the network element instance:
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > > > Instances.
b. In the Instance dialog, select the network element instance.
c. Click Edit (-/+).
d. In the Edit Instance dialog , update the engineering parameters in the
Engineering list.
e. Click Apply.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
175
Upsizing your solution
4. Deploy and start the media server network element instance.
For more information, see Deploying a Network Element instance on page 82 and Starting a
network element instance on page 156.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Changing engineering parameters in the database
About this task
Use this task to update the engineering parameters in the database.
Procedure
1. 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.
2. At the prompt, type cd /var/mcp/install and press Enter.
3. At the prompt, type populateInstallpropsFile.pl and press Enter.
The list of available loads is displayed.
Avaya Aura® Conferencing 8.0 loads have the filename MCP_18.x.x.xx_2013-xx-xxxxxx.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 and
Element Manager:
––- Invoking mcpUpgrade => to upgrade the EM & Database –––
Note:
If the upgrade message is not displayed, stop and contact Avaya support.
176
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium to a large deployment (without redundancy)
Once the upgrade of the MCP database and Element Manager is complete, the following
message is displayed:
––- EM & DataBase Upgrade Complete –––
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Moving an Avaya Media Server (MS) network element to a new
server
About this task
Use this task to move an Avaya Media Server (MS) network element to a new server.
Procedure
1. Stop the Avaya Media Server (MS) network element instance.
For more information, see Stopping a network element instance on page 43.
2. Undeploy the Avaya Media Server (MS) network element instance.
For more information, see Undeploying a network element instance on page 154.
3. Change the server for the media server instance:
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Media Servers and Clusters > Media Servers > > Instances.
b. In the Instance dialog, select the media server
network element instance.
c. Click Edit (-/+).
d. In the Edit Instance dialog, select the new media
and Web conferencing server from the Server list.
e. In the Edit Instance dialog, update the engineering
parameters in the Engineering list.
f. Click Apply.
4. Change the certificate configured for the Avaya Media Server (MS) HTTPS Certificate in
accordance with the guidelines for certificate configuration.
For more information, see Guidelines for certificate configuration on page 114.
5. Deploy and start the Avaya Media Server (MS) network element.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
177
Upsizing your solution
For more information, see Deploying a Network Element instance on page 82 and Starting a
network element instance on page 156.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Moving a Web conferencing Server network element to a new
server
About this task
Use this task to move a Web conferencing server network element to a new server.
Procedure
1. Stop the Web Conferencing Servers (WCS) network element instance.
For more information, see Stopping a network element instance on page 43.
2. Undeploy the WCS network element instance.
For more information, see Undeploying a network element instance on page 154.
3. Change the server for the WCS instance:
a. In the navigation pane of the Element Manager Console, select Feature Server
Elements > Web Conferencing > Web Conferencing Servers and Clusters > Web
Conferencing Servers > > Instances.
b. In the Instance dialog, select the WCS
network element instance.
c. Click Edit (-/+).
d. In the Edit Instance dialog, select the new
media and Web conferencing server from the Server list.
e. In the Edit 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.
178
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium to a large deployment (with redundancy)
5. Change the certificate configured for the WCS HTTPS Certificate in accordance with the
guidelines for certificate configuration.
For more information, see Guidelines for certificate configuration on page 114.
6. Deploy and start the WCS network element.
For more information, see Deploying a Network Element instance on page 82 and Starting a
network element instance on page 156.
Additionally, see Deploying Avaya Aura® Conferencing 8.0, which is available on http://
support.avaya.com/.
Next steps
Refer back to your checklist for more information about your next task. You should always use your
checklist for guidance. You should print it out so that you can mark each task as you complete it.
Related Links
Expanding from a medium to a large deployment (without redundancy) on page 171
Expanding from a medium to a large deployment (with
redundancy)
If you have an SMB or a medium Avaya Aura® Conferencing solution with redundancy, you can
expand your system to a large solution by following the procedures in this section.
These procedures are relevant for SMB or medium-sized deployments.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
179
Upsizing your solution
Figure 11: Medium Redundant Configuration
Figure 12: Large Redundant Configuration
180
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Expanding from a medium to a large deployment (with redundancy)
Related Links
Checklist for expanding a medium redundant deployment to a large redundant deployment on
page 181
Checklist for expanding a medium redundant deployment to a
large redundant deployment
No.
Task
Description
1
Disable the Access
Control List (ACL) rules
on Avaya Aura®
Conferencing server if
they are used
Configuring the access
control list on page 99
2
Back up conferencing
recordings
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
3
Add primary Media and
Web Conferencing
servers
Adding media and Web
conferencing servers on
page 174
4
Add secondary Media
and Web Conferencing
servers
Adding media and Web
conferencing servers on
page 174
5
Change the engineering
parameters in the
database
Changing engineering
parameters in the
database on page 176
6
Change the engineering
parameters for all the
remaining network
element instances
Changing engineering
parameters for a network
element instance on
page 175
7
Restore conferencing
recordings
For more information, see
Deploying Avaya Aura®
Conferencing, which is
available from the Avaya
Support website:http://
www.avaya.com/support
8
Configure ACL rules on
Avaya Aura®
Conferencing server to
reflect network topology
changes if they were
used
Configuring the access
control list on page 99
August 2014
Notes
Migrating Avaya Aura® Conferencing
Comments? [email protected]
181
Upsizing your solution
No.
Task
Description
9
Verify that the Avaya
Aura® Conferencing
system is operating
correctly
Verifying the system on
page 68
Notes
Related Links
Expanding from a medium to a large deployment (with redundancy) on page 179
182
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Appendix A: Overview of automatic
disaster recovery
Avaya Aura® Conferencing supports automatic disaster recovery (ADR). Typically, ADR means
having a second, replica system to which you can switch operations in the event of a failure on the
primary, main system. Typically, the secondary system is geographically separated from the primary
system. 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 primary
system, 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 data
synchronization. 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 the
primary site when it is repaired.
To ensure a smooth, automatic transition to the secondary site, you must perform some
configuration tasks on Avaya Aura® Session Manager and the Avaya Media Server (MS) resources
in advance. In addition, you must add the secondary site URL addresses to the users’ Domain
Name 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 for
normal service to resume. However, if you intend to switch to the secondary system for a prolonged
period of time, you must manually configure the details of the secondary servers on the System
Manager interface.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
183
Overview of automatic disaster recovery
Example layouts
Figure 13: An example of an installation of ADR
184
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Implications of virtualization for automatic disaster recovery
Figure 14: An example of ADR under normal operations
Related Links
Implications of virtualization for automatic disaster recovery on page 185
System service state on page 186
Implications of virtualization for automatic disaster
recovery
If you are using virtualization (VMWare) to deploy Avaya Aura® Conferencing, there are implications
for automatic disaster recovery (ADR). ADR deployments on VMWare need to use platform OVAs
for all deployment models.
Related Links
Overview of automatic disaster recovery on page 183
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
185
Overview of automatic disaster recovery
System service state
The concept of a system service state is a key concept to automatic disaster recovery (ADR). There
are 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 a
conferencing service. When Avaya Aura® Conferencing is locked, it is not operational and is not
providing a conferencing service.
Related Links
Overview of automatic disaster recovery on page 183
186
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Appendix B: Fixing remote host SSH keys
About this task
When 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 primary
reason), then SSH will not allow a connection to continue until that key is manually removed from
the 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 will
succeed:
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IT IS POSSIBLE THAT
SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you
right now (man-in-the-middle attack)! It is also possible that the RSA
host key has just been changed. The fingerprint for the RSA key sent by
the 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 is
being run.
Procedure
1. 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.
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
187
Index
A
AAC-hosted licensing
install ............................................................................ 67
ACL ....................................................................................108
configuring .................................................................... 99
ACL rules ............................................. 99–101, 103, 105, 108
adding new servers ............................................................163
adding redundancy ............................................................ 158
additional server hosts .......................................................174
additional servers ...............................................................174
administration
related documentation .................................................. 10
ADR
overview ..................................................................... 183
state ............................................................................186
VMWare ......................................................................185
allow bandwidth management ........................................... 135
Apple Safari ......................................................................... 18
application bundle ................................................................61
automatic disaster recovery
overview ..................................................................... 183
state ............................................................................186
AViCA ............................................................................ 36, 80
B
backing up
conference recordings .................................................. 37
database .................................................................39, 79
flash media gateways ............................................. 36, 80
FMG ........................................................................36, 80
media server .................................................................36
servers ..........................................................................40
bandwidth management ...................................................... 98
BIOS
modifying clock ............................................................. 52
D
database .................................................................. 39, 63, 79
replication ............................................................... 71, 91
single ...................................................................... 90, 91
database software ............................................................... 62
DCS
certificates .................................................................. 125
disaster recovery ............................................................... 183
state ............................................................................186
DMZ ................................................................... 138, 140, 146
E
Element Manager ................................................................ 44
End Entity .......................................................................... 133
engineering parameters .............................................175, 176
enrollment password ..........................................................116
enterprise solution ............................................................. 145
extracting ............................................................................. 61
F
Firefox ..................................................................................18
Fixing remote host SSH keys ............................................ 187
Flash Media Gateway
configuring a secure SIP TLS connection to Session
Manager ..................................................................... 134
flash media gateways .................................................... 36, 80
FMG ...............................................................................36, 80
restoring ........................................................................68
G
C
certificate configuration ......................................................114
certificates ..................................................................124, 125
application server ....................................................... 121
Avaya Media Server ................................................... 122
Collaboration Agent Manager .....................................120
Element Manager ....................................................... 118
network elements ....................................................... 116
Provisioning Manager .................................................119
WCS ........................................................................... 123
checklist
adding redundancy ............................................. 160, 167
Chrome ................................................................................ 18
cleaning up .......................................................................... 41
188
Collaboration Agent Manager ............................................ 147
components ......................................................................... 30
conference recordings ......................................................... 37
configurations ............................................................ 158, 165
Google Chrome ................................................................... 18
growing your system ..................................................171, 179
H
hardware environment ......................................................... 52
HP Proliant DL360 G8 ......................................................... 19
I
identity certificate
Flash Media Gateway .................................................133
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014
Index
implementation
related documentation .................................................... 9
import.dat ...........................................................................113
installing
database .......................................................................63
Element Manager ......................................................... 64
installing WebLM ................................................................. 67
intelligent workbook ....................................................... 15, 49
Internet Explorer .................................................................. 18
K
killing
network element ........................................................... 81
related documentation
administration ............................................................... 10
implementation ............................................................... 9
overview ......................................................................... 9
supporting .....................................................................10
related resources
training ..........................................................................11
remote backup parameters ..................................................42
replication errors .................................................................. 71
restoring ...............................................................................60
restoring server ....................................................................59
resync ................................................................................ 154
re-syncing the database ...................................................... 70
S
L
online help ........................................................................... 12
overview .................................................................................8
related documentation .................................................... 9
Safari ................................................................................... 18
secondary database instance ............................................ 164
secondary EM ....................................................................163
secondary media servers ...................................................162
server migration ................................................................... 30
server replacement .............................................................. 63
introduction ................................................................... 21
redundant ..................................................................... 26
requirements .................................................................21
simplex ......................................................................... 22
servers ................................................................................. 40
Session Manager .................................................................97
simplex
Element Manager ......................................................... 22
non-Element Manager .................................................. 24
single sign-on .....................................................................129
SSH keys ............................................................................. 38
starting
network element ......................................................... 156
support .................................................................................14
supporting
related documentation .................................................. 10
syslog server
configuration ................................................................. 58
system configuration
configuration ................................................................. 53
system default settings ...................................................... 135
System Manager ..................................................................96
P
T
platform ................................................................................45
PostgreSQL ......................................................................... 42
testing .................................................................................. 68
TLS
configuring for the Flash Media Gateway ................... 134
guidelines ................................................................... 114
tools package .......................................................................80
training
related resources ..........................................................11
turnkey ................................................................................. 93
Linux
installing ........................................................................49
M
MAC OS ...............................................................................18
media server .......................................................... 36, 64, 102
medium to large ......................................................... 173, 181
move media server ............................................................ 177
moving web conferencing server ....................................... 178
Mozilla Firefox ......................................................................18
N
network element instance ...................................... 43, 65, 154
deploying .............................................................. 82, 155
Network Element instance
starting ..........................................................................83
NTP clock
configuration ................................................................. 56
O
R
recordings ............................................................................ 67
redundant
Element Manager ......................................................... 26
non-primary Element Manager ..................................... 28
August 2014
Migrating Avaya Aura® Conferencing
Comments? [email protected]
189
Index
U
unneeded files ..................................................................... 41
unneeded installers ..............................................................42
USB restore ......................................................................... 47
user password owned locally .............................................135
V
verification ............................................................................68
videos .................................................................................. 11
virtualization
ADR ............................................................................ 185
VMware ................................................................................73
W
WCMS ............................................................................... 151
resync ......................................................................... 154
WCS .................................................................................. 142
web browser ........................................................................ 18
web conferencing
modifying the meeting event processor for a
management server ....................................................156
Web Conferencing Server ................................................. 149
WebLM ................................................................................ 98
install ............................................................................ 67
Windows 7.0 ........................................................................ 18
Windows XP ........................................................................ 18
190
Migrating Avaya Aura® Conferencing
Comments? [email protected]
August 2014