Avaya Oceana hardware requirements

Last Updated : May 15, 2025 |

The following table provides information about the memory, disk, and vCPU requirements for each component of Avaya Oceana®:

Component/

Platform

Requirement

Avaya Oceana® Agents

4500

2000

1000

500

250

100

Avaya Oceana® Cluster 1

Avaya Breeze® platform

Nodes

3

3

3

3

3

3

Memory/node

98GB

98GB

66GB

50GB

50GB

34GB

Minimum disk size/node

505GB

505GB

505GB

505GB

505GB

505GB

vCPUs/node

16

12

12

8

8

8

Input Output Processing / sec (IOPs)

120

100

100

50

50

50

Avaya Oceana® Cluster 2

Avaya Breeze® platform

Nodes

2

2

2

2

2

Memory/node

34GB

34GB

26GB

26GB

18GB**

Minimum disk size/node

355GB

355GB

355GB

355GB

355GB

vCPUs/node

8

8

4

4

4

IOPs

50

50

50

25

25

Avaya Oceana® Cluster 3

Avaya Breeze® platform

Nodes

2

2

2

2

2

2

Memory/node

34GB

34GB

18GB

18GB

18GB

14GB

Minimum disk size/node

405GB

405GB

405GB

405GB

405GB

405GB

vCPUs/node

8

8

4

4

4

4

IOPs

50

50

50

25

50

50

Avaya Oceana® Cluster 4 (Optional)

Avaya Breeze® platform

Nodes

3

3

2

2

2

2

Memory/node

18GB

18GB

18GB

18GB

18GB

10GB

Minimum disk size/node

405GB

405GB

405GB

405GB

405GB

105GB

vCPUs/node

4

4

4

4

4

4

IOPs

50

50

50

25

25

25

Avaya Oceana® Cluster 5 (Optional)

Avaya Breeze® platform

Nodes

2

2

2

2

2

2

Memory/node

14GB

14GB

14GB

14GB

14GB

10GB

Minimum disk size/node

305GB

305GB

305GB

305GB

305GB

305GB

vCPUs/node

4

4

4

4

4

4

IOPs

50

50

50

50

50

50

Omnichannel Datastore

Windows

Nodes

2

2

2

2

2

2

Memory/node

16GB

16GB

16GB

16GB

16GB

12GB

Minimum disk size/node

4 Disks (100GB, 60GB, 1TB, and 60GB)

4 Disks (100GB, 60GB, 1TB, and 60GB)

4 Disks (100GB, 60GB, 1TB, and 60GB)

4 Disks (100GB, 60GB, 100GB, and 60GB)

4 Disks (100GB, 60GB, 100GB, and 60GB)

4 Disks (100GB, 60GB, 100GB, and 60GB)

vCPUs/node

8

8

4

4

4

4

IOPs

100

100

100

50

50

50

Avaya Control Manager

Windows

Nodes

2

2

2

2

2

2

Memory/node

12GB

12GB

12GB

12GB

12GB

12GB

Minimum disk size/node

300GB

300GB

300GB

300GB

300GB

300GB

vCPUs/node

8

8

8

8

8

8

IOPs

50

50

50

25

25

25

Avaya Control Manager Database

Windows

Nodes

2

2

2

2

2

2

Memory/node

12GB

12GB

12GB

12GB

12GB

12GB

Minimum disk size/node

300GB

300GB

300GB

300GB

300GB

300GB

vCPUs/node

8

8

8

8

8

8

IOPs

50

50

50

25

25

25

Avaya Context Store External Data Mart and Customer Journey Database

Windows

Nodes

1

1

1

1

1

1

Memory/node

24GB

16GB

16GB

16GB

16GB

12GB

Minimum disk size/node

3200GB

2105GB

2105GB

2105GB

2105GB

215GB

vCPUs/node

12

8

8

8

8

4

IOPs

100

100

100

50

50

50

Avaya Control Manager Database co-resident with Avaya Context Store External Data Mart (EDM) and Customer Journey Database

Windows

Nodes

2

2

2

2

2

2

Memory/node

24GB

24GB

24GB

24GB

24GB

24GB

Minimum disk size/node

3500GB

2405GB

2405GB

2405GB

2405GB

515GB

vCPUs/node

12

12

12

12

12

12

IOPs

750

750

750

750

750

750

Avaya Aura® Web Gateway (Optional)

RHEL

Nodes

2

2

2

2

2

2

Memory/node

8GB

8GB

8GB

8GB

6GB

6GB

Minimum disk size/node

132GB

132GB

132GB

132GB

132GB

132GB

vCPUs/node

8

8

8

8

4

4

IOPs

100

100

100

100

100

100

Avaya Aura® Device Services (Optional)

RHEL

Nodes

2

2

2

2

2

2

Memory/node

9GB

9GB

9GB

9GB

9GB

9GB

Minimum disk size/node

250GB

250GB

250GB

250GB

250GB

250GB

vCPUs/node

6

6

6

6

6

6

IOPs

100

100

100

100

100

100

Avaya Aura® Media Server (Avaya Aura® Web Gateway) (Optional)

RHEL

Nodes

3*

3*

3*

2

2

2

Memory/node

16GB

16GB

16GB

16GB

8GB

8GB

Minimum disk size/node

50GB

50GB

50GB

50GB

50GB

50GB

vCPUs/node

16

16

16

16

8

8

IOPs

100

100

100

100

100

100

Avaya Aura® Media Server (Avaya Breeze® platform) (Optional)

RHEL

Nodes

2

2

2

2

2

2

Memory/node

8GB

8GB

8GB

8GB

8GB

8GB

Minimum disk size/node

50GB

50GB

50GB

50GB

50GB

50GB

vCPUs/node

8

8

8

8

8

8

IOPs

100

100

100

100

100

100

Avaya Aura® Session Border Controller (Optional)

RHEL

Nodes

2

2

2

2

2

2

Memory/node

16GB

16GB

16GB

16GB

16GB

16GB

Minimum disk size/node

100GB

100GB

100GB

100GB

100GB

100GB

vCPUs/node

6

6

6

6

6

6

**For 250 Avaya WebRTC Connect agents, Avaya Oceana® Cluster 2 requires at least 24 GB RAM to support the Avaya Mobile Video Snap-in and Avaya BotConnector Snap-in Avaya WebRTC Connect services.

* For 1000 Avaya WebRTC Connect agents, you must have 3 Avaya Aura® Media Server nodes.

Note:
  • Each Avaya Breeze® platform node of a cluster must reside on a different physical server.

  • For Red Hat Enterprise Linux (RHEL), Avaya Oceana® only supports the version that Avaya ships with the solution.

  • For new deployments, Avaya Oceana® only supports the External Data Mart database running Microsoft SQL Server on a supported version of Windows Operating System.

    For supported version combinations, see the following:

  • For Avaya WebRTC Connect:

    • Avaya Aura® Web Gateway OVA Profile = medium

    • Avaya Aura® Device Services OVA Profile = 1

    • Avaya Aura® Media Server (Avaya Aura® Web Gateway) OVA Profile = 5

    • Avaya Aura® Media Server (Avaya Breeze® platform) OVA Profile = 3

    For High Availability (HA) deployments, you must have two instances of each of these WebRTC Connect components.

  • Drive F of Omnichannel Datastore requires engineering based on the email and chat/SMS profiles of the customer.

  • Avaya recommends two dedicated standalone Application Enablement Services (AES) servers for all Avaya Oceana® deployments to ensure AES High Availability in the solution. Currently, Avaya Oceana® does not support AES GRHA.

  • For co-resident deployment of Avaya Control Manager and External Data Mart (EDM) databases, the minimum disk size/node includes the amount of disk space required to store one year of EDM Data and does not include the disk space required for SQL transaction logs or database backups. Therefore, you must create an appropriate SQL Server Agent Job or Maintenance Plan to prevent the transaction log from growing rapidly.

    For more information about maintenance plans, see https://docs.microsoft.com/en-us/sql/relational-databases/maintenance-plans/maintenanceplans?view=sql-server-2016 and select the appropriate version of SQL Server. Also, if you migrate EDM data from a source EDM to the co-resident Microsoft SQL server, ensure that you add sufficient disk space to accommodate the data.

  • Avaya Oceana® 3.10.0.1 deployment requires an addition of 2 GB RAM and 5 GB hard disk for each node. Avaya Breeze® platform Supports VMware/ESXi 7.x and VMware/ESXi 8.x