EASING YOUR DAILY TASKS: SYSTEM MANAGER AND · PDF fileSYSTEM MANAGER AND SOLUTION DEPLOYMENT...
Transcript of EASING YOUR DAILY TASKS: SYSTEM MANAGER AND · PDF fileSYSTEM MANAGER AND SOLUTION DEPLOYMENT...
EASING YOUR DAILY TASKS:
SYSTEM MANAGER AND SOLUTION
DEPLOYMENT MANAGER - RELEASE 7
Michael DiSaia
Thank you Sponsors!
Global
Sponsors
Gold
Sponsors
Silver
Sponsors
@Avaya
#AvayaATF
Join the
Conversation
© 2016 Avaya Inc. All right reserved 4
Avaya Aura®
System Manager
Avaya
Communicator
Portfolio Applications Avaya Aura Presence Services
Avaya Aura Messaging
Avaya Aura Contact Center
Avaya Aura Experience Portal
Avaya Breeze ®
Applications and Snap-Ins
Avaya Session
Boarder
Controller for
Enterprise SIP
Trunks
PSTN
Avaya Aura® Session Manager
Avaya Aura®
Media Server
Avaya CS 1000 Avaya Aura®
Communication
Manager
Avaya Aura®
for Survivable
Remote
3rd Party PBXs
Avaya
SIP endpoints
Avaya Scopia®
Clients
Applications and Snap-Ins
Avaya Aura
Conferencing
Geo-Redundant
Failover
PRI
SEC
Avaya Aura® Solution Architecture
New in AA7
© 2016 Avaya Inc. All right reserved 5
SUMMARY OF SYSTEM MANAGER 7.0
FUNCTIONALITY
Common User Provisioning
– Provision user services for all apps in
single workflow
Enterprise Directory Integration – AD, OpenLDAP, Domino, eDirectory and
SunOne
Bulk Import and Export (Excel/XML)
User Provisioning Rules
Web Services Interface – User Provisioning
Multi-Tenant Management
Web Services Interface – Routing and Dialing Plan Management
Administrator Authentication and Role Based Access Control (RBAC)
End-User Self Provisioning Portal
Embedded Identity Management (OpenSSO) for Authentication
Enterprise Level Authentication
Primary Management Interface (Central UI & Data Master)
– Session Manager
– Presence Services
– Avaya Breeze
– EDP Snap-in’s: Work Assignment,
Performance Center, Interaction Center, etc.
SMGR and CM Database Reporting
Centralized WebLM Licensing
Runtime Topology Service (RTS) – Discovery and Inventory
Scheduler Framework
Trust Management (PKI) framework
Data replication and distribution
Fault Management – Central Logging and Alarm collection
Geographic Redundancy
Solution Deployment Manager
BEFORE WE DIVE INTO WHAT IS NEW
WITH SYSTEM MANAGER RELEASE 7
What’s Changing with Avaya’s Appliance offering to support Avaya Aura 7 ?
© 2016 Avaya Inc. All right reserved 7
AVAYA AURA® 7 OFFER
Avaya Aura® 7.0 Deployment Options: – Virtualized Environment (Customer Supplied Servers and hypervisor)
– Collaboration Pod (Avaya Supplied Servers)
– Appliance Model (Avaya Supplied Servers)
Note: Support of Aura 7 on CPOD will be post 7.0 GA
© 2016 Avaya Inc. All right reserved 8
VIRTUALIZATION IN THE AVAYA APPLIANCE MODEL
The System Platform virtualization hypervisor is being replaced by a VMware based
Appliance Virtualization Platform (AVP)
Definition: The term appliance refers to the offer in which Avaya is responsible for supplying the
hardware, the hypervisor (VMware) and the application images to the customer.
ESXi (VMware vSphere)
App
A
App
B
Appliance Virtualization Platform
Utility Services with Services Port VM
In Avaya Aura® 6.x with System Platform In Avaya Aura® 7
Xen Hypervisor for virtualization
The hypervisor will be provided by VMware
Common Services (CDOM) Most functionality will be provided by Solution Deployment
Manager (which is a component of System Manager) or
other System Manager provided Functionality.
Note that the Release 7.0 Solution requires System Manager (SMGR) to be installed somewhere in the customer solution in order to
manage the Release 7.0 Applications
© 2016 Avaya Inc. All right reserved 9
VIRTUAL APPLIANCE VS.
VIRTUALIZED ENVIRONMENT
Offer Element Virtual Appliance Virtualized Environment
Server Provided By: Avaya
(Common Servers are preloaded with
AVP, Embedded Servers are shipped
without AVP preloaded)
Customer
Hypervisor Avaya Provided Appliance
Virtualization Platform (AVP) provides
a hypervisor based on an OEM
version of VMware (ESXi 5.5)
Customer Provided VMware
(ESXi 5.0, 5.1 or 5.5)
ESXi 6.0 – Supported May 2016
VMware Licenses Included in Virtual Appliance offer from
Avaya
Customer Provided
Server and Virtualization
Management
Solution Deployment Manager (part of
System Manager)
vCenter is not required or supported
with Release 7.0
VMware vCenter &vSphere Client
Solution Deployment Manager
can be used for deploying and
updating Avaya applications
VMware Training required none VMware Certification is required
to manager a customer’s VMware
infrastructure
SYSTEM MANAGER 7.0 SOLUTION
DEPLOYMENT MANAGER (SDM)
© 2016 Avaya Inc. All right reserved 11
Avaya Aura Upgrade Vision
1. Discover Elements
2. Analyze & Recommend
3. Download Files
4. Pre-Upgrade Checks
5. Schedule Upgrades
6. Execute Upgrade
7. Monitor Progress
Goal: Provide a centralized upgrade solution to enable
customers to easily move to the latest VE/SP-based Avaya
Aura
“Tech-less install/upgrade” – One-click upgrade
Single tool should support installation, upgrade & patching
Support centralized as well as local execution
One-step direct upgrade (not stepwise by release)
Scope: Avaya Aura core comprising CM (with related Gateways, TN
boards, etc.), SM (including BSM), Breeze PS, AES, WebLM, SMGR
High-Level Workflow 1. Discover the Avaya Aura elements in the customer’s network 2. Analyze whether elements and components are on the latest major/minor release, feature pack or service pack; Recommend updates: sequence of element and component upgrades 3. Download files needed for upgrading elements and components 4. Perform pre-upgrade checks to ensure that conditions for successful upgrade are met 5. Schedule upgrade sequence 6. Perform VE, AVP or SP-based upgrades and updates 7. Monitor and indicate upgrade progress; confirm upgrade success or perform rollback in case of failure
© 2016 Avaya Inc. All right reserved 12
Time Consuming
Manual & Tedious
Error Prone
Faster
Automatic
Reliable
SDM: SIMPLER UPGRADES / UPDATES REDUCING TCO
FROM TO
Manual All platforms done by hand.
Automatic After upgrade to AVP, drive
application upgrade from anywhere.
Waiting Time lost waiting for next step.
Background Sequence events and have them
run in the background.
Error Prone Manual readiness assessment.
Reliable Integrated checks to confirm
upgrade readiness.
Avaya Aura® 7.0 SDM includes automated upgrade support
for Communication Manager, Session Manager and Branch
Session Manager
© 2016 Avaya Inc. All right reserved 13
SYSTEM MANAGER 7.0 FEATURES FOR
DISCUSSION
Solution Deployment Manager (SDM)
Solution Deployment Manager Client (SDM-Client)
Automated Avaya Aura 7.0 Upgrade-Migrations
System Manager – CM and Database Reports
User Management
User Provisioning Rules (UPR) and LDAP Sync Enhancements
© 2016 Avaya Inc. All right reserved 14
SOLUTION DEPLOYMENT MANAGER OVERVIEW
System Manager with embedded SDM
is the primary management solution for
Avaya Aura® 7.0 and is Required when an
Aura 7 Application is part of an Aura Solution
Consolidates disparate tools into a single
centralized solution deployment manager
Deploys Application Software
– Optimizes physical resources required by the
Aura Applications
– Provides Lifecycle Management of the
deployed applications
Keeps Applications Current
– Identifies needed updates
– Patches applications/platform
Streamlines Upgrade-Migration Process
– Centrally driven upgrades with sequenced
tasks orchestrated by SMGR-SDM
Avaya Virtual Application
Manager (AVAM)
System Platform
Common Services
Software Manager
in SMGR
Solution Deployment
Manager in SMGR
© 2016 Avaya Inc. All right reserved 15
SOLUTION DEPLOYMENT MANAGER (SDM)
OVERVIEW (CON’T)
SMGR 7.0 with embedded SDM runs on an Avaya Provided Appliance which includes:
– Server Hardware
– Appliance Virtualization Platform (AVP) Hypervisor
– SMGR 7.0 application OVA.
SMGR-SDM also runs on customer provided Virtualization Environment (VE) solution.
SMGR-SDM will have Virtual Machine Management functionality to replace existing System Platform and AVAM capabilities.
A PC based SDM-Client will be available to deploy OVAs in the event SMGR is not available.
Support for all SDM features for all Aura Application will be done in phases, with the initial feature set and framework available in SMGR 7.0.
© 2016 Avaya Inc. All right reserved 16
DEPLOYMENT FUNCTIONALITY IN SMGR-SDM
– Session Manager (SM)
– Branch Session Manager (BSM)
– Application Enablement Service (AES)
– Utility Services (US)
– Communications Manager (CM)
– CM Messaging (CMM)
– Avaya Breeze (including Presence)
– Avaya Aura Media Server (AAMS)
– WebLM
– SAL
– System Manager (SMGR) -(deployed
using SDM-Client only)
Deployment of Aura Applications in both Customer Provided VE and Avaya Appliance Offerings. OVAs supported:
OVA
© 2016 Avaya Inc. All right reserved 17
SDM FUNCTIONALITY RELATED TO DEPLOYMENT
1. Define Location
2. Define Host and Access Credentials
VM Mgmt (start, stop, edit, delete, restart)
Monitor VM and Host Resources
3. Create VMs and Deploy OVA
1. IP Networking Configuration (IP Add, Subnet, Gw, DNS, NTP) 2. Set Flexible Footprint ( set resource requirements based on profile) 3. SDM verifies the hardware requirements (vCPU, vDisk , Memory) 4. Accept EULA 5. Deploy OVA
VM Dashboard
© 2016 Avaya Inc. All right reserved 18
‘UPDATE’ FUNCTIONALITY IN SMGR-SDM
Updates is intended to generically cover patching of an application and can include Kernel patches, Security patches, Hotfixes, Service Packs and Feature Packs.
Applicable to Customer Provided VE and Avaya Appliance Offers for AA 7 Applications
Ability to Apply Updates from SMGR SDM to the following Avaya Aura Applications:
– Communication Manager and Adjuncts (Rel 6.x and 7.0)
– Session Manager (Rel 7.0)
– Branch Session Manager (Rel 7.0)
– Utility Server (Rel 7.0)
– Communication Manager Messaging (Rel 7.0)
– WebLM (Rel 7.0.1)
– Avaya Virtual Platform (AVP) 7.0 - Hypervisor Avaya Provided Appliance
System Manager 7.0 Updates will be done from the SDM Client or via the SMGR CLI
© 2016 Avaya Inc. All right reserved 19
‘UPDATE’ FUNCTIONALITY IN SMGR-SDM (CON’T)
View all elements and their associated elements (e.g. TN boards, Gateways, Media Modules) for update in a hierarchical table view.
Ability to select SMGR-SDM controlled and automated update job (analysis, pre-upgrade checks, job sequencing) or a System Administrator controlled update job (new 7.0.1)
Create an On-demand or Scheduled Update Operation
Monitor an Update’s progress and status
Define manual or auto-commit Update; with roll back option
Uninstall an Update
SDM has the ability to run up to 100 simultaneous update jobs (5 Upgrade/Update) groups with a maximum of 20 elements in a group)
© 2016 Avaya Inc. All right reserved 20
‘UPGRADE’ FUNCTIONALITY IN SMGR-SDM
The term Upgrades is intended to cover Release-to-Release Software Upgrades that do not require hardware changes or hypervisor changes; Upgrade process that are triggered via the normal process without requiring additional backup and restore steps.
Existing CM Upgrade functionality introduced in AA6.2 Feature Pack 4 (SMGR 6.3.8) will be available with SDM. Includes upgrading Communication Managers, TN Boards, Branch Gateways, Media Modules. This also includes the automation of an upgrade of CM 6.x templates to 6.3.6 (FP4), Pre-Upgrade Check mechanism and job sequencing.
Avaya Aura applications running on System Platform moving from Release 6.x to Release 7.0 are discussed under Migrations
Current Avaya Aura Applications running in a Customer Provided VE moving from Release 6.x to 7.0 will use the established 6.x upgrade process that is documented in each application’s VE Upgrade Guide.
Avaya Aura upgrade support via SMGR-SDM for 7.0 to 7.x will be supported in Release 7.1. Includes support in the Avaya Provided Appliance and Customer VE offers.
© 2016 Avaya Inc. All right reserved 21
AUTOMATED MIGRATION FUNCTIONALITY IN
SMGR-SDM
The term Migration is intended to cover special upgrade situations where there is a Hardware Server Change; the main OS of the system is changing and requires a complete re-installation, a Hypervisor change
SDM automated migration functionality is available in SMGR-SDM 7.0 running in the Avaya Appliance Offer and Customer Provided VE solutions.
Used to migrate Avaya Aura Rel 6 applications running on an Avaya appliance to Rel 7 running on the AVP appliance or Customer Provided VE
Automated tasks include: apply Pre-Migration Patch, perform a backup of the existing translations and configuration; deploy the 7.0 OVA into the VMware Environment; and restore the data from backup.
SMGR-SDM must perform Pre-Upgrade/Migration checks prior to scheduling or executing the automated Upgrade-Migration. The checks are intended to reduce failures and errors in the field. The following is a sample of the checks performed:
– Hardware Compatibility and Free of Errors (Raid Battery)
– Validate required software files are downloaded/available in the Software Library
– Sufficient CPU, Memory and Hard disk
– Sufficient Bandwidth
© 2016 Avaya Inc. All right reserved 22
AUTOMATED MIGRATION FUNCTIONALITY IN
SMGR-SDM (CON’T)
SDM to orchestrate and automate the migration of the following applications to Release 7.0:
– Communication Manager (from 6.x Templates):
Duplex CM Main / Survivable Core [CM]
Simplex CM Main / Survivable Core [CM, CMM, US]
Embedded CM Main [CM, CMM, US]
– Branch Session Manager (BSM) (from 6.x Templates):
Simplex Survivable Remote [CM, BSM, US]
Survivable Remote [CM, BSM, US]
– Communication Manager 5.2.1
– Session Manager 6.x
– System Manager 6.x (SDM-Client)
AVP
Session
Manager 7.0
Customer
Provided VE
SMGR-SDM
7.0
Session
Manager 6.3
Communication
Manager 6.1
Communication
Manager 6.3
CM 7.0
CM 7.0
Linux
OVA
1. Application Analysis 2. Pre-Upgrade Checks 3. Pre-Migration Patch 4. Backup 5. Configuration 7.0 App 6. 7.0 OVA Deployment 7. Restore
Like-for-Like
Upgrade/Migration
SP-8800
SP-8800
© 2016 Avaya Inc. All right reserved 23
THE PRIMARY BENEFITS IN USING THE AVAYA
AURA 7 AUTOMATED UPGRADE-MIGRATION
CAPABILITIES ARE:
To move from a manual step-by-step procedure local to the application server to an automated migration procedure.
To drive application upgrades and migrations remotely from a centralized System Manager.
To eliminate time lost waiting for each next step in the upgrade-migration process, by using an automated sequencing of tasks with the application upgrade-migration events running in the background without manual intervention.
To move from multiple manual tasks that require human intervention that can be error prone, to reliable integrated checks that assess and confirm upgrade-migration readiness
© 2016 Avaya Inc. All right reserved 24
SOLUTION DEPLOYMENT MANAGER -CLIENT (SDM-
CLIENT) OVERVIEW
System Manager 7.0
SDM-Client 7.0
Note that the SDM-Client is not intended to be the main solution, but rather cover special cases where a Centralized SMGR-SDM is not available.
SMGR with embedded SDM is the primary management solution for Avaya Aura 7.0
AVP
AVP
RH Linux
For the initial SMGR deployment or where SMGR is not accessible (such as certain remote locations or staging of Aura applications), there will be a SDM-Client that can reside on a technician’s laptop/PC. This will provide the necessary functionality to install the OVAs on either an Avaya Appliance or Customer Provided VE. The SDM client will use the same API back end and user interface as the main SMGR/SDM.
OVA
© 2016 Avaya Inc. All right reserved 25
FUNCTIONALITY AVAILABLE IN THE SDM-CLIENT
Supported Windows Platform
– Windows 7 (Professional / Enterprise) – 64bit
– Windows 8.1 (Professional / Enterprise) – 64bit
Supported same Web Browsers as SMGR 7.0
Support Flexible Footprint Feature (size OVA capacity of applications) *
SDM Client’s Ability to support application OVA Deployment. Same applications as the centralized SMGR-SDM (one application at a time can be deployed). To Avaya Appliance and Customer VE
Local computer or an HTTP URL for selecting application OVA file to deploy.
Initial application configuration as part of the OVA deployment process*
Ability change Hypervisor IP Address on the Avaya Virtual Platform (AVP)*
Ability to support Hypervisor Patching on the Avaya Virtual Platform (AVP)*
SDM-Client’s ability to support SMGR patching only. Patching of other Avaya Aura applications must use centralized SDM on SMGR *
Lifecycle Management of the OVA Applications deployed to a VM. Includes the ability to start, stop, and reset all or selected VMs *
SDM-Client required for initial deployment of System Manager and for SMGR 6.x migrations to SMGR 7.0
* Also Available at Central SDM in SMGR
© 2016 Avaya Inc. All right reserved 26 26
SMGR SDM and SDM Client feature comparison
Centralized Solution Deployment Manager Solution Deployment Manager - Client
VMware lifecycle management VMware lifecycle management
Deployment of Avaya Aura® applications Deployment of Avaya Aura® applications
Deployment of hypervisor patches (AVP) Deployment of hypervisor patches (AVP)
Upgrade / Migration of Aura Applications Upgrade / Migration of System Manager
Deployment of Application patches Deploying System Manager patches
Discovery and Inventory
Analyze
Create Software Library
Upgrade / Migration Task Sequencing
Upgrade / Migration Dependency Checks
RBAC and Administrator Activity Logging
© 2016 Avaya Inc. All right reserved 27
WHY IT IS IMPORTANT TO USE SDM TO DEPLOY
AURA APPLICATIONS RUNNING ON AVP
When deploying with SDM client onto AVP the following is done automatically:
– CPU and Memory reservations for the VM will be automatically sized correctly for the Server
– VM hard disk will be correctly sized if applicable
– VM networking will be automatically configured
– Correct VM disk format will be selected
– A static route for the Services Port will be added to the VM
– The VM will be registered to the Utility Services VM for Services Port connection
– Will ensure Utility Services is present for security and alarm forwarding for the server
Deploying Avaya Aura applications to the Avaya Appliance (AVP) using the vSphere Client or vCenter is not supported
© 2016 Avaya Inc. All right reserved 28
APPLICATION ‘UPDATE’ WORK FLOW –
COMMUNICATION MANAGER PATCHING SCENARIO:
‘Update’ being the DEPLOYMENT of a Patch (hot fix), Service Pack or Feature Pack.
Ability to Apply Updates from SMGR SDM to the following Avaya Aura 7.0.x Applications:
– Communication Manager and Adjuncts (TN Boards, Media Modules)
– Session Manager
– Branch Session Manager
– Utility Server
– Communication Manager Messaging
– WebLM (7.0.1)
– Avaya Virtual Platform (AVP) – ESXi Host running on Avaya Provided Appliance
This scenario assumes the following is setup – System Manager 7.0.x is up an running
– Hardware and Applications are defined in the Elements Inventory as a result of a Discovery (manual or SNMP based)
– Software Library is defined and required software is on the library
– User Setting for PLDS or Alternate Source are defined (not required for custom patching which is new in release 7.0.1)
© 2016 Avaya Inc. All right reserved 29
UPGRADE MANAGEMENT PAGE –
SMGR ORCHESTRATED (ANALYZE AND CHECKS)
1.
2.
© 2016 Avaya Inc. All right reserved 30
UPGRADE ACTIONS – SMGR (3A) OR ADMIN
(3B)CONTROLLED PATCHING
3a
3b
© 2016 Avaya Inc. All right reserved 31
PATCH CONFIGURATION –
4.
Override Pre-upgrade Check is enabled if any of the recommended pre-upgrade check fails for the element. Admin is only allowed to edit configuration if the override pre-upgrade check checkbox is checked. Mandatory pre-upgrade checks that fail will not allow access to the software update Or Upgrade configuration area. Pre-upgrade (or upgrade)checks must be run for SMGR controlled upgrades or upgrades (3a option). For custom patching the administrator can skip running the pre-upgrade checks. For CM, SM and BSM, the checks are still run in the background.
© 2016 Avaya Inc. All right reserved 32
EXAMPLE OF PRE-UPGRADE CHECK DETAILS
Details are accessible by clicking on the icon On the Upgrade Management Page
© 2016 Avaya Inc. All right reserved 33
PATCH CONFIGURATION AND SELECTION
5. Select Update or Upgrade
6. Select Library Source
7. Select Patch
8. Select License Agreement
© 2016 Avaya Inc. All right reserved 34
SAVE CONFIGURATION AND ENABLE JOB
9. Schedule Job
© 2016 Avaya Inc. All right reserved 35
UPDATE STATUS
Visual indicators job is running
© 2016 Avaya Inc. All right reserved 36
PATCH JOB COMPLETE AND SUCCESSFUL
Visual indicators job was successful
© 2016 Avaya Inc. All right reserved 37
DETAILS FOR THE PATCH UPDATE JOB
Details for the entire patch job are accessible by clicking on the icon on the Upgrade Management Page
ADDITIONAL ENHANCEMENTS TO
IMPROVE MANAGEMENT TASKS
© 2016 Avaya Inc. All right reserved 39
SYSTEM MANAGER – CM AND DATABASE
REPORTS
System Manager provides the ability to generate reports based on Communication Manager objects that are stored in the System Manager database and list/Display Reports run on Communication Manager.
Capabilities include: – Reports can be generated in CSV, PDF or HTML
formats
– Ability to customize report output (e.g. which
fields, report header, delimiters)
– Ability to send report to a predefined Email
address. As well as to Secure Copy (SCP) and
sFTP report output to a file server
– Ability to control access via the System Manager
RBAC infrastructure
– A total of 500 canned CM List and Display reports
will be available in SMGR 7.0. In addition, the
reporting infrastructure is capable of running
reports against all CM attributes stored in the
SMGR database.
– Enables customers using ASA/MSA Reporting to
have the same services available after migrating
to SMGR.
© 2016 Avaya Inc. All right reserved 40 40 40
REPORT GENERATION WORK FLOW
1. Select CM
2. Select Report Type
3. Select RPT Parameters, Schedule the generate
4. List of Generated Reports
Appendix A in the Administering System manager guide has a list of Reports that are supported
© 2016 Avaya Inc. All right reserved 41 41 41
USER MANAGEMENT – USER PROVISIONING
MANAGER (UPM)
Single point of administration to provision user services for multiple Avaya products
Using User Profile Manager (UPM) you can perform the following tasks:
– Add a user profile (i.e. user identity information)
– View, modify, and delete and existing user profile
– Add and modify a communication profile of a user (services and endpoint)
– Assign or remove permission, roles, and groups
– Manage User Contact Lists
– Global Changes
– Search Utility
Avaya
Communicator
One X Mobile
96xx SIP
Avaya Aura
Conferencing
Avaya Aura
Messaging
Breeze Snap-ins
© 2016 Avaya Inc. All right reserved 42 42 42
UPM AND ENDPOINT SEARCH UTILITY
© 2016 Avaya Inc. All right reserved 43 43 43
USER PROVISIONING RULES (UPR)
Automates the user provisioning process by enabling the creation of provisioning rules that consist of user attributes and configuration data.
The UPR can be associated with a user as part of the user provisioning workflow to automate and simplify the user provisioning process.
UPRs can be used when creating user via the System Manager native User Interface, Web Services API, Bulk Import/Export Utility and LDAP synchronization with an Enterprise Directory Server.
© 2016 Avaya Inc. All right reserved 44 44 44
USER MANAGEMENT - ENTERPRISE
DIRECTORY SYNCHRONIZATION
System Manager supports over 35 attributes that can be synced to an Enterprise
Directory Server. Some examples include, Phone Number, Mailbox Number,
Employee Number, Location Information, User Provisioning Rule, as well as many
other attributes associated with an Employee
User Provisioning Rule Mapping
© 2016 Avaya Inc. All right reserved 45
LDAP SYNC OF ENTERPRISE DIRECTORY ADMIN
ROLES WITH SMGR ADMIN ROLES
System Manager 7.0 introduces the ability to synchronize
Enterprise Directory roles as defined in a customer’s
LDAP Directory to System Manager Administrator roles.
Built upon SMGR’s User Management LDAP Directory
Synchronization feature.
Introduces a new LDAP attribute mapping in SMGR that
allows the Administrator to correlate an LDAP Directory
role to a System Manager role as defined in SMGR
RBAC.
The attribute mapping mechanism includes both pre-
defined system roles as well as custom roles on SMGR.
Simplifies the central administration of System Manager
Administrators
Enterprise LDAP
Server
System Manager 7.0
System Manger 7.0
LDAP Mapping UI
Complete your survey at the end of the session in the Mobile App
✓
✓
✓
✓
✓
Visit Our Smart City
6:30pm 9:00pm
Monday, April 4
7:00am 8:30am
12:15pm 1:30pm
Tuesday, April 5
7:00am 8:30am
12:15pm 1:30pm
6:00pm 8:00pm
Wednesday, April 6
7:00am 8:30am
(Expo closes after
breakfast)
Thursday, April 7
Expo Hours
© 2016 Avaya Inc. All right reserved 49
Backup Slide Material
© 2016 Avaya Inc. All right reserved 50
ADDITIONAL RESOURCES
System Manager 7.x documentation is available on both http://support.avaya.com (under Avaya Aura® System Manager 7.x). The following documentation is available:
– Understanding Avaya Aura® System Manager 7.0
– Implementing Avaya Aura® System Manager 7.0
– Administering Avaya Aura® System Manager 7.0
– Upgrading Avaya Aura® System Manager to 7.0
– Upgrading Avaya Aura® 7.0 Applications
– Deploying Avaya Aura® System Manager 7.0
– Troubleshooting Avaya Aura® System Manager 7.0
– Avaya Aura® System Manager 7.0 Release Notes
– System Manager 7.0 Port Matrix
– System Manager 7.0 SNMP White paper (including MIBS)
– Avaya Aura® System Manager 7.0 Security Guide
Avaya Aura® System Manager 7.x Product Page on the Avaya Sales Portal. https://sales.avaya.com/cs/Sites?lookuphost=/&lookuppage=/en/pss/avaya-aura-system-manager&view=collatera
Avaya Aura® System Manager 7.x on Avaya DevConnect https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_system_manager/releases/7_0/index.gsp
Avaya Aura® System Manager 7.x - Avaya Learning and Certification
https://www.avaya-learning.com/t/Catalog/search/25
© 2016 Avaya Inc. All right reserved 51
SDM AND AURA 7 UPGRADES - SPECIFIC
RESOURCES
Avaya Aura® System Manager 7.0 Solution Deployment Manager Job-Aid (https://downloads.avaya.com/css/P8/documents/101019960)
Chapter 25 of the ‘Administering Avaya Aura® System Manager for Release 7.0’ has details on SDM (https://support.avaya.com/documents/)
Chapter 15 of the ‘Administering Avaya Aura® System Manager for Release 7.0’ has details on setting up element Discovery and Inventory (https://support.avaya.com/documents/)
The Guide ‘Upgrading and Migrating Avaya Aura® applications to Release 7.0’ has details on using SDM to Upgrade/Migrate Aura 7 applications (https://support.avaya.com/documents/)
The Guide ‘Deploying Avaya Aura® applications’ has details on using SDM to Deploy Aura 7 applications using SDM(https://support.avaya.com/documents/)
June 2015 Tech Transfer Site (Partner and Sales-focused):https://sales.avaya.com/cs/Sites?lookuphost=/&lookuppage=/en/general/june-2015-tech-transfer
Avaya Learning Curriculum announcement (Customer-focused): http://avaya-news.com/learning/docs/june015/2015_06_03_AvayaAura7_Curriculum.pdf
The Avaya Aura 7.0 Offer Definition is posted on the sales portal (very informational document to understand the release): https://sales.avaya.com/documents/1399584208566
© 2016 Avaya Inc. All right reserved 52
Common Server Release 2 Specifications (New AVP Based Servers):
The GP Proliant DL360 PG8 is the default server shipped with all new orders
Component DL360PG8 SRVR
LARGE AVP
DL360PG8 SRVR
MEDIUM AVP
DL360PG8 SRVR
SMALL AVP
Form factor 1U 1U 1U
Processor family Intel (2.9 GHz - E5-2667)
Intel (2.3 GHz - E5-2630)
Intel (2.3 GHz - E5-2630)
Number of processors 2 2 1
Memory type 4 GB RDIMM (16) 4 GB RDIMM (8) 4 GB RDIMM (4)
Total memory 64GB 32GB 16GB
Hard Disk Drive 300GB Drives 300GB Drives 300GB Drives
Number of Hard Disk Drive
4 3 2
RAID Level 5 3 1
Network interface 4 4 4
Optical drive DVD+/-RW, SATA, INTERNAL
DVD+/-RW, SATA, INTERNAL
DVD+/-RW, SATA, INTERNAL
Power supply 750W AC 460W AC 460W AC
Number of power supplies
2 2 1
© 2016 Avaya Inc. All right reserved 53
Servers Supported (Servers existing in the field)
Server
SMGR 7.0
HP ProLiant DL360 G7 √
Dell Power Edge R610 √
HP ProLiant DL360 PG8 (Common Server R2) √
Dell Power Edge R620 (Common Server R2) √
√ - Supported X – Not Supported
NOTES: 1. The S8800 that supported System Manager 6.x will no longer be supported for System Manager 7.0 deployments
2. When ordering or deploying multiple servers for a System Manager Geographic Redundancy (SMGR-GR) configuration, all servers must be identical (manufacture, model, server resources).
3. Also note that the SMGR HA or GR configuration is not supported in a mixed hardware configuration where one SMGR instance is running on Avaya Provided Appliances and the second SMGR instance is running on Customer Provided VMware hardware.
© 2016 Avaya Inc. All right reserved 54
System Manager 7.0 on Appliance Virtualization Platform (AVP):
Software Supported Lineup and Virtual Resource Requirements
√ - Supported X – Not Supported
AVP Release SMGR / WebLM 7.0
AVP 7.0 √
Footprint Profile # vCPU
Reserved
Min vCPU
Speed
(MHz)
vRAM Virtual
Hard Disk
CSR1 Support CSR2 Support
Profile-1 (35K users
with 35 BSM’s and
12 SM’s)
4 2290 MHz 9GB 105GB Yes Yes
Profile-2 (35K-250K
users with up to 250
BSM’s and 12 SM’s)
6 2290 MHz 12GB 105GB No (will not fit) Yes
Profile-3 SMGR
High Capacity (35K-
250K users with up
to 500 BSM’s and 28
SM’s
8 2290 MHz 18GB
250GB No (will not fit)
Yes
© 2016 Avaya Inc. All right reserved 55
System Manager 7.0 running in Customer Provided Virtualized Environment:
VMware ESXi Software Supported Lineup and Virtual Resource Requirements
√ - Supported X – Not Supported
Customer Provided VE - VMware ESXi
SMGR / WebLM 7.0
VMware ESXi 5.0 √
VMware ESXi 5.1 √
VMware ESXi 5.5 √
Footprint Profile # vCPU
Reserved
Min. vCPU
Speed (MHz)
Virtual
RAM
Virtual Hard
Disk
CPU
Reservation
Memory
Reservation MB
Profile-1 (35K users
with 35 BSMs and
12SM)
4 2290 MHz 9GB 105GB 9160 9126
Profile-2 (35K-250K
users with up to 250
BSM’s and 12SM’s)
6 2290 MHz 12GB 105GB 13740 12288
Profile-3 SMGR High
Capacity (35K-250K
users with up to 500
BSM’s and 28SM’s
8 2290 MHz 18GB
250GB 18320
18432
© 2016 Avaya Inc. All right reserved 56
AVAYA AURA 7 BROWSERS TESTED AND
SUPPORTED
Avaya Aura Application Internet Explorer Supported Fire Fox Supported
Session Manager 7.0 (SM) IE 9, 10 and 11 FF 37, 38 and 39
Branch Session Manager 7.0 (BSM) IE 9, 10 and 11 FF 37, 38 and 39
System Manager 7.0 (SMGR) IE 9, 10 and 11 FF 37, 38 and 39
Application Enablement Service 7.0
(AES)
IE 9, 10 and 11 FF 18 and later
Utility Services 7.0 (US) IE 10 and 11 FF 38 and 39
Communications Manager 7.0 (CM) via SMGR - IE 9, 10 and 11
via Local CM EM (SMI) - IE 10 and 11
via SMGR - FF 37, 38 and 39
via Local CM EM (SMI) - FF 38 and 39
CM Messaging 7.0 (CMM) IE 10 and 11 FF 38 and 39
Engagement Development Platform 3.1
(EDP) (including Presence)
IE 9, 10 and 11 FF 37, 38 and 39
Avaya Aura®
Media Server 7.0 (AAMS) IE 9, 10 and 11 via SMGR - FF 37, 38 and 39
via Local AAMS EM - FF 37, 38 and 39
WebLM 7.0 IE 9, 10 and 11 FF 37, 38 and 39
© 2016 Avaya Inc. All right reserved 57
SYSTEM MANAGER 7.0 CAPACITIES
Capacities SMGR 7.0
Number of administrator logins 250
Number of simultaneous logins 50
Number of Total administered endpoints 250,000
Number of Total administered Users defined in System
Manager database 250,000
Number of messaging mailboxes 250,000
Number of contacts per user 250
Number of public contacts 1,000
Number of personal contact lists, per user 1
Number of members in a personal contact list 250
Number of groups 300
Number of members in a group 400
Number of elements 25,000
Number of Communication Managers and/or CS1000s 500
Number of Session Managers 28*
Number of Branch Session Managers 500**
Number of IP Offices 2,000
Number of IP Office Unified Communication Module (UCM)
or Application servers as part of Branch Deployments 2,000
Number of roles 200
Number of roles, per user 20
Number of licensing clients 1,000
Number of trust management clients 2,500
Number of Tenants (SMGR Multi-tenant) 250
* Increased capacity in AA7 ** Move from 250 to 500 Supported on SMGR 7.0.1 (FP1)
This table includes supported maximum capacities for each individual element type. Since there is only one System Manager per Avaya Aura® deployment, it’s essential to understand that the solution number is not a summation of all the supported Elements listed in the Table.
Please reference the Avaya Aura 7 Offer Definition posted on the Sales Portal or the System Manager Overview documented posed on the Avaya support portal for further details
© 2016 Avaya Inc. All right reserved 58
UPGRADE-MIGRATIONS TO SMGR 7.0
System Manager 6.x (Standalone Template – System Platform Appliance
Offer) to System Manager 7.0 on Appliance Virtualization Platform (AVP)
High-level View of Workflow:
1. System Manager Backup and Complete System Platform Backup ( disaster recovery)
2. Record SMGR 6.x Application Network Settings (All IP Address’, Mask, GW, DNS, NTP Server)
3. Load Solution Deployment Manager Client on Technicians PC to perform SMGR 7.0 Deployment
4. Download AVP Utility Service 7.0 and System Manager 7.0 OVA to Technicians PC
5. Install AVP to the existing CSR1 or CSR2 Server
6. Connect Technician’s PC to AVP
7. Using the SDM-Client, Create a Location – Host – VM in the VM Management Section
8. Deploy Utility Services OVA (set application footprint profile size)
9. Enter SMGR details in SDM Client and use SDM Client to migrate SMGR by providing the backup.
This will internally deploy OVA and perform data migration.
10. Install the Avaya Secure Gateway (ASG) File for each application OVA installed and the AVP. (AVP,
Utility Services and SMGR)
© 2016 Avaya Inc. All right reserved 59
UPGRADE-MIGRATIONS TO SMGR 7.0 (CONT’D)
System Manager 6.3.x with latest Service Pack on Virtualized Environment
(Customer Provided VMware ESXi on certified VMware Servers )
High-level View of Workflow:
1. Perform a backup of the existing System Manager 6.3.x via SMGR Console. Once complete,
shutdown the Virtual Machine (VM).
2. Record SMGR 6.3.x Application Network Settings (All IP Address’, Mask, GW, DNS, NTP
Server)
3. Download the System Manager 7.0 OVA
4. Shutdown the existing SMGR 6.3.x Virtual Machine (VM)
5. Deploy the System Manager 7.0 OVA into the VMware ESXi Environment ( 5.0, 5.1 or 5.5)
using vSphere or vCenter. The same IP address, hostname and network parameters as the old
SMGR VM must be used. The Solution Deployment Manager -Client can also be used to
deploy the OVA
6. Use data migration utility to migrate the System Manager 6.x backup to the new System
Manager 7.0 virtual machine
7. Test application for functional sanity
© 2016 Avaya Inc. All right reserved 60
SMGR SOFTWARE MANAGEMENT – FEATURE
TIMELINE
SMGR 6.2 - Initial Software Management functionality introduced to support upgrades to B5800 and IP Office
SMGR 6.3.2 (FP2 May - 2013) – Full port of the Network Management – Software Update Manager (SUM) application to System Manager was completed.
SMGR 6.3.8 (FP4 - June 2014) – Enhancements to support and automate CM 6.x to CM 6.3.6 was added along with other workflow enhancements such as job chaining/sequencing and pre-upgrade checks
SMGR 7.0 (August 2015) – Further evolution and consolidation of the software management tools to form the Solution Deployment Manager (SDM) that is part of System Manager