Avaya Aura System Manager Overview and Specification Release 81x Issue8 Feb08 2021
Avaya Aura System Manager Overview and Specification Release 81x Issue8 Feb08 2021
and Specification
Release 8.1.x
Issue 8
February 2021
© 2015-2021, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU
All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR
AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
Notice SERVICE.
While reasonable efforts have been made to ensure that the Licenses
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO,
document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya
of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY
AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS,
Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED
“Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL
performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER.
of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING,
Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE
deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA
such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA
the express behalf of Avaya. End User agrees to indemnify and hold RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU
harmless Avaya, Avaya's agents, servants and employees against all AND ANYONE ELSE USING OR SELLING THE SOFTWARE
claims, lawsuits, demands and judgments arising out of, or in WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR
connection with, subsequent modifications, additions or deletions to USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO,
this documentation, to the extent made by End User. YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Link disclaimer SOFTWARE (HEREINAFTER REFERRED TO
Avaya is not responsible for the contents or reliability of any linked INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
websites referenced within this site or Documentation provided by THESE TERMS AND CONDITIONS AND CREATE A BINDING
Avaya. Avaya is not responsible for the accuracy of any information, CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
statement or content provided on these sites and does not APPLICABLE AVAYA AFFILIATE (“AVAYA”).
necessarily endorse the products, services, or information described Avaya grants You a license within the scope of the license types
or offered within them. Avaya does not guarantee that these links will described below, with the exception of Heritage Nortel Software, for
work all the time and has no control over the availability of the linked which the scope of the license is detailed below. Where the order
pages. documentation does not expressly identify a license type, the
Warranty applicable license will be a Designated System License as set forth
below in the Designated System(s) License (DS) section as
Avaya provides a limited warranty on Avaya hardware and software. applicable. The applicable number of licenses and units of capacity
Refer to your sales agreement to establish the terms of the limited for which the license is granted will be one (1), unless a different
warranty. In addition, Avaya’s standard warranty language, as well as number of licenses or units of capacity is specified in the
information regarding support for this product while under warranty is documentation or other materials available to You. “Software” means
available to Avaya customers and other parties through the Avaya computer programs in object code, provided by Avaya or an Avaya
Support website: https://support.avaya.com/helpcenter/ Channel Partner, whether as stand-alone products, pre-installed on
getGenericDetails?detailId=C20091120112456651010 under the link hardware products, and any upgrades, updates, patches, bug fixes,
“Warranty & Product Lifecycle” or such successor site as designated or modified versions thereto. “Designated Processor” means a single
by Avaya. Please note that if You acquired the product(s) from an stand-alone computing device. “Server” means a set of Designated
authorized Avaya Channel Partner outside of the United States and Processors that hosts (physically or virtually) a software application
Canada, the warranty is provided to You by said Avaya Channel to be accessed by multiple users. “Instance” means a single copy of
Partner and not by Avaya. the Software executing at a particular time: (i) on one physical
“Hosted Service” means an Avaya hosted service subscription that machine; or (ii) on one deployed software virtual machine (“VM”) or
You acquire from either Avaya or an authorized Avaya Channel similar deployment.
Partner (as applicable) and which is described further in Hosted SAS License types
or other service description documentation regarding the applicable
hosted service. If You purchase a Hosted Service subscription, the Designated System(s) License (DS). End User may install and use
foregoing limited warranty may not apply but You may be entitled to each copy or an Instance of the Software only: 1) on a number of
support services in connection with the Hosted Service as described Designated Processors up to the number indicated in the order; or 2)
further in your service description documents for the applicable up to the number of Instances of the Software as indicated in the
Hosted Service. Contact Avaya or Avaya Channel Partner (as order, Documentation, or as authorized by Avaya in writing. Avaya
applicable) for more information. may require the Designated Processor(s) to be identified in the order
by type, serial number, feature key, Instance, location or other
Hosted Service specific designation, or to be provided by End User to Avaya through
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN AVAYA electronic means established by Avaya specifically for this purpose.
HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA Heritage Nortel Software
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA “Heritage Nortel Software” means the software that was acquired by
WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO UNDER Avaya as part of its purchase of the Nortel Enterprise Solutions
THE LINK “Avaya Terms of Use for Hosted Services” OR SUCH Business in December 2009. The Heritage Nortel Software is the
SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND ARE software contained within the list of Heritage Nortel Products located
APPLICABLE TO ANYONE WHO ACCESSES OR USES THE at https://support.avaya.com/LicenseInfo under the link “Heritage
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED Nortel Products” or such successor site as designated by Avaya. For
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON Heritage Nortel Software, Avaya grants Customer a license to use
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE Heritage Nortel Software provided hereunder solely to the extent of
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY the authorized activation or authorized usage level, solely for the
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. IF purpose specified in the Documentation, and solely as embedded in,
YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A for execution on, or for communication with Avaya equipment.
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT Charges for Heritage Nortel Software may be based on extent of
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE activation or use authorized as specified in an order or invoice.
TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF
Copyright PARTNER ACKNOWLEDGES AND AGREES THE AVAYA
CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND ALL
Except where expressly stated otherwise, no use should be made of RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC) CODEC
materials on this site, the Documentation, Software, Hosted Service, IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE
or hardware provided by Avaya. All content on this site, the FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES
documentation, Hosted Service, and the product provided by Avaya IN WHICH IT DOES NOT RECEIVE REMUNERATION TO: (I)
including the selection, arrangement and design of the content is ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD
owned either by Avaya or its licensors and is protected by copyright (“AVC VIDEO”) AND/OR (II) DECODE AVC VIDEO THAT WAS
and other intellectual property laws including the sui generis rights ENCODED BY A CONSUMER ENGAGED IN A PERSONAL
relating to the protection of databases. You may not modify, copy, ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER
reproduce, republish, upload, post, transmit or distribute in any way LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
any content, in whole or in part, including any code and software OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
unless expressly authorized by Avaya. Unauthorized reproduction, INFORMATION FOR H.264 (AVC) AND H.265 (HEVC) CODECS
transmission, dissemination, storage, and or use without the express MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
written consent of Avaya can be a criminal, as well as a civil offense
WWW.MPEGLA.COM.
under the applicable law.
Compliance with Laws
Virtualization
You acknowledge and agree that it is Your responsibility for
The following applies if the product is deployed on a virtual machine.
complying with any applicable laws and regulations, including, but not
Each product has its own ordering code and license types. Unless
limited to laws and regulations related to call recording, data privacy,
otherwise stated, each Instance of a product must be separately
intellectual property, trade secret, fraud, and music performance
licensed and ordered. For example, if the end user customer or
rights, in the country or territory where the Avaya product is used.
Avaya Channel Partner would like to install two Instances of the
same type of products, then two products of that type must be Preventing Toll Fraud
ordered.
“Toll Fraud” is the unauthorized use of your telecommunications
Third Party Components system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
“Third Party Components” mean certain software programs or
company's behalf). Be aware that there can be a risk of Toll Fraud
portions thereof included in the Software or Hosted Service may
associated with your system and that, if Toll Fraud occurs, it can
contain software (including open source software) distributed under
result in substantial additional charges for your telecommunications
third party agreements (“Third Party Components”), which contain
services.
terms regarding the rights to use certain portions of the Software
(“Third Party Terms”). As required, information regarding distributed Avaya Toll Fraud intervention
Linux OS source code (for those products that have distributed Linux
OS source code) and identifying the copyright holders of the Third If You suspect that You are being victimized by Toll Fraud and You
Party Components and the Third Party Terms that apply is available need technical assistance or support, call Technical Service Center
in the products, Documentation or on Avaya’s website at: https:// Toll Fraud Intervention Hotline at +1-800-643-2353 for the United
support.avaya.com/Copyright or such successor site as designated States and Canada. For additional support telephone numbers, see
by Avaya. The open source software license terms provided as Third the Avaya Support website: https://support.avaya.com or such
successor site as designated by Avaya.
Party Terms are consistent with the license rights granted in these
Software License Terms, and may contain additional rights benefiting Security Vulnerabilities
You, such as modification and distribution of the open source
software. The Third Party Terms shall take precedence over these Information about Avaya’s security support policies can be found in
Software License Terms, solely with respect to the applicable Third the Security Policies and Support section of https://
Party Components to the extent that these Software License Terms support.avaya.com/security.
impose greater restrictions on You than the applicable Third Party Suspected Avaya product security vulnerabilities are handled per the
Terms. Avaya Product Security Support Flow (https://
The following applies only if the H.264 (AVC) codec is distributed with support.avaya.com/css/P8/documents/100161515).
the product. THIS PRODUCT IS LICENSED UNDER THE AVC Downloading Documentation
PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE For the most current versions of Documentation, see the Avaya
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH Support website: https://support.avaya.com, or such successor site
THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC as designated by Avaya.
VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A Contact Avaya Support
PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS See the Avaya Support website: https://support.avaya.com for
GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. product or Hosted Service notices and articles, or to report a problem
ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, with your Avaya product or Hosted Service. For a list of support
L.L.C. SEE HTTP://WWW.MPEGLA.COM. telephone numbers and contact addresses, go to the Avaya Support
website: https://support.avaya.com (or such successor site as
Service Provider designated by Avaya), scroll to the bottom of the page, and select
THE FOLLOWING APPLIES TO AVAYA CHANNEL PARTNER’S Contact Avaya Support.
HOSTING OF AVAYA PRODUCTS OR SERVICES. THE PRODUCT Trademarks
OR HOSTED SERVICE MAY USE THIRD PARTY COMPONENTS
SUBJECT TO THIRD PARTY TERMS AND REQUIRE A SERVICE The trademarks, logos and service marks (“Marks”) displayed in this
PROVIDER TO BE INDEPENDENTLY LICENSED DIRECTLY FROM site, the Documentation, Hosted Service(s), and product(s) provided
THE THIRD PARTY SUPPLIER. AN AVAYA CHANNEL PARTNER’S by Avaya are the registered or unregistered Marks of Avaya, its
HOSTING OF AVAYA PRODUCTS MUST BE AUTHORIZED IN affiliates, its licensors, its suppliers, or other third parties. Users are
WRITING BY AVAYA AND IF THOSE HOSTED PRODUCTS USE not permitted to use such Marks without prior written consent from
OR EMBED CERTAIN THIRD PARTY SOFTWARE, INCLUDING Avaya or such third party which may own the Mark. Nothing
BUT NOT LIMITED TO MICROSOFT SOFTWARE OR CODECS, contained in this site, the Documentation, Hosted Service(s) and
THE AVAYA CHANNEL PARTNER IS REQUIRED TO product(s) should be construed as granting, by implication, estoppel,
INDEPENDENTLY OBTAIN ANY APPLICABLE LICENSE or otherwise, any license or right in and to the Marks without the
AGREEMENTS, AT THE AVAYA CHANNEL PARTNER’S EXPENSE, express written permission of Avaya or the applicable third party.
DIRECTLY FROM THE APPLICABLE THIRD PARTY SUPPLIER. Avaya is a registered trademark of Avaya Inc.
WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
PARTNER IS HOSTING ANY PRODUCTS THAT USE OR EMBED
THE H.264 CODEC OR H.265 CODEC, THE AVAYA CHANNEL
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Contents
Chapter 1: Introduction............................................................................................................ 7
Purpose.................................................................................................................................. 7
Change history........................................................................................................................ 7
Chapter 2: System Manager overview.................................................................................... 9
New in this release.................................................................................................................. 9
New in System Manager Release 8.1.3.1............................................................................ 9
New in System Manager Release 8.1.3............................................................................. 10
New in System Manager Release 8.1.2............................................................................. 12
New in System Manager Release 8.1.1............................................................................. 12
New in System Manager Release 8.1............................................................................... 13
Feature description................................................................................................................ 16
Overview........................................................................................................................ 16
Common console............................................................................................................ 17
Solution Deployment Manager.......................................................................................... 17
®
Automated upgrades and migrations of Avaya Aura applications....................................... 23
Supported servers........................................................................................................... 24
Dual stack support........................................................................................................... 24
Out of Band Management in System Manager................................................................... 25
Geographic Redundancy................................................................................................. 26
Data Replication Service.................................................................................................. 27
Management of users, public contacts, and shared address............................................... 28
Fault management.......................................................................................................... 28
Logging service............................................................................................................... 29
Log Harvester................................................................................................................. 29
Audit Logging.................................................................................................................. 29
Scheduler....................................................................................................................... 30
Bulk import and export..................................................................................................... 30
Bulk import and export using the Excel file......................................................................... 31
Multi Tenancy.................................................................................................................. 32
User provisioning rule...................................................................................................... 33
Supported footprints of System Manager........................................................................... 33
Configuration management.............................................................................................. 35
Security features............................................................................................................. 35
Enhanced Access Security Gateway (EASG) overview....................................................... 36
Element management...................................................................................................... 36
Group management......................................................................................................... 36
License management...................................................................................................... 37
System Manager Communication Manager capabilities overview........................................ 37
Granular role-based access control................................................................................... 38
Communication Manager feature concurrency enhancements............................................ 39
Certification validation...................................................................................................... 40
Bulk import and export enhancements.............................................................................. 41
®
Avaya Aura Device Services element.............................................................................. 41
Virtual machine report...................................................................................................... 42
Security hardening options............................................................................................... 42
Third-party certificate support........................................................................................... 42
Extended Hostname Validation......................................................................................... 43
Customer root account .................................................................................................... 43
Preserve security hardening modes on upgrade................................................................ 43
Chapter 3: Avaya Aura® overview......................................................................................... 44
®
Avaya Aura applications deployment offers............................................................................ 44
®
Avaya Aura Virtualized Appliance overview...................................................................... 44
Virtualized Environment overview..................................................................................... 46
Overview of Infrastructure as a Service environment.......................................................... 49
Software-only environment overview................................................................................. 52
Chapter 4: Interoperability..................................................................................................... 54
Product compatibility.............................................................................................................. 54
Chapter 5: Licensing requirements....................................................................................... 55
Chapter 6: Performance specifications................................................................................ 56
Capability and scalability specification..................................................................................... 56
Geographic Redundancy....................................................................................................... 57
Chapter 7: Security................................................................................................................. 58
Security specification............................................................................................................. 58
Trust Management.......................................................................................................... 58
External authentication.......................................................................................................... 59
SAML authentication........................................................................................................ 59
Role Based Access Control.................................................................................................... 59
Chapter 8: Resources............................................................................................................. 61
System Manager documentation............................................................................................ 61
Finding documents on the Avaya Support website............................................................. 62
Accessing the port matrix document.................................................................................. 62
Avaya Documentation Center navigation........................................................................... 63
Training................................................................................................................................ 64
Viewing Avaya Mentor videos................................................................................................. 64
Support................................................................................................................................ 65
Using the Avaya InSite Knowledge Base........................................................................... 65
Glossary................................................................................................................................... 67
Purpose
This document describes tested characteristics and capabilities of Avaya Aura® System Manager,
including feature descriptions, interoperability, performance specifications, security, and licensing
requirements.
This document is intended for anyone who wants to gain a high-level understanding of System
Manager features, functions, capacities, and limitations within the context of solutions and verified
reference configurations.
Change history
The following changes have been made to this document since the last issue:
Avaya Aura® System Manager is a central management system that provides a set of shared
management services and a common console. All shared and element-specific management for
Avaya Aura® applications that System Manager supports is performed from the common console.
System Manager provides the following key capabilities:
• Centralized software management solution to support deployments, migrations, upgrades, and
updates to the suite of Avaya Aura® applications.
• Avoid duplicate data entry through shared management services.
• Centralized access to all Avaya Aura® applications through a browser-based management
console with single sign on.
• Optimization of IT skill sets with consistency of management functions across Avaya solutions.
• Integration with enterprise IT infrastructure, such as identity management, authentication,
authorization, security, and enterprise directory
The emergency Dial Pattern routes notification message is now displayed in the Notifications
widget on the System Manager dashboard.
Enhancements to the Notifications widget
From Release 8.1.3.1, the Notifications widget on the System Manager dashboard also displays
the user login information and emergency Dial Pattern routes notification message for Emergency
Location Management Solution.
From System Manager Release 8.1.3.1 and later, you cannot close the Notifications widget.
• You can add, list, view, and delete subject names for the provided entity class using the
manageEntityClassWhitelist command. You can add and delete bulk entries of subject
names for an entity class. You can also check the status of the subject name validation for
the entity class.
• You can use the Number of days after which system deletes expired certificates field on
the Services > Configurations > Settings > SMGR > Trust Management page to set the
number of days to delete the expired certificates from the system.
Support for outbound connection logging
With Release 8.1.3, you can log all outgoing connections from System Manager, using the
outboundConnectionLogging utility.
Support for configuring the outbound firewall rule
With Release 8.1.3, you can configure System Manager outbound firewall rule by using the
configureOutboundFirewall utility. You can add, list, view status, disable, remove, and
overwrite the IP addresses and FQDN in the whitelist for establishing the outbound connection
from System Manager.
Support of new CLI command for managing the password policies
With Release 8.1.3, System Manager supports the setSecurityPolicy command for
managing password policies using the command line interface (CLI). This command is only
applicable for changing or setting up the password for a CLI user or a root user that you create at
the time of deployment.
Enhancement to password policies
With Release 8.1.3, the Communication Profile Password Policy and the Password strength policy
are enhanced with the following:
• Minimum total length supports the default value of 14 characters as the minimum number
of characters that you must use in a password.
• Previous passwords blocked supports the default value of 10 for the number of latest
passwords that the system maintains in its history.
• Supports the addition of the new Maximum repeated consecutive characters field.
• Supports the addition of the new Maximum consecutive characters from same character
type field.
Support for VMware ESXi 7.0
With Release 8.1.3, Avaya Aura® applications support the VMware® vSphere ESXi 7.0 and
VMware® vCenter Server 7.0 in the VMware virtualized environment.
System Manager Welcome message
From System Manager Release 8.1.3, after your first successful login, when you log in to the
System Manager web console or the System Manager command line interface again, System
Manager displays the Welcome <SystemManager_UserName> pop-up window at your each
subsequent login.
Enhancements to the System Manager alert messages at login
With Release 8.1.3, for the Emergency Location Management Solution, System Manager displays
the Session Manager emergency Dial Pattern routes notification warning message in an Alert
Messages pop-up window, if the Routing Locations, Routing Policies, and Dial Patterns are not
configured on Session Manager according to the emergency calling guideline.
Centralized subscription licensing
With Release 8.1.3, WebLM supports the Centralized subscription licensing feature for solution
licenses.
Enhancement to the number of IP Office branches support
With Release 8.1.3, System Manager supports up to:
• 2000 IP Office branches with System Manager Profile 3.
• 3500 IP Office branches with System Manager Profile 4.
Feature description
Overview
The following sections provide a brief description of the functionality of the feature that System
Manager provides in support for various Avaya products. For detailed information on the services
available for a specific Avaya product, see the interoperability table in the System Manager 8.x
Product Offer Definition on the Avaya Support website at http://support.avaya.com.
Common console
The common console is a common management interface for managing various applications in
System Manager. It is a framework for the aggregation of management presentation views and
supports dynamic extendibility and contraction as you add or remove management applications.
You can use the web management console in a variety of scenarios ranging from product-specific
management to suite management. The different scenarios can leverage the common look-and-
feel and common components.
Note:
When an application is configured with Out of Band Management, Solution Deployment
Manager does not support upgrade for that application.
For information about upgrading the application, see the application-specific upgrade
document on the Avaya Support website.
• Download Avaya Aura® applications.
• Install service packs, feature packs, and software patches for the following Avaya Aura®
applications:
- Communication Manager and associated devices, such as gateways, media modules, and
TN boards.
- Session Manager
- Branch Session Manager
- AVP Utilities
- Avaya Aura® Appliance Virtualization Platform, the ESXi host that is running on the Avaya
Aura® Virtualized Appliance.
The upgrade process from Solution Deployment Manager involves the following key tasks:
• Discover the Avaya Aura® applications.
• Refresh applications and associated devices and download the necessary software
components.
• Run the preupgrade check to ensure successful upgrade environment.
• Upgrade Avaya Aura® applications.
• Install software patch, service pack, or feature pack on Avaya Aura® applications.
For more information about the setup of the Solution Deployment Manager functionality that is part
of System Manager 8.1.x, see Avaya Aura® System Manager Solution Deployment Manager Job-
Aid.
• You must use Solution Deployment Manager Client 7.1 and later to create the kickstart
file for initial Appliance Virtualization Platform installation or recovery.
Note:
- System Manager must be on the same or higher release than the application you are
upgrading to. For example, you must upgrade System Manager to 7.1.3.2 before you
upgrade Communication Manager to 7.1.3.2.
All the applications that are supported by System Manager do not follow the general
Avaya Aura® Release numbering schema. Therefore, for the version of applications
that are supported by System Manager, see Avaya Aura® Release Notes on the Avaya
Support website.
- Solution Deployment Manager Client must be on the same or higher release than the
OVA you are deploying. For example, if you are deploying Communication Manager
7.1.3 OVA, Solution Deployment Manager Client version must be on Release 7.1.3,
7.1.3.1, 7.1.3.2, or 8.0. Solution Deployment Manager Client cannot be on Release
7.1.
• Configures application and networking parameters required for application deployments.
• Supports selecting the application OVA file from a local path or an HTTPS URL. You do not
need access to PLDS.
• Supports changing the hypervisor network parameters, such as IP Address, Netmask,
Gateway, DNS, and NTP on Appliance Virtualization Platform.
• Supports installing patches for the hypervisor on Appliance Virtualization Platform.
• Supports installing software patches, service packs, and feature packs only for System
Manager.
Note:
To install the patch on System Manager, Solution Deployment Manager Client must be
on the same or higher release as the patch. For example, if you are deploying the patch
for System Manager Release 7.1.1, you must use Solution Deployment Manager Client
Release 7.1.1 or higher.
However, to install the patch on System Manager Release 7.0.x, Solution Deployment
Manager Client must be on Release 7.0.x.
Avaya Aura® applications use centralized Solution Deployment Manager from System
Manager to install software patches, service packs, and feature packs. For the applications
that cannot be patched from centralized Solution Deployment Manager, use the application
Command Line Interface or web console.
For more information about supported releases and patching information, see Avaya Aura®
Release Notes on the Avaya Support website.
• Configures Remote Syslog Profile.
• Creates the Appliance Virtualization Platform Kickstart file.
With Solution Deployment Manager, you can deploy the following applications:
• AVP Utilities 8.1.3
• System Manager 8.1.3
• Session Manager 8.1.3
• Branch Session Manager 8.1.3
• Communication Manager 8.1.3
• Application Enablement Services 8.1.3
• WebLM 8.1.3
• Communication Manager Messaging 7.0
For information about other Avaya product compatibility information, go to https://
support.avaya.com/CompatibilityMatrix/Index.aspx.
With Solution Deployment Manager, you can migrate, upgrade, and update the following
applications:
• Hardware-based Session Manager 6.x
• System Platform-based Communication Manager
- Duplex CM Main / Survivable Core with Communication Manager
- Simplex CM Main / Survivable Core with Communication Manager, Communication
Manager Messaging, and Utility Services
- Simplex Survivable Remote with Communication Manager, Branch Session Manager, and
Utility Services
- Embedded CM Main with Communication Manager, Communication Manager Messaging,
and Utility Services
- Embedded Survivable Remote with Communication Manager, Branch Session Manager,
and Utility Services
• System Platform-based Branch Session Manager
- Simplex Survivable Remote with Communication Manager, Branch Session Manager, and
Utility Services
- Embedded Survivable Remote with Communication Manager, Branch Session Manager,
and Utility Services
Note:
You must manually migrate the Services virtual machine that is part of the template.
The centralized deployment and upgrade process provides better support to customers who want
to upgrade their systems to Avaya Aura® Release 8.1.3. The process reduces the upgrade time
and error rate.
Solution Deployment Manager dashboard
You can gain access to the Solution Deployment Manager dashboard from the System Manager
web console or by installing the Solution Deployment Manager client.
Supported servers
The following servers are supported for deployments and upgrades to Release 8.1 and later:
• Dell™ PowerEdge™ R620
• HP ProLiant DL360p G8
• Dell™ PowerEdge™ R630
• HP ProLiant DL360 G9
• S8300E, for Communication Manager and Branch Session Manager
• Avaya Solutions Platform 120 Appliance: Dell PowerEdge R640
• Avaya Solutions Platform 130 Appliance: Dell PowerEdge R640
Note:
- Avaya Aura® Release 8.0 and later does not support S8300D, Dell™ PowerEdge™
R610, and HP ProLiant DL360 G7 servers.
- Avaya Aura® Release 7.0 and later does not support S8510 and S8800 servers.
For fresh installations, use Avaya Solutions Platform 120 Appliance or Avaya Solutions Platform
130 Appliance: Dell PowerEdge R640.
both IPv4 and IPv6, System Manager supports only IPv4 addresses until explicitly configured to
support IPv6 addresses.
IPv6 Support
System Manager Release 7.1 and later support IPv6 addresses with dual stack capabilities. The
System Manager administrator can configure IPv6 addresses for features such as Geographic
Redundancy, Certificates with IPv6 address, System Upgrade, and Discovery of network
elements.
Note:
Once OOBM is enabled on System Manager, public interface eth1 is no longer reachable
using ping command from other systems that are present in a public network. However,
System Manager can reach other systems on a public interface.
Out of Band Management in a Geographic Redundancy setup
When you configure Geographic Redundancy, provide Management network details only.
Validation fails if you configure Geographic Redundancy with Public network details. In
Geographic Redundancy setup, you do not disable or enable Out of Band Management on both
primary and secondary System Manager virtual machine. You can enable Out of Band
Management on the primary System Manager virtual machine and disable Out of Band
Management on the secondary System Manager virtual machine, and vice versa.
Restoring System Manager backup
While restoring backup on System Manager with different Out of Band Management network
details, the restore operation fails at validation phase.
Tenant Management on Out of Band Management-enabled System Manager
By default, the Multi Tenancy feature is disabled on System Manager when Out of Band
Management is enabled. You must enable Multi Tenancy on Out of Band Management-enabled
System Manager for the Tenant Management administrator to manage tenant users.
Geographic Redundancy
The System Manager Geographic Redundancy service replicates the Avaya Aura® element
support for two geographically distant System Manager sites with separate subnetworks and
across a WAN so that the System Manager management services can change from one site to
another when one of the sites or servers fails. The System Manager Geographic Redundancy
sites are set up in pairs with each site in a System Manager standalone or System Manager HA
configuration. You can designate one server from the pair as the primary System Manager server
and the other as the secondary System Manager server.
In normal operation also called sunny-day scenario, the primary System Manager provides all
element administration and automatically replicates the administrative changes made on the
primary System Manager server to the secondary System Manager server on a batch transaction
basis. The secondary System Manager functions in the warm standby mode or the read-only
mode and provides a subset of System Manager services, such as the System Manager
Geographic Redundancy status or statistics, Inventory, and Authentication and Authorization.
In the event of catastrophic failure or split network, also called rainy-day scenario, you can activate
the System Manager server that you designated as secondary to assume full management of all
supported Avaya Aura® elements. The elements that support the Active-Standby mode include
Avaya Aura® Session Manager and Avaya Aura® Communication Manager. Geographic
Redundancy-unaware elements might require manual intervention to gain services from the
secondary System Manager server that is active.
The primary and the secondary System Manager servers can be in active mode in the split
network scenarios.
After deactivation of the secondary System Manager server, the system administrator selects the
database of the primary or the secondary System Manager server as the master database. The
System Manager feature provides tools to select the database. After the database recovery and
replication, the System Manager Geographic Redundancy servers revert to the normal operation
mode, Active-Standby.
database occur automatically. DRS replicates only the data that has been updated since the
last replication. Automatic synchronization is a scheduled activity and occurs after each fixed
interval of time as set in the configuration files.
The data from the master database is sent to the replica node in batches. DRS creates replication
batches whenever the data in the master database is added, modified, and deleted.
Using DRS, you can:
• View replica nodes in a replica group.
• Repair the replica nodes that are not synchronized. The repair action replicates the required
data from System Manager.
Fault management
The Fault management service presents the status of alarms, traps, and notifications received by
System Manager and its components, and the other elements that are integrated with the System
Manager SAL agent. The Fault management service maps events to alarms and tracks the state
of alarms. Using the Fault Management service, you can acknowledge and clear alarms.
The Alarm management service provides a central point for receiving alarms that System
Manager and other components generate. The service supports alarm monitoring,
acknowledgement, configuration, clearing, and retiring. You can also browse System Manager for
historical alarm events.
Logging service
The Logging service provides configuration capabilities and overall management of logs. It
receives and stores log events and harvests file-based logs or local database logs.
The log viewer is integrated with the common console to provide consistent presentation of log
messages for System Manager and the adopters. It displays a list of logs where you can view the
details of each log, search for logs, and filter specific logs. Log details include information about
the event that generates the log and the severity level of the log. You can search logs based on
search conditions and set filters to view logs that match the filter criteria.
Log Harvester
The Log Harvester service manages the retrieval, archival, and analysis of harvested log files
stored in hosts or elements on which Serviceability Agent is enabled. The Serviceability Agent
harvests the logs and sends the harvested logs to the Logging service through HTTPS. The
logging service does the following:
• Identifies a successful harvest request related to a harvest profile.
• Accepts the file segments.
• Creates a well-defined file structure, and saves the request in the System Manager node.
You can harvest log files for one or more products of the same or different types running on the
same or different computers. The system displays the list of file archives and respective profiles
on the log harvesting user interface, and the status of each archive is available in the user
interface table.
Audit Logging
System Manager Release 7.1 and later support the Audit Logging configuration. By using this
configuration, System Manager can notify the administrator and perform the configured action
during one or all of the following events:
• Audit failure
• 75% occupation of audit partition
• 90% occupation of audit partition
Scheduler
The Scheduler service provides a generic job scheduling service for System Manager and the
adopting products. It provides an interface to execute a task on demand or on a periodic basis. So
you can schedule a job to generate an output immediately or set the frequency of the task
execution to run on a periodic basis. You can also modify the frequency for a periodic job. After
you define a task or a job, System Manager creates instances of the task, monitors the execution
of the task, and updates the status of the task.
Scheduled jobs can be of following three types:
• system scheduled
• admin scheduled
• on-demand
Multi Tenancy
Using the Multi Tenancy feature, tenants can share the same instance of the application, while
allowing the tenants to manage users to fit the customer needs as if the application runs on a
dedicated environment.
You can manage Multi Tenancy from the System Manager web console. System Manager
supports the following capabilities:
• Administer the tenant.
• Administer tenant administrators for a tenant.
• Administer the organization hierarchy of the tenant.
• View the tenant hierarchy on the Tenant Management and User Management pages.
• View the tenant associated with a user.
• Create and edit the user associated with a tenant from the User Management page.
System Manager provides a tenant administration dashboard that requires administrator
credentials.
By default, the Multi Tenancy feature is disabled. To use the Multi Tenancy feature, you must
manually enable it. After enabling the Multi Tenancy feature, you cannot disable the feature.
System Manager supports maximum 250 tenant partitions as part of System Manager Multi
Tenant Management.
Note:
• From Release 8.0 and later, System Manager Profile 1 is not supported. If System
Manager is on a pre Release 8.0 and using the Profile 1, ensure that the server has the
required resources to configure Profile 2 on Release 8.0 and later.
• System Manager Release 8.0 and later profile 2 does not support CSR2 Small Appliance
Virtualization Platform Server. Therefore, if you are upgrading from System Manager
Release 7.1 to Release 8.0 and later on Appliance Virtualization Platform, you must use
CSR2 Medium Appliance Virtualization Platform Server. For more information about the
Appliance Virtualization Platform CSR2 server types, see Avaya Aura® Communication
Manager Hardware Description and Reference.
Note:
From Release 8.0 and later, System Manager Profile 1 is not supported. If System Manager is
on a pre Release 8.0 and using the Profile 1, ensure that the server has the required
resources to configure Profile 2 on Release 8.0 and later.
Configuration management
Configuration management provides a configuration repository for System Manager services.
Configuration management is responsible for storing configuration data, also called as profiles, for
System Manager services and notifying the services of configuration changes.
You can view and edit a profile of a service using Configuration management.
Security features
OVA Signing
OVA signing is a security feature where OVA files are digitally signed to ensure file integrity. The
system verifies the digital signature of the OVA, feature pack, and service pack before deploying,
upgrading, and patching operations.
Security hardening
Using the security hardening feature, you can enable or disable military grade hardening or
commercial grade hardening for System Manager. Enabling military grade hardening in System
Manager enables commercial grade hardening by default.
It also facilitates a system with higher security and restricts unauthorized access and changes to
the system settings.
Certificate-based authentication
With System Manager 7.1, you can disable the password-based login and configure the
certificate-based authentication for system login.
The certificates for this authentication can be issued by System Manager as the certificate
authority or by a third-party certificate authority.
To authenticate the user, the system provides the option to retrieve only the selected fields from
the certificate.
Backup encryption
With System Manager 7.1, you can encrypt system backups using a password. Encrypted
backups of a military grade hardened system can be restored to a matching type of hardened
system: military grade, commercial grade, and standard.
Encrypted backups of a commercial grade hardened system can be restored only on a
commercial grade hardened system or a standard hardened system. Likewise, encrypted backups
of standard hardened system can be restored only on a standard hardened system.
Element management
Inventory maintains a repository that records elements deployed on System Manager, including
their runtime relationships. An element in the Inventory refers to a single or clustered instance of a
managed element. Inventory provides a mechanism for creating, modifying, searching, and
deleting elements and the access point information from the repository. Inventory retrieves
information about elements that are added or deleted from the repository.
Inventory integrates the adopting products with the common console of System Manager. Through
Inventory, element type can provide a link that can redirect to the Web page of the element
manager. System Manager Web Console displays the links for only specific element types.
Inventory supports the creation and updation of application systems by importing data from an
XML file. You can import elements only through the Web console.
Group management
Group and Lookup Service (GLS) is a shared service that provides group administration and
lookup service for managed resources. GLS encapsulates the mechanisms for creating, changing,
searching, and deleting groups and group memberships. Use GLS to group resources in ways that
work best for the business, such as organizing resources by location, organization, and function.
On the System Manager web console, with GLS, you can assign different roles to administrators
and allow administrators to perform only limited tasks on group of resources. For example, you
can create a user group so that only an authorized user can manage the user group.
GLS supports group administration for the following common resources:
• Shared across elements, such as roles and users
• Unshared element-specific resources
GLS contains a repository of groups and memberships from System Manager and other
applications that use the GLS service. GLS synchronizes the resources with other Avaya
applications and services that manage these resources. GLS maintains resource IDs and their
group memberships. With GLS, you can search for one or more resources based on their attribute
values and get resource attributes for one or more resources.
License management
System Manager provides Web-based license manager (WebLM) to centrally manage licenses for
one or more Avaya software products for your organization. All Avaya applications that use
WebLM for license management use WebLM that System Manager provides instead of WebLM on
System Platform.
System Manager WebLM supports the Centralized licensing feature for Avaya Aura®
Communication Manager.
To track and manage licenses in an organization, WebLM requires a license file from the Avaya
Product Licensing and Delivery System (PLDS) website at https://plds.avaya.com.
Template management
Using Templates, you can specify specific parameters of an endpoint or a subscriber once and
reuse the template for subsequent tasks of adding endpoints or subscribers. You can use default
templates or add your own custom templates.
The two categories of templates are: default templates and user-defined templates. You cannot
edit or delete the default templates. However, you can modify or remove user-defined templates at
any time.
Subscriber management
Using Subscriber Management, you can manage, add, change, remove, and view subscriber data.
Subscriber management supports Avaya Aura® Messaging, Communication Manager Messaging,
and Modular Messaging objects.
Discovery Management
You can discover specific devices within the network using the Discovery Management capability
of System Manager. You can also manage the Simple Network Management Protocol (SNMP)
access parameters used for the discovery process. Device discovery discovers your network,
including subnets and nodes.
Element Cut Through
Using the Element Cut-Through link, you can gain access to the Communication Manager cut
through the Element Cut-Through page. As an administrator, you have permission to gain access
to the Communication Manager cut through.
Certification validation
With System Manager Solution Deployment Manager and Solution Deployment Manager client,
you can establish a certificate-based TLS connection between the Solution Deployment Manager
service and a host that is running Avaya Aura® 7.x and later applications. This provides secure
communications between System Manager Solution Deployment Manager or the Solution
Deployment Manager client and Appliance Virtualization Platform or ESXi hosts or vCenter.
The certificate-based sessions apply to the Avaya Aura® Virtualized Appliance offer using host
self-signed certificates and the customer-provided Virtualization Environment using host self-
signed or third-party certificates.
You can check the following with certificate-based TLS sessions:
• Certificate valid dates
• Origin of Certificate Authority
• Chain of Trust
• CRL or OCSP state
• Log Certificate Validation Events
Solution Deployment Manager checks the certificate status of hosts. If the certificate is incorrect,
Solution Deployment Manager does not connect to the host.
For the correct certificate:
• The fully qualified domain or IP address of the host to which you are connecting must match
the value in the certificate SAN or the certificate Common Name and the certificate must be
in date.
• Appliance Virtualization Platform and VMware ESXi hosts do not automatically regenerate
their certificates when host details such as IP address or hostname and domain changes.
The certificate might become incorrect for the host.
If the certificate is incorrect:
• For the Appliance Virtualization Platform host, Solution Deployment Manager regenerates the
certificate on the host and then uses the corrected certificate for the connection.
• For the VMware ESXi host or vCenter, the system denies connection. The customer must
update or correct the certificate on the host or vCenter.
For more information about updating the certificate, see “Updating the certificate on the ESXi
host from VMware”.
Note:
Solution Deployment Manager:
• Validates certificate of vCenter
• Validates the certificates when a virtual machine is deployed or upgraded on vCenter
managed hosts
With Solution Deployment Manager, you can only accept certificate while adding vCenter. If a
certificate changes, the system gives a warning that the certificate does not match the certificate in
the trust store on Solution Deployment Manager. You must get a new certificate, accept the
certificate as valid, and save the certificate on the system.
To validate certificates, you can open the web page of the host. The system displays the existing
certificate and you can match the details.
Clients only need to provide identity information such as email addresses or Windows userid
and enterprise credentials.
• Web Deployment Service: Supports publishing and deploying of UC client updates for end-
users.
Important:
If you run the report generation script when an upgrade is in progress on System Manager,
the upgrade might fail.
Avaya Solutions Platform 130 Appliance (Dell PowerEdge R640) is a single host server with
ESXi 6.5 preinstalled.
• Kernel-based Virtual Machine Virtualized Environment
Topology
The following is an example of a deployment infrastructure for System Manager on VMware.
Topology
The following diagram depicts the architecture of the Avaya applications on the Infrastructure as a
Service platform. This diagram is an example setup of possible configuration offered by Avaya.
Important:
The setup must follow the Infrastructure as a Service deployment guidelines, but does not
need to include all the applications.
tested RPMs and follow the instructions in the PSN periodically published by Avaya. PSN is
available at PSN020361u.
Note:
For information about RPM updates for the Red Hat Enterprise Linux operating system and
required changes to operating system files on Software only installation, see Avaya Aura®
Software Only White paper on the Avaya Support website.
Supported platforms
You can deploy the Avaya Aura® application software-only ISO image on the following platforms:
• VMware
• Kernel-based Virtual Machine (KVM)
• Hyper-V
Note:
Starting with the Release 8.0.1, Avaya Aura® applications support Hyper-V.
• Amazon Web Services
• Google Cloud Platform
• Microsoft Azure
Product compatibility
For the latest and most accurate compatibility information, go to http://support.avaya.com/
CompatibilityMatrix/Index.aspx.
When you place an order for the following products using the Avaya Solution Designer, you can
include a new System Manager or an upgrade of System Manager as an entitlement:
• New Communication Manager, Session Manager, or CS 1000
• Upgrade of Communication Manager, Session Manager, or CS 1000
Additionally, you can add the System Manager DVD and the System Manager server to the order.
Geographic Redundancy
The System Manager Geographic Redundancy service replicates Avaya Aura® application support
for two geographically distant System Manager sites with separate subnetworks and across a
WAN. You can change the System Manager management services from one site to another when
one of the sites or servers fails. System Manager Geographic Redundancy sites are set up in
pairs. From the server pair, one server is designated as the primary System Manager server and
the other server as the secondary System Manager server.
Security specification
As the management console for some Avaya products, System Manager must be resilient to
attacks that might cause service disruption, malfunction, or unauthorized access to data. As a part
of the Avaya Aura® solution, System Manager must be protected from security threats, such as:
• Unauthorized access or modification of data
• Theft of data
• Denial of Service (DoS) attacks
• Viruses and Worms
• Web‐based attacks that include Cross‐Site Scripting and Cross‐Site Forgery
For information about security‐related considerations, features, and services for System Manager,
see Avaya Aura® System Manager Security Design on the Avaya Support website at https://
support.avaya.com/security.
Related links
Trust Management on page 58
Trust Management
System Manager uses Trust Management to provision and manage certificates of various
applications, servers, and devices thereby enabling a secure, inter-element communication. Trust
Management provides Identity (Server) and Trusted (Root/CA) certificates that applications can
use to establish mutually authenticated TLS sessions.
System Manager uses a third-party open source application as a Certificate Authority, Enterprise
Java Beans Certificate Authority (EJBCA), to issue Identity and Trusted certificates to applications
through Simple Certificate Enrollment Protocol (SCEP). However, it does not issue certificates to
the endpoints.
For information about getting the endpoint certificates, see the endpoint specific documentation on
the Avaya Support website.
Related links
Security specification on page 58
External authentication
You can configure System Manager to authenticate administrative users through external
authentication services, such as an enterprise directory, Kerberos, or a RADIUS server. An
administrative account is provisioned within System Manager during installation for initial access.
System Manager supports the following authentication authorities:
• Local users
• External RADIUS users
• External LDAP users
• External Security Assertion Markup Language (SAML) users
The authentication scheme policy determines the order in which you can use the authentication
authorities. The authentication servers policy controls the settings for the external SAML, LDAP,
RADIUS, and KERBEROS servers.
Related links
SAML authentication on page 59
SAML authentication
For enterprise level Single Sign On, System Manager provides Security Assertion Markup
Language (SAML) authentication. System Manager uses SAML implementation version 2.0 of
OpenAM Release 9.5.4 to provide SAML-based authentication with external Identity Providers.
System Manager uses the web browser Single Sign On profile of the SAML authentication.
Related links
External authentication on page 59
You can perform LDAP synchronization of Microsoft Active Directory or other supported directory
server administrator roles with System Manager administrator roles. The capability includes
system roles and custom roles on System Manager.
Note:
Granular RBAC is not supported for managing Avaya Meetings Server, Web Gateway, and
Work Assignment elements by creating custom roles.
Training
The following courses are available on the Avaya Learning website at http://www.avaya-
learning.com. After you login to the website, enter the course code or the title in the Search field
and click Go to search for the course.
Course code Course title
20460W Virtualization and Installation Basics for Avaya Team Engagement Solutions
20970W Introducing Avaya Device Adapter
20980W What's New with Avaya Aura® Release 8.1
71200V Integrating Avaya Aura® Core Components
72200V Supporting Avaya Aura® Core Components
20130V Administering Avaya Aura® System Manager Release 8.1
21450V Administering Avaya Aura® Communication Manager Release 8.1
Support
Go to the Avaya Support website at https://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release notes,
downloads, and resolutions to issues. Use the online service request system to create a service
request. Chat with live agents to get answers to questions, or request an agent to connect you to a
support team if an issue requires additional expertise.
Related links
Using the Avaya InSite Knowledge Base on page 65
Primary System The first or the master System Manager server in a Geographic
Manager server Redundancy setup that serves all system management requests.
Secondary System The System Manager server that functions as a backup to the primary
Manager server System Manager server in a Geographic Redundancy setup. The
secondary System Manager server provides the full System Manager
functionality when the system fails to connect to the primary System
Manager server.
Excel (continued) K
import ............................................................................31
export Kernel-based Virtual Machine
user data .......................................................................30 overview ....................................................................... 47
user data to Excel .........................................................31
export CM Agent profile ....................................................... 31
export CM station data .........................................................31
L
extended hostname validation license ..................................................................................55
overview ....................................................................... 43 license management ............................................................37
external authentication .........................................................59 licensing requirements .........................................................55
logging ................................................................................. 29
F logging service .....................................................................29
Log Harvester overview ....................................................... 29
Fault management ...............................................................28 log harvesting ...................................................................... 29
feature description log viewer .............................................................................29
System Manager .......................................................... 16
finding content on documentation center .............................63
finding port matrix ................................................................ 62
M
footprint flexibility ................................................................. 34 manage application instances ............................................. 36
footprint hardware matrix manage elements ................................................................ 36
System Manager on Appliance Virtualization Platform .33 manage license ....................................................................37
System Manager on VMware ....................................... 34 Management interface ......................................................... 25
military grade hardening ...................................................... 35
G Multimedia Messaging
System Manager .......................................................... 41
geographic redundancy Multi Tenancy .......................................................................32
configuration prerequisites ........................................... 27 My Docs ...............................................................................63
Geographic Redundancy ..................................................... 26
geographic redundancy configuration
prerequisites ................................................................. 27
N
geographic redundancy configuration prerequisites ............ 27 new features
GLS ......................................................................................36 Communication Manager ............................................. 39
Granular role-based control ................................................. 38 new in release
Group and Lookup Service .................................................. 36 System Manager 8.1 .................................................... 13
Group management .............................................................36 new in release 8.1.1
System Manager .......................................................... 12
H new in release 8.1.2
System Manager .......................................................... 12
hardware supported new in release 8.1.3
System Manager .......................................................... 24 System Manager .......................................................... 10
new in release 8.1.3.1
System Manager ............................................................ 9
I
IaaS O
overview ....................................................................... 49
import offer
user data .......................................................................30 Avaya virtualized appliance .......................................... 44
user data from Excel .....................................................31 Infrastructure as a Service ............................................44
import CM station data .........................................................31 Software-only environment ...........................................44
Infrastructure as a Service Virtualized Environment ................................................44
overview ....................................................................... 49 Out of Band Management ....................................................25
InSite Knowledge Base ........................................................65 OVA
IPv6 support .........................................................................25 signing .......................................................................... 35
OVA signing ......................................................................... 35
overview .........................................................................47, 52
Amazon Web Services (AWS) ......................................50
W
watch list .............................................................................. 63
WebLM .................................................................................37
X
xml
Bulk import and export ..................................................41