Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c87befb553017c1aa323650024, userName='null'}
JIRAIDAUTHCHOR-10772
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8e901a1, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccd308e6, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4


This section describes

Spacevars
0product
hardware and software requirements and recommendations for
Spacevars
0series3
installations using VMware ESXi.


Warning
iconfalse

The recommended hardware and software settings are intended to ensure optimum 

Spacevars
0product
stability and performance. If the recommended settings are not used, 
Spacevars
0product
system may not behave as expected.


Note
titleSBC SWe Edge Operations in an ESXi Cluster are Supported, with Restrictions


The 

Spacevars
0series3
 supports operations within an ESXi host under the control of a vCenter Server (centralized management utility for VMware) provided the operations and features invoked on the ESXi host by the vCenter Server match those invoked by the ESXi host console when running outside the control of the vCenter Server.

Refer to the following guidelines and restrictions:

  1. Select operations on the ESXi host initiated by the vCenter Server (such as those not available with the ESXi host console when running in standalone mode) may result in a disruption of 
    Spacevars
    0series3
     operations. Examples of popular vCenter Server-initiated operations that are not supported by the 
    Spacevars
    0series3
     include vMotion and Fault Tolerance.
  2. If unsupported vCenter Server-initiated operations result in a disruption of the
    Spacevars
    0series3
    , a new unprovisioned (blank) and unlicensed 
    Spacevars
    0series3
     may need to instantiated to replace the original 
    Spacevars
    0series3
     instance.  Please contact Ribbon TAC to initiate a license re-issuance.


License Requirements

You must obtain and apply a valid 

Spacevars
0product3
 license in order to configure and use the 
Spacevars
0product3
. See below:


Server Hardware Requirements

Multiexcerpt
MultiExcerptNameVMware Hardware


ConfigurationRequirement
Processor2nd Generation Intel Core or Intel Xeon Processor (Sandy bridge or later)
Host OSESXi 5.5 or above
Architecture64-bit Intel processor
RAM

Each 

Spacevars
0series3
instance requires from 1.5 GiB to 4 GiB of RAM depending on the configuration

DatastoreHard disk requirements are dependent upon the number of VMs hosted, the size of each VM at full size, and whether snapshots will be enabled.



Warning
iconfalse

Platforms using AMD processors are not supported.

Minimum ESXi hosting requirements are posted by VMware.

VMware ESXi

Note

The minimum CPU Emulation Mode (EVC) recommended is Nehalem (problems have occurred when the EVC on the ESXi host is set to Penryn).

Customized ESXi images for various server platforms are available on VMware and Hardware platform vendor sites.

  • It ensures that all the required drivers for network and storage controllers are available to run ESXi server.
  • Most of the customized ESXi images comes with customized management software to manage server running ESXi software.
  • Customized ESXi images for HP ProLiant and IBM servers are available at:

For more information, please visit the VMware Knowledge Base

Refer to VMware Compatibility Guide (external site) for a list of VMware supported Intel processors. 

Refer to ESXi hardware requirements to ensure the VMware supported Intel processors meet ESXi hardware requirements.


Ribbon Recommendations for 
Spacevars
0series3

General Recommendations

  • Plan enough resources (RAM, CPU, NIC ports, hard disk, etc.) for all the virtual machines (VMs) to run on the server platform, including resources needed by ESXi itself.
  • Allocate each VM with only as much virtual hardware as that VM requires. Provisioning a VM with more resources than it requires can, in some cases, reduce the performance of that VM as well as other virtual machines sharing the same hostAdding excess resources may not result in improved performance nor will improved performance or feature difference be supported. Refer to the SBC SWe Edge Performance and Capacity for sanctioned VM sizes and supported performance against sanctioned VMs.

  • Disconnect or disable any physical hardware devices that you will not be using (floppy drives, network interfaces, storage controllers, optical drives, USB controllers, etc.) under BIOS settings to free up interrupt/CPU resources.


Caption
0Table
1VM Configuration Recommendations


SettingMinimum
vCPU1, 2, 4, and 10 supported
RAM

1.5 GiB to support 1 vCPU

2 GiB to support 2 vCPUs

3 GiB to support 4 vCPUs

4 GiB to support 10 vCPUs

vNIC

5 

Spacevars
0series3
 is created with 5 Virtual Network Interfaces (vNICs); all 5 interfaces are required.

Note: One vNIC is mandatory for management.

Virtual Hard Disk5 GiB


 

Additional Information

  • Minimal networking configuration requires the Management Network Interface and at least one Media Interface to be assigned.
  • Each SBC SWe Edge VM will use approximately 5 GiB of Virtual Hard Drive space. Drive size is predetermined by the imported image.
  • The Management Network Interface and each Media Interface must be configured on separate VLANs. Failure to do so can result in undesired behavior such as one-way or no-way audio.


Info
iconfalse

Refer to Downloading the SBC SWe Edge Package for On-Premises Deployment for software download instructions.