Skype For Business Server 2015 Step by Step For Anyone - Installing and Upgrading - REV - 05

What is New in Avaya
Aura® 7.0
© 2015 Avaya Inc. All rights reserved.

Welcome!
 Welcome to the What is New in Avaya Aura® 7.0 course!
 Intended Audience – The content provided in this course is intended for
all audiences interested in the new features and functionalities introduced
in Avaya Aura® release 7.0.
 Course Length – Approximately 3 hours

Course Objectives
Upon completion of this course, you should be able to:
 Describe how the Avaya Aura platform provides the foundation
for business collaboration.
 List key benefits to Avaya Aura 7.0.
 Identify the products and applications included in Avaya Aura
7.0.
 Describe the key features introduced with Avaya Aura 7.0.
 Identify the Avaya Aura 7.0 hardware requirements for specific
servers and deployments.
 Describe Appliance Virtualization Platform.
 List the features and functionalities of the Utility Server in Avaya
Aura 7.0.
 Describe Solution Deployment Manager and it role in an Avaya
Aura 7.0 deployment.
 List key features of Solution Deployment Manager.

Course Objectives continued
Upon completion of this course, you should be able to:
 Describe Out of Band Management and how it is used in Avaya
Aura® 7.0.
 List common upgrade and migration scenarios from previous
releases to Avaya Aura® 7.0.
 Identify supported and unsupported migrations to Avaya Aura
7.0.

Agenda
Module Time (minutes)
Overview 30
Hardware 30
** Break ** 10
Appliance Virtualization Platform 30
Solution Deployment Manager 30
** Break ** 10
Out of Band Management 30
Upgrade and Migration to Avaya Aura 7.0 30
Note:
• Times are approximate give or take discussions, questions and answers.

Avaya Aura® 7.0 What is New Course Tests
Course/Course Number Test Length
What is New in Avaya Aura® 7.0 (2007V or W) No -
Migrating and Upgrading to Avaya Aura® Platform 7.0 (2012V) No -
What is New in Avaya Aura® Application Enablement Services 7.0 (2008V or W) Yes; (2008T) 30 minutes
What is New in Avaya Aura® Communication Manager 7.0 (2009V or W) Yes; (2009T) 60 minutes
What is New in Avaya Aura® Presence Services 7.0 (2010V or W) Yes; (2010T) 30 minutes
What is New in Avaya Aura® System Manager 7.0 and Avaya Aura® Session Manager Yes; (2011T) 60 minutes
7.0 (2011V or W)
Note:
• Recommended to take What is New in Avaya Aura® 7.0 or Migrating and Upgrading to Avaya Aura®
Platform 7.0 course and product specific course before taking the assessment.
• Each product-level assessment includes questions from the What is New in Avaya Aura® 7.0
course.
• Login to www.avaya-learning.com to take the respective test.
• V= Virtual Instructor-Led, W= Web-based Training (recorded session), T= Test

Certification - ACIS/ACSS
Note:
Solution courses and certification exam availability:
• ACIS Certification – 2Q/2016
• ACSS Certification – 3Q/2016

Overview

Avaya Aura® 7.0
Major Release! Flexible Footprint
Secure Mobile 250K SIP Users

Collaboration 350K Devices
End-To-End
AES 256 bit Solution Deployment Manager Encryption
encryption Indicator
S8300E
End user encryption
indicator Avaya Aura Media Server with CM
PS on EDP
Improved Full virtualization on Avaya or Out of Band

certificate Customer Supplied Servers Management
management
Appliance Virtualization EDP Call Intercept Applications for

Platform enterprises that use AES application
Foundation for Business Collaboration
Conferencing • Simplified deployment of multimedia

collaboration applications
Video Communications
Enablement • Single user experience across
Click
headquarters, branch and on the go
security to
Talk
• Dynamic allocation of bandwidth

Session
Telephony Management across the enterprise
• Intuitive, cross-enterprise
management
• Multilayer security from core to end
System points
Instant Management
Messaging
• Complete Redundancy and
Virtualization options
• Scalable to 350,000 Endpoints
Presence
• Integration into business applications
and processes

Avaya Aura® 7.0 Themes and Key Features
Security Media Server Call Center Enablement
Virtualization
Other Feature Enhancements
Supportability
Management Simplification
Scalability

The Avaya Aura® Platform

Third party logos belong to the respective owners. Avaya is not an owner or licensee of the same.
Included in Avaya Aura® 7.0
Product/Application Release
Avaya Aura® Session Manager (SM) 7.0
Avaya Aura® Communication Manager (CM) 7.0
Avaya Aura® Branch Gateways (BGW) 7.0
Avaya Aura® Presence Services (PS) 7.0

(Snap-in on Engagement Development Platform)
Avaya Aura® System Manager (SMGR) 7.0

(Including Solution Deployment Manager)
Avaya Aura® Utility Services (US) 7.0
Avaya Aura® Application Enablement Services (AES) 7.0
Avaya Aura® Appliance Virtualization Platform (AVP) 7.0
Avaya Aura ® Media Server 7.7
Avaya WebLM 7.0

Why Upgrade to Avaya Aura® 7.0?
 Avaya Aura® Media Server enables massive footprint reduction
and new capabilities.
 Ability to grow beyond the Midsize Enterprise boundaries, and
create fit for purpose configurations.
 Reduced server hardware footprint requirement for
modernization with Virtual Appliance.
 Ability to separate management and non-management network
traffic.
 Innovate with Presence Services as a Snap-in on the
Engagement Development Platform
 Reduced TCO with a single, centralized management tool to
deploy Avaya Aura® applications, and deliver feature/service
packs.
 A simpler way to keep Avaya Aura® solution current.
 Support for users with multiple SIP devices at full solution scale
for mobility and device choice.
 + Additional Security and Supportability Improvements.
 ++ Numerous other Feature Enhancements.
Key Applications and Features
 Avaya Aura® Media Server
 Virtualization in the Appliance Model
 Virtualized Environment Updates
 Midsize Enterprise Evolution
 Solution Management
 Communication Manager/Session Manager
 Presence Services
 Application Enablement Services
 Security
 Scalability
Note:
This Overview module describes the high level features in Avaya Aura® 7.0
Details for these key features are discussed in detail in other learning modules.

Massive Footprint Reduction
 Avaya Aura® Media Server Adoption by Communication Manager
From
TO 1 Server (dedicated)
up to 4000 AAMS channels
13 G450 Gateways, 4160 channels: 39U rack space

CM 7.0 with Avaya Aura® Media Server
 Avaya Aura® Media Server (AAMS) 7.7 – Media source for Avaya Aura®
Communication Manager 7.0.
 Software-based media server – AAMS provides soft DSP/media channel
resources on general-purpose hardware, with multiple deployment options.
 Customer Benefits:
• Add to your existing G650 and G450 DSP resources utilizing smaller footprint.
• Possible to replace your existing G650/G450 DSP resources, resulting in potentially
massive reduction in hardware footprint.
• Same voice announcements can be deployed to AAMS that are already centrally deployed
to CM-VAL boards, using the SMGR hosted VAL Management functionality.
• Optimization of Call Center resources – reduced costs for call recording by reducing
gateway footprint.
• AAMS provides features not offered by Media Gateways and Port Networks:
– Virtualization
– High channel density
– No playback announcement limits
– Additional codecs.

Communication Manager with AAMS Use Cases
 Communication Manager with AAMS best fit for:
– Call center requiring lots of DSP resources for call recording, announcements
or IVR applications (digit collection)
– Customers with MCC or G650 cabinets looking to reduce their footprint as they
upgrade and transition to IP.
– All IP construct (H.323 or SIP endpoints) with high DSP/media channel
requirements.
 Communication Manager with Gateways best fit:
– Not ready for all IP – Still require TDM and T.38 fax.
– Customers with existing G450s who want to keep their investment but may add
AAMS if doing a major addition.

Midsize Enterprise (ME) - Evolution
ME Release 6
Pre-Packaged
Template Offer As ME customer’s business
ME Value Proposition evolve there have been some
System Manager challenges with the ME template
 Solution focused for boundaries:
Midsize Enterprise Session Manager
Communication  Scale ceilings
 Lightweight footprint Manager 2400 users
with multiple CMM 1000 CC Elite
applications AES
 FRHA (interrupted – 10+
 Pre-installed for Presence Services minutes depending on
deployment Utility Services scenario)
simplification No Geo-Redundancy
Xen Hypervisor Dom0
 Pre-defined application set
 Off board application servers
like AES and SM are not
supported

ME Upgrade & Migration to Avaya Aura® 7.0
 Applications split into individual product

applications.
ME upgrades/migrates  ME CSR1/2 server platform can be re-
ME Release 6 to Aura® 7 used.
Pre-Packaged applications with
Template Offer Flexible Footprint  Configuration Data maintained.
System Manager
System Manager
Session Manager ME systems upgraded to
Session Manager Avaya Aura® R 7.0
Communication Benefit with Flexibility*:
Communication Manager
Manager
CMM CMM  Grow beyond 2400 users/ 1000 CC Elite
Agents.
AES Presence Services
 Application level Resiliency options /
Presence Services Geo Redundancy.
AES
 Leverage off board servers like AES and
Utility Services
Utility Services SM.
Xen Hypervisor Dom0 AVP – VMware Hypervisor  Re-deploy for application segmentation
& choice.
 Full Avaya Aura® roadmap alignment.
* May require additional servers for capacity and
deployment options
ME CSR1/2 can be reused

Security Enhancements
 TLS Secured Gateway Links
– Extend the TLS support that protects the control link between CM and media gateway
– All trunk links between CM and AAMS are supported with TLS.
 AES 256 bit encryption
– AES is a symmetric encryption algorithm (same key used for both encryption and decryption of the
data stream).
– To ensure support for customer demands for stronger security, Avaya Aura® 7.0 will offer AES-256
(with 256 bit length as the key) for audio/video/data bearer streams.
 Improved Certificate Management (SMGR)
– Certificate Authority Generation Utility in SMGR
– Include SRVname option in certificate SubjectAltName field
– Remove Obsolete Certificates
– Auto Renew Certificates
 Improved Certificate Management (Gateways)
– Support of SHA2-signed certificates for firmware image files that are downloaded to G430/G450
gateways.
– Support of the Online Certificate Status Protocol (OCSP) as an alternative technique to CRL
Revocation Lists. Allows customer to treat gateways in the same class as phones
– Support of the “Time Zone Enhancement” to support certificate expiration. Note that certificates are
build with an certificate expiration that is expressed in Greenwich Mean Time (GMT).
 End to end encryption indicator
– SIP end-points and clients to display an indicator that tells the end user whether the signaling and the
media is end-to-end secure. The initial offer will only support SIP endpoint/clients on intra-enterprise
point to point calls.

Scalability
 Increased SIP Capacity to support 250K SIP Users and 350K SIP Devices:
– Avaya Aura® Core supports 250K SIP Users and 350K SIP devices.
– Add up to 28 Session Managers (up from 12) to grow their networks to up to 250k SIP
users/350k SIP devices.
 Increased Number of Domain Control Associations in AES:

– Increase the maximum number of Domain Control associations from the current limit of 4 to 8
with AE Services 7.0.
 Increased Number of Device Media and Call Control (DMCC) Registrations in AE
Services:
– Increase the maximum DMCC instances from 4000 to 8000 in AE Services 7.0.

CM and Branch Gateway Enhancements
 Single Button Press for Call Park Pickup (CM):
– With Release 7.0, Call Park can be configured to allow parked calls to be picked up with the press of a
single button, streamlining call management in closely aligned work groups..
 Triple tone for call pickup on H.323 Devices (CM):
– When a call is made to a member of a call pickup group, and the call is not answered after 15
seconds, Release 7.0 customers can now administer a triple tone to be sent in order to improve the
response rate of call pickup group members to incoming calls.
 Support for “+” Digit on Call Type Analysis (CTA) Form:
– By recognizing the + digit, the CTA from can transform the + digit to the correct international access
code such as 011 in North America or 00 in EMEA.
 SNMP Engine for CM:
– CM will have a new Master Agent based on NET-SNMP which is included in the Red Hat Linux
distribution, a new set of subagents, and will define a new CM-MIB.
– There will now be separate object IDs for each CM Maintenance object for the Major Alarm, Minor
Alarm, Warning, and Resolved.
 Alarming Individual DSP Core Failures (BGW):
– With Avaya Aura® 7.0 Branch Gateways will now generate alarm when any of the four DSP cores on
the DSP board is out of service.

Session Manager Enhancements
 Automatic Alarm Clearing for Session Manager Alarms:
– With Avaya Aura® 7.0, when an alarm is cleared in Session Manager there will now be a notification
sent out via SNMP that it was cleared, removing the need to manually clear the alarm on systems
monitoring the SM.
 Avaya Aura® Session Manager SIP Message Compaction :
– Before forwarding a SIP message, as part of the Adaptation Module processing, SM will remove the
headers and parameters that are either Avaya proprietary or deemed excessive/unnecessary for non-
Avaya elements.
– This improves the solution interoperability.
 Emergency Call Adjunct Interface Update for MDA:

– With the introduction of MDA (Multiple Device Access), a single user can register from multiple
devices. With SM 7.0, the existing SM AELS (Adjunct Emergency Location Server) interface has been
enhanced to provide the device used by the user so more accurate location information can be
determined.
 Avaya Aura® Session Manager Lync Integration Enhancements:
– Previously, for Lync integration, the administrator had to enter or administer the Presence handle of an
Avaya Aura® user twice: once as the Avaya Presence/IM (formerly XMPP) handle and the second
time as the Avaya Aura® SIP handle. The duplicate administration was required for proper routing of
the Lync originated subscription and IM requests.
– Starting with this release, the Presence Services handle only needs to be administered once.

Presence Services 7.0 moving to EDP 3.1
 Leveraging the EDP Platform, Presence Services is able to provide the
current PS capabilities plus increased capacity and redundancy options.
 Allows for rapid application development in a robust, scalable
environment which improves time-to-market by extending the Presence
and Instant Messaging capabilities to 3rd-party developers through the
EDP environment.
Presence Services
(Snap-in)
Engagement Development Platform
Appliance Virtualization Platform
Avaya Common Server

Application Enablement Services High Availability
 High Availability Support:
– System Platform no longer supported in AES 7.0.
– Since Fast Reboot HA (FRHA) and Machine Preserving HA (MPHA) are
provided by System Platform, these options will not be supported in AES 7.0.
– In AES 7.0, the Geographic Redundant HA feature will now provide FRHA
equivalence:
• Simplified offer
• License enforceable
• Two AES GRHA servers can be co-located to emulate FRHA or
geographically separate (No dedicated link, data sharing over the
LAN/WAN)
– AES 6.3.3 available for MPHA customers.

Hardware

Avaya Aura® Release 7.0 Hardware

Avaya Common Server R1 Specifications
 Existing servers in the field:
Component HP ProLiant DL360 G7 Dell PowerEdge R610
Form factor 1U 1U
Processor family Intel Xeon 5600 Series – E5620 Intel Xeon 5600 Series – E5620
Number of processors 2 2
Memory type 2 GB DDR3 RDIMM 2 GB DDR3 DIMM
Total memory 12 GB 12 GB
Hard Disk Drive 300 GB 146 GB
Number of Hard Disk Drive 3 3
RAID Level 1 5
Network interface 4 4
Optical drive DVD +/- RW, SATA DVD +/- RW, SATA
Power supply 460 Watts AC 502 Watts AC
Number of power supplies 2 2

Avaya Common Server R2 Specifications
 Existing servers in the field:
Component HP ProLiant DL360 PG8 Dell Power Edge R620
Form factor 1U 1U
Processor family Intel (2.3 GHz - E5-2630) Intel (2.3 GHz - E5-2630)
Number of processors 2 2
Memory type 4 GB RDIMM 4 GB RDIMM
Total memory 32GB 32GB
Hard Disk Drive 300GB Drives 300GB Drives
Number of Hard Disk Drive 2 2
RAID Level 1 1
Network interface 4 4
Optical drive DVD+/-RW, SATA, INTERNAL DVD+/-RW, SATA, INTERNAL
Power supply 495W 495W
Number of power supplies 2 2

S8300E Server
 Next version of the S8300 server blades.
 Based on a 2.0 GHz, Dual Core, 22nm Intel Ivy Bridge processor.
 Highlights :
• Runs System Platform and VMware Appliance Virtualization Platform.
• Supports G430 Branch Gateway and G450 Media Gateway.
• Supports VMware hypervisor ESXi 5.x and is certified by VMware as VMware Ready.
• Supports Communication Manager Release 6.3.8+.
• Same functionality as the S8300D server but higher performance and memory footprint.

S8300E Server Continued
 Improvements over S8300D:
• More powerful, next generation, dual core processor (Intel Dual Core 2.0 GHz Ivy Bridge
processor).
• Increased maximum DRAM memory capacity of 16 GB. Initial configuration ships with 16 GB (the
S8300D ships with 8GB which is its maximum capacity).
• Next generation DDR3 SDRAM memory technology (faster than DDR2 and lower cost at the
higher densities).
 Running Communication Manager - Supports CM 6.2 FP4 and CM 7.0+:
• Not required to support earlier releases of CM; Not required to support RAMDISK or a Solid State
Drive.
• Slot V1 of Gateway.
 Maintenance - Same maintenance architecture as the S8300D.

 Redundancy – Same redundancy architecture as the S8300D. Runs Communication
Manager as:
• Main Internal Communications Controller (ICC).
• Survivable Remote (formerly, LSP).
• As an ICC, supports a standalone system, while the Survivable Remote function is more typical of
a remote edge system of a larger enterprise.
 Performance - Same or better performance (BHCC) when compared with the S8300D
server.

S8300E Server Specifications
Component Minimum Specifications
Processor • 2.0 GHz, Dual Core, 22nm Intel® Ivy Bridge
Memory • 320 GB hard disk
• 16 GB DDR 3 SDRAM
Connectors • Ethernet LAN (future use)
• Services Port with link status and activity LEDs
• USB 2.0 ports (3)
• USB DVD drive
Flash Drive • Not supported
Note:
Internal Solid State Drive (SSD) is not supported by S8300E server.

S8300E Server High-level Capacities
Capability S8300E Server
Call processing feature set • Communication Manager Release 6.3.8 and later.
Maximum number of stations • Communication Manager Release 6.3.x supports:

• 1000 H.323 stations
• 700 SIP stations for LSP
• 700 SIP stations for Branch Session Manager
Maximum number of trunks • 450
Reliability options • Single Server
Port-network connectivity • N/A
Supported gateways • G430 Branch Gateway

• G450 Branch Gateway
Maximum number of supported gateways • 50
Survivability options • G430 Branch Gateway

• G450 Branch Gateway
Number of Survivable Remote Servers in one • 50

configuration
Port Networks • N/A

S8300E Faceplate
– LED functions same as S8300D:
• Alarm
• Application up
• Active
• OK-to-Remove
– Shut Down button.
– Ethernet LAN port (future use).
– Services Ethernet port with link status and activity LEDs.
– Three USB 2.0 ports.

S8300E server LEDs description
LED Color Description

ALM Red • ON when power is turned on or when a major alarm is present.
APP Green • ON when Communication Manager is running or a test is in progress.
ACT Yellow • ON when a gateway, an IP station, or an IP console registers with the
S8300E.
OK to Remove Green • Flashes when shutdown is in progress.
• ON when shutdown complete and you can remove the S8300E server.
Compact Flash Yellow • On when compact flash is in use.
Ethernet Port Green • ON when the data rate is 10 MB or 100 MB
Yellow
Services Port Green • Flashes when data is being transmitted or received over the Ethernet
link.

S8300D vs. S8300E Comparison Summary
FEATURE S8300D S8300E NOTES
Processor 1.06 GHz Dual Core U7500 2.0 GHz Dual Core Ivy Bridge Higher CPU performance.
L2 cache 2 MB 512 KB Included in the processor chip.
L3 cache None 4 MB L3 cache provides higher performance
Chipset 3100 MICH Cave Creek PCH New higher performance platform
Type of memory DDR2 SDRAM DDR3 SDRAM DDR3 memory is faster than DDR2, provides a
longer life cycle, and a lower cost at the higher
densities.
Maximum memory supported 8 GB 16 GB Boards ship with 16 GB of DRAM installed

by the design
Type of memory socket Single RDIMM Two DDR3 SODIMM VLP DIMMs are required to fit within a single
MM slot
Internal SSD 8 GB Not supported Avaya’s System Platform no longer uses the
SSD that ships with the S8300D. The S8300D
support the installed base requiring the SSD.
Hard drive 250 GB Serial ATA 320 GB Serial ATA Enterprise class required.
Faceplate Ethernet ports One for Services Two ports, one for Services and The second faceplate port is planned for out of
one for future use band management but could have other uses.
USB ports Three USB 1.1/2.0 Three USB 1.1/2.0
USB DVD drive Supported Supported

USB Compact Flash reader for External USB CF reader External USB CF reader NOT
backups supported. supported.

S8300E Installation, Upgrade, and Migration
 Communication Manager Server:
• Supports the external CD/DVD-ROM connected to one of the USB ports for
installation and upgrade purposes.
• The only supported USB DVD drive is the Digistor DIG73322 (comcode 700406267).
A new version of this drive may be available in the future.
 Migrations to S8300E:
• Process the same as S8300 (A, B, and C) to S8300D.
• Migrate S8300 (A, B, C and D) to S8300E.
 Migration workflow to the S8300E:

• Backup translation data from the S8300 (A, B, C, and D) server.
• Swap out the S8300A/B/C/D serve with the S8300E server.
• Install CM 6.2 FP4 or CM 7.0 on the new S8300E server.
• Restore translation data on the S8300E.
 Appliance Virtualization Platform – Supports Headless Install. New

S8300E servers will have AVP installed in the field.

S8300E in CM and Media Gateway
 S8300 in CM and media-gateway SAT.

Appliance Virtualization
Platform

Avaya Aura® 7.0 Virtualization Options
Virtual Appliance
Avaya Supplied Server, Avaya
Supplied VMware® (AVP)
Virtualized
Environment
Customer Supplied
VMware® and Servers
Collaboration Pod
Avaya Supplied VMware®,
Servers, networking, storage
pre-installed applications

Avaya Aura® 6.x to Avaya Aura® 7.0
Common Utility
Services App A App B SMGR SM
(Cdom) Services
Xen Server (Dom0) Appliance Virtualization Platform
Avaya Supplied Server Avaya Supplied Server
Release 6.x Release 7.0
 System Platform – Release 6.x  Appliance Virtualization Platform – Release 7.0

– Fixed templates. – Fixed Templates replaced with customer selected
applications
– Limited virtualization
– Functionality provided by CDOM in system
– Included per server management capabilities in platform will now be provided a centrally located
CDOM System Manager.
Note:
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.
Keys to Avaya Aura® 7.0 Solution
 Appliance Virtualization Platform – Customized OEM version of VMware®
hypervisor (ESXi 5.5) to support Avaya Supplied Servers:
– All existing System Platform offers will migrate to AVP in Avaya Aura® 7.0. Session
Manager will also move to an AVP based offer.
– AVP management will be via Avaya tools (System Manager)
– vCenter is not provided or supported in 7.0 appliance offer
 Avaya Aura® Applications - Existing VMware OVAs enable us to virtualize
several applications on a single server:
– Enables a reduced footprint for the Avaya Aura® solution.
– Lower barrier for existing customers upgrading to the current release – particular those
on older releases.
 Flexible Footprint – No pre-defined templates restrictions.
– Customers are free to run any combination of supported applications on Avaya servers
provided the server has sufficient resources
 Avaya Supplied Servers - Ongoing support for foundational hardware:
– Avaya Common Servers (CSR1, CSR2)
– Collaboration Pod Servers
– S8300D and S8300E Embedded Servers

Avaya Aura 7.0 Model Comparison
 Appliance Model:  Virtualized Environment Model:
– Avaya Supplied Servers – Uses customer-provided Virtualization
Environment.
– Appliance Virtualization Platform
(ESXi 5.5). – Avaya Aura® applications (OVAs) are
deployed using System
– Avaya Aura® applications (OVAs)
Manager/Solution Deployment
are deployed using System
Manager, vCenter.
Manager/Solution Deployment
Manager.
SDM SMGR
Utility
Server App App
SDM
Appliance Virtualization Platform SMGR App
Avaya Supplied Server Customer Virtualization Environment

Flexible Virtualization in the Appliance Model
 Flexible virtualization of Avaya Aura® Applications per customer
requirements.
 Data Center: single application per server for massive scale.
SM
High Capacity - Single Application Appliance
 Branch Office: flexible deployment of applications on single server for tiny

h/w footprint.
LSP BSM AES AAMS
Branch Office solution: with Avaya Aura Media Server – no gateway required!

Appliance Model Mapping
Avaya Aura® 6 System Appliance Virtualization

Platform/cDOM Platform
• Xen Hypervisor • VMware Hypervisor

• LDAP authentication for VMs • Application responsible for authentication
• System Platform HA • Application HA
• Services Port • Services Port VM
• Softswitch (bridges) • vSwitch
• NIC bonding • VMware hypervisor NIC bonding
• Hardware alarms • VMware hypervisor Hardware alarms
• Heratbeat to CDOM • NA
• ASG • VMware hypervisor ASG customization
• CPLD – server drivers • VMware hypervisor CPLD for embedded servers
• System Platform deployed via DVD • VMware hypervisor to be deployed via DVD
• SP Patching • SDM to support patching of VMware hypervisor
• Backup/Restore • Manual per application
Applications supported in initial release

SMGR, SM, BSM, AES, US, CM, WebLM, EDP, CMM, AAMS, PS (On EDP), ADS/SAL

Availability Features in the Appliance Model
Application Avaya Aura® 6.2 Feature Pack 4 Avaya Aura® 7 Availability Features
Availability Features
Communication • Software Duplication for Local transparent • Software Duplication for Local transparent
Manager instantaneous Failover instantaneous Failover
• Survivable Core for Geo Redundancy • Survivable Core for Geo Redundancy
Session Manager • Active-Active clustering, • Active-Active clustering,

• N+M routing • N+M routing
System Manager • System Manager High Availability (based • SMGR HA Not supported in 7.0
on System Platform FRHA)*
• System Manager Geo Redundancy
• System Manager Geo Redundancy
Presence • N+1 Active Standby • N+1 Active/Active High Availability.
AES • AES HA (based on System Platform FRHA) • Equivalent functionality available from AES
* Geographic Redundancy
• AES MPHA (based on System Platform)* • AES MPHA not supported in 7.0
• AES Geographic Redundancy • AES Geographic Redundancy
Midsize Enterprise • Platform Level HA supported (System • FRHA not supported in 7.0
Platform FRHA) + Application level availability features are
• Application level availability features are supported (similar to VE configuration)
NOT supported

Utility Server Features and Operational Modes
 Features:
• MyPhone
• DHCP Server
• TFTP Server
• HTTP Server
• Administration Tools
 Utility Server Modes – Selection of mode only
available at time of deployment. Redeploy Utility
Server change the mode of operation:
• Services Port plus Utility Services Mode
• Utility Services Only Mode
• Service Port Only
 Third-party Certificates - Supports IP phone

firmware downloads. Utility Services supports the
loading and use of third party certificates to establish
a trust relationship with IP endpoints also supporting
third party certificates.
 Utility Services will no longer bundle the IP phone
firmware within the build. Administrators are required
to download the latest version from PLDS and place it
upon Utility Services.

Utility Server
 Required on all Application Model (AVP- Host
servers) offers.
 Utility Server must be installed as the first
Avaya Aura® application after the AVP
installation.
 Replaces Console Domain (Cdom):
• Runs Services Port connection that was
available on System Platform.
• Allows connection of PC directly to Eth1 on
AVP Host Server.
• Allows laptop connection to the applications
management interface that resides on host
server.
• Supports ASG logins and the loading of
customer ASG files onto the system. A
generic ASG file is included on the system by
default.
 Enables:
• Routing capability from the Service Port
(Eth1) to the Virtual Machines.
• Alarm Conversion

Utility Server and AVP Networking
 Accessing Management Interfaces:
• Service Port – Routing function is moved into the Utility Services (Service Port VM)
using IP address: 192.11.13.6/29.
• AVP Management Port:
> Port 2 provides the management interface to the ESXi hypervisor.
> Associated with the Services Port (physical Eth1).
> Assigned IP address: 192.168.13.6/29.
Utility Services
(Service Port VM)
192.11.13.6/30
(Eth1)
192.168.13.6/29
Appliance Virtualization Platform (Eth1)
(ESXi Hypervisor)

Utility Server and AVP Network Connections
Utility Services
Eth0 Eth1
(Service Port VM)
192.11.13.6/30

Eth0 (ESXi Hypervisor) Eth1
Public vSwitch Management - Port 1 Management - Port 2 Service port vSwitch
192.168.13.6/29
Avaya Provided Server
Eth0 (Physical) Eth1 (Physical)

Avaya Aura® Applications Supported on AVP
Avaya Aura® System Manager (SMGR) Avaya Aura® Application Enablement Service (AES)
Avaya Aura® Session Manager (SM) Branch Session Manager (BSM)
Avaya Aura® Communications Manager (CM) Avaya Aura® Communication Manager Messaging
(including CC Elite) (CMM)
Avaya Aura® Utility Services (US) Avaya Aura® Media Server (AAMS)
Engagement Development Platform (EDP) Avaya Aura® Presence Services (AAPS on EDP)
Avaya WebLM ADS/SAL

AVP Headless Installation- Key Components
No requirement for Keyboard and Mouse in AVP installation. © 2015 Avaya Inc. All rights reserved.
AVP Installation File Generator Tool
1

AVP Installation File Generator Tool continued
Welcome to the Avaya Appliance Virtualization Platform configuration file generator.

This spreadsheet will generate a ks.cfg file to be used on the USB key when installing AVP. Please
enter the values in the above fields (column B) and then press the grey box generate button
(column C).
4 Save the file onto a USB key. Insert the AVP installation CD into the server and insert the USB
key into the server.
WARNING - Once the server reboots AVP will be installed, all existing data on the server will be
lost.
5 Reboot the server, wait up to 30 minutes and then connect to either eth1 with 192.168.13.5 to
connect to 192.168.13.6 or if server is connected to the main network connect to the public IP
address detailed in the file.
If using a monitor, the screen will change to black before the installation is complete. This is
expected and no action should be taken.
AVP- Appliance Virtualization Platform

SDM - Solution Deployment Manager
OOBM - Out of Band Management

Attribute Value (default) Notes
• Host Public IP Address – Customer Network IP address or Avaya
AVP Management IP address 10.10.10.1 Virtualization Platform Host.
• Format: x.x.x.x
• Host Netmask – Customer subnet mask for the Appliance Virtualization
AVP Netmask 255.255.255.0 Platform host.
• Format is x.x.x.x
• Host Gateway IP address - IP address of the customer default
gateway on the network. Should be on the same network as the Host IP
AVP gateway IP address 10.10.10.254 address.
• Format is x.x.x.x
• Hostname - Hostname for the Appliance Virtualization Platform host.

AVP Hostname AVPserver
• Should be an alphanumeric string.
• Domain - Domain for the host. If no host is provided by the customer
please use the default.
AVP Domain avpdomain.com • Format is alphanumeric string dot separated.
• Example mydomain.com
• NTP server IP address - IP address of customer NTP server.

NTP server 10.10.10.50 • Format x.x.x.x.
• One NTP server entry only.
• Customer DNS server IP address - IP address of customer DNS
server.
DNS server 10.10.10.60 • Format is x.x.x.x.
• One DNS server entry only.
• LAN ID for S8300D and S8300E - VLAN ID for the S8300D and
S8300E.
Public VLAN ID • If the customer is not using VLANs leave as 1.
1
(Used on S8300D and S8300E only) • For any other server type leave as 1.
• Range is 1 – 4095.

Attribute Value (default) Notes
• Out of Band Management - Install AVP with Out of Band

• Management setup.
• Management port will be connected to Eth2 of the server and
applications will be expected to deploy in Out of Band Management
Yes modes.
Out of Band Management Setup
No (default) • Only select yes if you intend to use Out of Band Management setup.
• VLAN ID for OOBM - Out of Band Management VLAN for S8300D.

• For S8300E use front plate port for OOBM.
• For common server use Eth2 for OOBM.
OOBM VLAN ID • If using OOBM please consult the documentation for more details.
1 • Requires latest G430 / G450 firmware for OOBM with S8300D.
(Used on S8300D only)
• Root password for the system - Root password for the Appliance
Virtualization Platform.
• This field is hidden. Make a note of the password as it will be required
for addition to System Manager.
• Password should be 8 characters long, with a mix of lower case, upper
case and numbers.
AVP user root Password
(blank) • This password is required for registration with System Manager and
(hidden field)
SDM client.

Format USB Flash Drive Procedure
 Insert USB Flash drive into Microsoft Windows® desktop.
• Select Start – Run – CMD.

AVP Headless Install
 AVP Headless Install for Avaya Supplied Servers:

• Insert Appliance Virtualization Platform (AVP) DVD.
• Insert USB Flash Drive with KS.CFG file.
• Reboot server.
• AVP installs and ejects DVD.
• Remove DVD and USB stick from the server (critical for HP servers).
• Ping server IP(s) from desktop to verify network connectivity.
• Deploy Virtual Machines using Solution Deployment Manager.
• Login to Virtual Machine and accept EULA to process the licensing.
• Patch Virtual Machines.

Live Demo
 Configure AVP Installation File Generator Tool.
 Generate ks.cfg file.

High Level Migration Process to AVP
Planning
• Verify existing 6.3 System Platform, Templates, Patches install media, files, and
recovery CD is available.
• Have on-hand: AVP and US software, USB (FAT 32 formatted), ks.cfg file, and 7.0
Virtual Machine components.
Pre-Installation
• Backup System Platform and save backups to external media/site.

• Backup each application including Services VM (if used).
• Note releases from System Platform and templates.
Installation
• Insert AVP DVD and USB Flash drive into Avaya Supplied Server.
• AVP installs and ejects CD/DVD.
• Remove USB and CD/DVD media from server.
• Deploy VMs using values provided (Solution Deployment Manager)
• Patch Virtual Machines.

Deploying Avaya Aura® Applications
 Utility Server - Each AVP host server requires a Utility Server.
• Provides the routing from the Services Port (Eth1) to the Virtual Machines and
additional functions such as alarm conversion.
 System Manager – Required in all Avaya Aura® 7.0 solutions using

Appliance Virtualization Platform:
• Provides the Common Services functionality across all applications to check versions,
deploy, update, and upgrade Avaya Aura® Applications.
• Example: 6.x sites with a Communication Manager require System Manager and
Communication Manager in release 7.0.
 Avaya Aura® Applications – Can be installed on a server as long as

there is sufficient resources on the AVP host to support it:
• Each application has variable capacities and specific resource requirements.
• Customer requirements and capacities determine the solution footprint.
• Consult Avaya Sales/Sales Engineering for detailed specifications and guidance for
your customer’s scenario.

Deploying Avaya Aura® Applications continued
 Automated Migrations and Upgrades – SDM supports automated
upgrade for CM, SM, and BSM.
 Release 6.x to 7.0 – All System Platform-base Release 6.x system can be
migrated to Avaya Aura® 7.0.
 Recovery to System Platform-based system – In the event of a
migration failure, there is a process to return system to release 6.x.
 No keyboard and mouse required - Installation of Appliance
Virtualization Platform can be performed “headless.”
• Do not use the “non-Supported Attended” AVP installation (only visible with
keyboard/mouse attached).
• Headless is key for servers that do not have keyboard/mouse connections (S8300D
and S8300E servers).

AVP EULA License
1. SSH to AVP Server:
• Username: root
• Password: < root password defined in AVP-Installation-file-generator.xlsm>
2. Read terms of EULA.

3. Accept terms of EULA.
1 login as: root

Using keyboard-interactive authentication.
Password:
The time and date of this login have been sent to the system logs.
VMware offers supported, powerful system administration tools. Please see

www.vmware.com/go/sysadmintools for details.
The ESXi Shell can be disabled by an administrative user. See the vSphere Security
documentation for more information.
Read the following End User License Agreement “EULA” carefully. You must accept the terms of
this EULA to install this software.
2 Press any key to read the EULA.
AVAYA GLOBAL SOFTWARE LICENSE TERMS

REVISED: March 2015
3 Do you accept the terms of this EULA? (Y)es / (N)o: Y

installing license
show eula done
~ #

AVP EULA License continued
 SDM - VM Management – Location – Host tab – License Status column.

Verify AVP Version and ESXi System Version
 Verify AVP version: cat /opt/avaya/etc/avaya-avp.version
~# cat /opt/avaya/etc/avaya-avp.version
Release: 7.0.0.0
Sprint: 16
Build: 1
SVN: 46
~ #
 Verify ESXi System Version: # esxcli system version get
~# esxcli system version get

Product: VMware ESXi
Version: 5.5.0
Build: Releasebuild-2456374
Update: 2
~ #

AVP Services Command
 AVP Services HELP: # /opt/avaya/bin/eventlist.py -h
~# /opt/avaya/bin/eventlist.py –h
Usage: eventlist.py [options]
Options:
-h, --help show this help message and exit
-l LOGSIZE, --logsize=LOGSIZE
Number of logs to retrieve.
-c CATEGORY, --category=CATEGORY
Categories to retrieve (info, error, warning, user).
Multiple -c arguments can be used.
 AVP Services INFO: # /opt/avaya/bin/eventlist.py –c info

~# /opt/avaya/bin/eventlist.py –c info
2015-06-02 20:13:09.216891+00:00 INFO User [email protected] logged in as
2015-06-02 20:12:02.358389+00:00 INFO User [email protected] logged out (login time:
Tuesday, 02 June, 2015 20:12:02, number of API invocations: 0, user agent: VMware-
client/5.1.0)
2015-06-02 20:12:02.351300+00:00 INFO User [email protected] logged in as VMware-
client/5.1.0

AVP Rollback to System Platform
 Restrictions:
– ESXi - Creates a GPT (GUID Partition Table) partition table as opposed to the
usual msdos or MBR (Master Boot Record) partition table.
– System Platform - Refuses to install on a GPT partitioned disk, and gives you
no choice but to abort the install.
ESXi System Platform

AVP Rollback to System Platform continued
 Workaround:
– Boot a RAM-disk recovery CD.
– Log into the ESXi server via the services port.
• The services port is configured and usable regardless of
server type.
 SSH to: [email protected]
– Login: admin
– Password: admin01
– su to root shell.
– Delete the GPT partition (commands in BOLD):
• >parted /dev/sda (HP Systems: /dev/cciss/c0d0)
• >mklabel
– Confirm: Yes
• >msdos (Make new label)
• ><enter>
• >parted /dev/sdX (where X=b for S8300D, X=a for S8300E)
• >mklabel
– Confirm: Yes
• >msdos (Make new label)
• ><enter>
• >quit
– Install System Platform. © 2015 Avaya Inc. All rights reserved.
AVP and Utility Server Unsupported Functions
 Services VM on Embedded Survivable Remote:
• Services VM memory has increased to 1GB; Other factors do not fit.
• Use Main SAL, ION box, S8300E or backup VPN for SAL traffic as workarounds.
 Remote migration from 6.x to 7.0:

• Remote upgrade is not possible on the migration to 7.0. Physical access to the server
required.
• Post 7.0 upgrades can be done remotely (e.g 7.0 to .7.1).
 Consolidated maintenance application backup and restore (no on demand back up

interface on SDM):
• Each application needs to be configured for scheduled backups
• Restores (if required) is done directly on the application
• Backup and restore as part of upgrade and migration is included in 7.0
 Survivable Embedded Session ICC and CM to branch gateway command:

• Not possible to jump from gateway to CM and from CM to the gateway.

Solution Deployment
Manager

Solution Deployment Manager
Avaya Aura ® Applications (OVAs):

• Session Manager (SM)
• Branch Session Manager (BSM)
• System Manager (SMGR)
Solution Deployment Manager • Application Enablement Service (AES)
• Utility Services (US)
• Communications Manager (CM)
• CM Messaging (CMM)
• Engagement Development Platform (EDP)
(including Presence Services Snap-in)
• Avaya Aura Media Server (AAMS)
• WebLM
• ADS/SAL
• Avaya Aura Messaging (AAM)
App A App B App A App B

ESXi Host AVP Host
Virtualized Environment Avaya Common Server

Solution Deployment Manager
1
SDM Client
Windows® Desktop
2
Centralized System Manager – SDM.
SDM Deployment Process:

SDM System Manager
1. Use SDM Client to deploy
System Manager to Appliance
Virtualization Platform Server.
2. Use Centralized SMGR - SDM
to deploy other Avaya Aura®
applications.
Avaya Common Server
Solution Deployment Manager Topology
PLDS
or
System Manager SDM Alternate Source
CM
IP Office
G450
AA®
G650 AES Applications
 Centralized:
– Deployment of applications.
– Software/Firmware upgrades.
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 Deployment of hypervisor patches
Upgrade elements Upgrade of System Manager
Deployment of element patches Deploying System Manager patches
Discovery -
Analyze -
Software Library -
Upgrade Sequencing -
Upgrade Dependency -

SDM Managed Applications
 SDM can deploy Avaya Aura® 7.0 Application OVAs to both customer-provided
Virtual Environment and Avaya Provided Appliance environments:
– Session Manager (SM)
– Branch Session Manager (BSM)
– System Manager (SMGR)
– Application Enablement Service (AES)
– Utility Services (US)
– Communications Manager (CM)
– CM Messaging (CMM)
– Engagement Development Platform (EDP) (including Presence)
– Avaya Aura® Media Server (AAMS)
– WebLM
– ADS/SAL
– Avaya Aura® Messaging (AAM)

SDM Client - Installation Prerequisites
 Operation System:
– Microsoft Windows® (7 (32 and 64 bit)
– Microsoft Windows® 8.1 (32 and 64 bit)
– Microsoft Windows® Server 2008
– Microsoft Windows® Server 2012 R2
 Disk Requirements: 5 GB
 Open Port Requirements:
– Port 443
– Port 1527
– CATALINA_HOME must not be set as environment variable on the computer.

 Supports same web browsers as SMGR 7.0.
 Automatically start SDM service at Start-up.
Note:
– Centralized SMGR - SDM is the preferred deployment solution.
– SDM Client is an alternate solution when the SMGR - SDM is not available.

SDM Client – Installation Steps Summary
1. At Microsoft Windows® desktop, launch: SDMClient_win64_7.0.x.0.xxxxx-xx.exe.
2. Accept End User License Agreement (EULA).
3. Select a location for installation files.
4. Install SDM client on Windows desktop.
3
Note: SDM Services is required to run SDM
client.
SDM Client Dashboard
 Launch SDM client from desktop. SDM client shortcut launches browser:
– https://localhost/vm-mgmt-ui/pages/dashboardClient.html
 SDM Dashboard:
– VMs – VM Management
– Upgrades – Upgrade Management
– VM/Host Status – Graph
 Start SDM Client Services if you cannot

access SDM client.

SDM Client Dashboard – VM Management Tree
VM Management Tree
Locations
Hosts
Virtual Machines Virtual Machines
Additional SDM Virtual Machines Virtual Machines

Management Functions

VM Management - Locations
Select new Location to see Host tab.

VM Management - Hosts
Connecting to Host
Root password
defined during ks.cfg
file creation.
VM Management - VMs
Virtual Machine configuration continued on next page.

Virtual Machine Deployment Workflow
1. Select Location and Host:
• Select Host:<Location A>
• Host FQDN: <AVP FQDN or IP Address>
• VM Name: <SMGR01>
2. Select Resource Pool and Datastore:

• Resource Pool: <automatically collected by SDM>
• Datacenter/Cluster: <automatically collected by SDM>
• Datastore: <datastore01>
3. Deploy OVA:
• Provide Path: <radio button selected by default>
• Select OVA File: <C:\Users\Student\Downloads\SMGR-7.0.0.6.14011-e55-49.ova>
• Select Flexible Footprint: <User selectable Profile based upon Avaya Application
(OVA)>
4. Configuration Parameters:
• IP/Network parameters: <Customer provided data>
5. Network Parameters:
• Public: <VM Network>
• Out of Band Management (optional): <Management Network>
6. Deploy:
• Accept EULA
• Login to Avaya Aura® server

VM Management – VM Configuration
1
Validation Check

VM Management – VM Configuration continued

VM Management – VM Configuration continued
End User
5
License Agreement

Live Demo
 Install Solution Deployment Manager – Client.
 Access and Navigate Solution Deployment Manager –
Client.

Centralized SMGR –SDM Dashboard
 Navigate to Services – Solution Deployment Manager.
 Solution Deployment Manager:
• VMs – VM Management
• Upgrades – Upgrade Management
• Downloads – Download Management
• Software Libraries – Software Library Management
• Settings – User Settings
* *
* Additional Options in SDM Central versus SDM Client.

SDM – VM Management – Locations and Host
Create same Locations and Hosts defined in SDM Client to
automatically populate System Manager Virtual Machine
appearance.

SDM Dashboard – User Settings
 Enables SDM
software analysis
capabilities against
PLDS or Alternate
Source.
 Specify Avaya Support
Site (PLDS) or
Alternate Source.
 Enter PLDS
credentials.
 Define proxy settings
(if required).
VM VM PLDS
SDM
AVP Compare Alternate Source
Configurations
SDM Dashboard – Upgrade Management
 Automated upgrade and migration capabilities of SMGR-SDM for
Communication Manager and Session Manager is based on proper
Discovery for these Elements.
 Automated process uses an Analyze function to compare the software
versions running on CM (including Gateways), TN Boards and Media
Modules), and SM to what a customer solution entitlement.
 It is critical that a proper Discovery and Inventory be executed prior to
trying to use the automated procedures.
Note:
Refer to the Administering Avaya Aura® System Manager for Release 7.0, for
detailed information on Managing Inventory.

SDM Dashboard – Upgrade Management cont.
 Supports:
– CM release 5.x to 5.21. Then upgrade 5.2.1 to 7.0.
– CM 6.x to release 7.0.
 System Manager (6.3.8 or 7.0) also supports upgrading CM 6.x,
gateways, media modules, and TN boards to Release 6.3.6. Then apply
latest Service pack:
– The user interface is available only if you select the target version on the
Solution Deployment Manager - Upgrade Release Setting page to Release
6.3.8.
– For CM 6.x to 6.3.6 upgrades, System Platform is upgraded as part of the
automated upgrade process.
 Upgrade Management requires setup of SNMP and Login Discovery.

SDM Dashboard – Manage Software
 Enables automatic upgrade of Communication Manager and associated devices (Gateways,

TN boards, media modules).
 Displays the current inventory along with the upgrade state of the devices.
 Options to refresh and analyze current inventory.
 Provide recommendations on available upgrade options (software or firmware) for devices.
 Views and status during the upgrade process. © 2015 Avaya Inc. All rights reserved.
SDM Dashboard – Software Library Management
SCP Configuration Tab
SFTP Configuration Tab
FTP Configuration Tab
 Remote repository for software and firmware used to

upgrade Elements. HTTP/HTTPS Configuration Tab
 SMGR access this library during the

software/firmware download process.
 IP Office uses the HTTP/HTTPS Configuration to
retrieve the software/firmware files during the upgrade
process.

SDM Dashboard – Download Management
 Upload software and firmware from Avaya PLDS or Alternate Source to

the System Manager.
 Files are later used to upgrade software and firmware of devices.

Out of Band
Management

Out of Band Management
 Enables the ability to have a separate management and non-management
network traffic across physical and logical connections.
Avaya Aura®
OOBM VLAN Service VLAN Public VLAN
 Isolates Management traffic from Public networking traffic.

 System Manager Management network traffic (examples):
– Session Manager database replication.
– Element Management to Communication Manager, Session Manager, and
Enterprise Development Platform, etc.
– Solution deployment, upgrades, and updates.
 System Management Non-Management or Public traffic (examples):

– End-user self-provisioning.
– Client devices getting certificates through Simple Certificate Enrollment Protocol (SCEP).

OOBM Architecture for Common Servers
 Public Port Group - ESXi management interface with customer network address
specified or generic customer network address.
– Connected to vSwitch0 and uplink as Eth0.
– Eth0 set to: Enabled.
 Services Port Group - ESXi management interface.

– Connected to vSwitch1 and have an uplink as Eth1.
– IP address: 192.168.13.6
– Subnet Mask: 255.255.255.248
– Eth1 set to: Enabled
 Out of Band Management Port Group - Isolated Management network.

– Connected to vSwitch2 and have an uplink as Eth2 on the server.

OOBM Architecture for S8300 Servers
 Public Port Group - ESXi management interface with customer network address
specified or generic customer network address.
– Connected to vSwitch0 and uplink as Eth1.
– VLAN: <defined in ks.cfg file>
 Services Port Group – ESXi management interface.

– IP Address: 192.168.13.6
– Subnet Mask: 255.255.255.248
 Out of Band Management (S8300D) - Isolated Management network.

– Connected to vSwitch0 with no VLAN ID.
 Out of Band Management (S8300E) - Isolated Management network.


Out of Band Management Architecture continued
NIC Virtual Machine A NIC
NIC Virtual Machine B NIC
Virtual Switches
Optional Redundant Paths
NIC NIC
NIC NIC
Physical Server
OOBM VLAN
Service VLAN
Public VLAN
Physical Switch A
OOBM VLAN
Service VLAN
Public VLAN
Physical Switch B
OOBM Networking
 OOBM Appliance Virtualization Platform –OOBM is already setup and ready for
Avaya Aura® Application deployment.
 OOBM for Virtualized Environment - Customer is responsible for the
configuration of the vSwitches and connection to the rest of the network.
– Hypervisor only carries management traffic.
– There is no user traffic to the hypervisor. First management port of the ESXi hypervisor is present on
either:
• OOBM vSwitch
• Public vSwitch
– Services Port VM includes an interface on both:

• OOBM vSwitch
• Public vSwitch
 Solution Deployment Manager - Provides the configuration of the OOBM

management IP addresses, vSwtich and Port Group setup and any static routing
required to route traffic onto the management network.
 Hypervisor Configuration - Allows customers to setup an OOBM configuration
such that all control and management traffic is separated onto a different physical
NIC on the servers.

NIC Bonding
 NIC Teaming/Bonding – Allows multiple Network Interface Connections
(NICs) to bond to multiple network interface into a single channel.
– Appliance Model (AVP) - Use CLI.
– Virtualized Environment Model (VE) – Use vSphere client.
 AVP NIC Bonding:

– Log into AVP host via CLI:
• Add eth3 to the public virtual switch:
# /opt/avaya/bin/nic_teaming add vmnic3 vSwitch0
• Add eth3 to the list of active adapters:
# esxcli network vswitch standard policy failover set -v

vSwitch0 --active-uplinks vmnic0,vmnic3

NIC Bonding cont.
 ESXi Host NIC Bonding:
1. Log into vCenter/vSphere and select the ESXi host.
2. Navigate to Configuration tab.
Note: Configuration tab is displayed when accessing ESXi host directly using vSphere
client.
3. At Networking - vSwitch0, click Properties.

NIC Bonding cont.
4. Select Network tab.
5. Click Add button.

NIC Bonding cont.
6. Select vmnic3.
7. Click Next button.

NIC Bonding cont.
8. Use the Move Up/Move Down buttons to make both NICs Active Adapters.
9. Click Next button.

NIC Bonding cont.
10. Click Finish button.
10

OOBM Support for Avaya Aura® Applications
 Appliances with the OOBM support:
– Communication Manager 7.0
– Session Manager 7.0
– Application Enablement Services 7.0
– System Manager 7.0
– Gateways, including Avaya Aura® Media Server 7.7
– Presence Services 7.0

OOBM Appliance Virtualization Platform
 SDM administration – Network Parameters – Out of Band Management.

OOBM for Virtualized Environment
 vSphere administration – Deploy OVM:
– Network Mapping
– Properties

Upgrade and Migration
to Avaya Aura® 7.0

Avaya Aura® 7.0 Deployment Options
Virtualized Non-Virtualized
Virtualized Virtual Collaboration Pod Server Software
Application Environment Appliance Appliance Only
Communication Manager √ √ Future x x
Session Manager √ √ Future x x
System Manager √ √ Future x x
Application Enablement Services √ √ Future x √
Presence Services (on EDP) √ √ Future x x
Utility Services √ √ Future x x
WebLM √ √ Future x x
Communication Manager Messaging √ √ Future x x
Avaya Aura Media Server √ √ Future √ √
Note:
• Virtualized Environment = Customer Supplied ( Server + VMware) + Avaya Supplied Applications
• Virtual Appliance = Avaya Supplied (Server + Appliance Virtualization Platform + Applications)
• Server Appliance = Avaya-supplied (Server + Redhat Linux OS + Application)
• Software Only = Customer-supplied ( Server + Redhat Linux OS) + Avaya supplied Application

Avaya Common Servers Support for New Orders
 Virtual Appliance Deployments - For new purchases, Avaya Aura® 7.0 applications are shipped with the HP ProLiant DL360
PG8 server.
 ASD uses internal logic to determine which mix if servers are appropriate for a solution based upon answers provided to
questions within too.
 ASD tool uses factors such as number of users and availability to calculate the appropriately sized server construct.
Material Code Description

380762 • DL360PG8 SRVR LARGE AVP
380763 • DL360PG8 SRVR MEDIUM AVP
380764 • DL360PG8 SRVR SMALL AVP
380765 • DL360PG8 SERVER CM HIGH DUPLX AVP
Server DL360PG8 SRVR DL360PG8 SRVR DL360PG8 SRVR SMALL DL360PG8 SERVER
Component LARGE AVP MEDIUM AVP AVP CM HIGH DUPLX AVP
Form factor 1U 1U 1U 1U
Processor family Intel (2.9 GHz - E5- Intel (2.3 GHz - E5- Intel (2.3 GHz - E5-2630) Intel (2.9 GHz - E5-
2667) 2630) 2667)
Number of processors 2 2 1 1
Memory type 4 GB RDIMM (16) 4 GB RDIMM (8) 4 GB RDIMM (4) 4 GB RDIMM (4)
Total memory 64GB 32GB 16GB 16GB

Hard Disk Drive 300GB Drives 300GB Drives 300GB Drives 300GB Drives
Number of Hard Disk Drive 4 3 2 2
RAID Level 5 3 1 1
Network interface 4 4 4 4
Optical drive DVD+/-RW, SATA, DVD+/-RW, SATA, DVD+/-RW, SATA, DVD+/-RW, SATA,
INTERNAL INTERNAL INTERNAL INTERNAL
Power supply 750W AC 460W AC 460W AC 460W AC

Number of power supplies 2 2 1 1
Other Supported Hardware
 Avaya Servers Supported for Server Appliance Deployments of AAMS
(Not Virtualized):
Material Code Description
380841 R220XL Server AAMS Small
 Avaya Embedded Servers:

– Both S8300D and S8300E will be supported by Aura 7.0.
 Gateways:
– Supported gateways include:
• G430
• G450
• G650
– Legacy gateways tested with Aura 7.0 but they are no longer under
manufacturer support.
• G350 + S8300D
• G250 + S8300D
• G700 + S8300D

SMGR – Supported Upgrade Paths (4)

SM – Supported Upgrade Paths (5)

CM – Supported Upgrade Paths (5)

CMM - Supported Upgrade Paths (4)

AE Services – Supported Upgrade Paths (6)

PS – Supported Upgrade Paths (5)

US – Supported Upgrade Paths (2)

WebLM – Supported Upgrade Paths (3)

Next Steps – Additional
Training

Next Steps – Additional Training
Course Course Number
What is New in Avaya Aura® Application Enablement Services 2008V or W
7.0
What is New in Avaya Aura® Communication Manager 7.0 2009V or W
What is New in Avaya Aura® Presence Services 7.0 2010V or W
What is New in Avaya Aura® System Manager 7.0 and Avaya 2011V or W
Aura® Session Manager 7.0
Migrating and Upgrading to Avaya Aura® Platform 7.0 2012V
Avaya Aura® 7.0 Administration 2013V
What is New in Avaya Aura® Contact Center Elite 7.0 2515V or W

Documentation and Resources
https://support.avaya.com
https://support.avaya.com
 What’s New with Avaya Aura® Release 7.0

 What’s New Avaya S8300E Server
 Deploying Avaya Aura® Applications
 Deploying Avaya Aura® Utility Services on VMware®
 Deploying Avaya Aura® Communication Manager on VMware®
 Deploying Avaya Aura® System Manager on VMware®
 Upgrading System Manager to Release 7.0 on VMware® in Virtualized Environment
 System Manager 7.0 SNMP White paper (including MIBS)
 Deploying Avaya Aura® Session Manager on VMware®
 Avaya Aura® Application Enablement Services using VMware® in the Virtualized Environment Deployment Guide
 Deploying Avaya Aura® Application Enablement Services in a Software-Only Environment
 Avaya Aura® Presence Services Snap-in Reference
 Migrating from System Platform to Appliance Virtualization Platform
 Upgrading to Avaya Aura® 7.0
 Deploying and Updating Avaya Aura® Media Server Appliance

Course Summary
Topics covered in this course include:
 Describe how the Avaya Aura platform provides the
foundation for business collaboration.
 List key benefits to Avaya Aura 7.0.
 Identify the products and applications included in Avaya
Aura 7.0.
 Describe the key features introduced with Avaya Aura
7.0.
 Identify the Avaya Aura 7.0 hardware requirements for
specific servers and deployments.
 Describe Appliance Virtualization Platform.
 List the features and functionalities of the Utility Server in
Avaya Aura 7.0.
 Describe Solution Deployment Manager and it role in an
Avaya Aura 7.0 deployment.
 List key features of Solution Deployment Manager.
Course Summary continued
Topics covered in this course include:
 Describe Out of Band Management and how it is used in
Avaya Aura® 7.0.
 List common upgrade and migration scenarios from
previous releases to Avaya Aura 7.0.
 Identify supported and unsupported migrations to Avaya
Aura 7.0.

Skype For Business Server 2015 Step by Step For Anyone - Installing and Upgrading - REV - 05

Uploaded by

Copyright:

Available Formats

Skype For Business Server 2015 Step by Step For Anyone - Installing and Upgrading - REV - 05

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Skype For Business Server 2015 Step by Step For Anyone - Installing and Upgrading - REV - 05

Uploaded by

Copyright:

Available Formats

What is New in Avaya

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

What is New in Avaya Aura® 7.0 (2007V or W) No -

Migrating and Upgrading to Avaya Aura® Platform 7.0 (2012V) No -

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

Secure Mobile 250K SIP Users

Improved Full virtualization on Avaya or Out of Band

Appliance Virtualization EDP Call Intercept Applications for

Conferencing • Simplified deployment of multimedia

• Dynamic allocation of bandwidth

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

Avaya Aura® Session Manager (SM) 7.0

Avaya Aura® Communication Manager (CM) 7.0

Avaya Aura® Branch Gateways (BGW) 7.0

Avaya Aura® Presence Services (PS) 7.0

Avaya Aura® System Manager (SMGR) 7.0

Avaya Aura® Utility Services (US) 7.0

Avaya Aura® Application Enablement Services (AES) 7.0

Avaya Aura® Appliance Virtualization Platform (AVP) 7.0

Avaya Aura ® Media Server 7.7

Avaya WebLM 7.0

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

13 G450 Gateways, 4160 channels: 39U rack space

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

 Applications split into individual product

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

 Increased Number of Domain Control Associations in AES:

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

 Emergency Call Adjunct Interface Update for MDA:

© 2015 Avaya Inc. All rights reserved.

Engagement Development Platform

Appliance Virtualization Platform

Avaya Common Server

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

© 2015 Avaya Inc. All rights reserved.

Memory type 2 GB DDR3 RDIMM 2 GB DDR3 DIMM

Hard Disk Drive 300 GB 146 GB

Number of Hard Disk Drive 3 3

Power supply 460 Watts AC 502 Watts AC

Number of power supplies 2 2

© 2015 Avaya Inc. All rights reserved.

Memory type 4 GB RDIMM 4 GB RDIMM

Total memory 32GB 32GB