Chapter 3: Planning Your Mcu Deployment; Deploying Redundant Mcus - Avaya Scopia Elite 6000 Administrator's Manual

Chapter 3: Planning your MCU Deployment

When planning your MCU deployment, it is important to consider both bandwidth usage and port
security, as described in the following sections:
Related links

Deploying Redundant MCUs

Planning a Centralized or Distributed Topology (Cascading) for MCU
Planning Network Redundancy or IP Separation (Dual NIC)
About the Capacity of the MCU
Ports to Open for the Scopia
Deploying Redundant MCUs
Redundancy is a way to deploy a network component, in which you deploy extra units as 'spares',
to be used as backups in case one of the components fails.
You can achieve MCU redundancy by deploying additional MCUs that are configured with the
same set of service prefixes as the devices which they back up. You can also use the distributed
topology of your deployment where MCUs located in different time zones can cover up for a failing
MCU. MCU fallback is managed by Equinox Management, as explained in Administrator Guide for
Avaya Equinox Management .
This is different from LAN redundancy, which uses one of the MCU's two network ports as
redundant, so if one fails, the other takes over. For more information, see
Redundancy or IP Separation (Dual NIC)
Related links
Planning your MCU Deployment
December 2017
on page 16
on page 20
®
Elite 6000 MCU on page 22
on page 20.
on page 16
Administrator Guide for Avaya Scopia
Comments on this document? infodev@avaya.com
on page 17
on page 20
Planning Network
®
Elite 6000 MCU 16