Sentinel IPSMGW is supported in a virtualized environment, details presented here provide a guide to the scope of that support and how Sentinel IPSMGW should be setup in that environment.

VMWare Supported

VMWare vSphere ESXi 5.1 and 6 is supported and certified. vCenter is not a mandatory requirement.

Operating System Support

Please refer to the Platforms section of the Rhino Compatibility Guide for supported operating systems.

Hyper-threading support

Hyper-threading is supported and used to maximize performance throughput.

Uncontended RAM Required

Sentinel IPSMGW does make use of Uncontended RAM.

Uncontended disk I/O Required

Sentinel IPSMGW does not require Uncontended disk I/O.

Dedicated Storage Array Required

Sentinel IPSMGW does not require dedicated storage. CDR files and Rhino logs should be partitioned separately and managed to avoid failure or data loss due to space utilization.

CPU Contention Supported

CPU Contention is supported, however %ready numbers should be kept below 5% to avoid significant impact on overall application performance. It is strongly recommended that VMs are bound to physical CPU sockets to ensure predictable latency.

Fault Tolerance

A rhino cluster provides support for both high availability and fault tolerance internally. Sentinel IPSMGW does not make use of the Rhino replication but does use the high availability systems. The cluster as a whole can tolerate failure of individual nodes with no support from the virtual machine. Live replication of virtual machines (FT Model) will interfere with Rhino’s internal clustering mechanisms.

VMWare Fault Tolerance

Sentinel IPSMGW does not support VMWare Fault Tolerance.

VMWare vSphere High Availability

Sentinel IPSMGW provides is own HA clustering based upon the Rhino SLEE Architecture.

VMWare vSphere App High Availability

Sentinel IPSMGW does not support App High Availability.

VMWare vMotion

Sentinel IPSMGW does not support VMWare vMotion.

VMWare vSphere Data Protection

Sentinel IPSMGW supports Data Protection with the exception of RAM.

Stretched Clustering

Sentinel IPSMGW supports Stretched Clustering.

VMWare VM Suspend/Resume

Sentinel IPSMGW does not support Suspend/Resume.

VMWare VM Snapshots

Sentinel IPSMGW does not support Snapshots.

VMWare VM Clone

Sentinel IPSMGW does not support Cloning.

VMWare power management options supported

Sentinel IPSMGW supports all power management.

VMWare clock synchronization

Sentinel IPSMGW does not require clock synchronization.


Sentinel IPSMGW does not require SR-IOV.

Test Lab Minimum Virtual Host Requirements

1 vCPU, 8Gb RAM, 30Gb HD, 0 IOPS (Disk I/O is not normally a significant requirement as it’s not used except for logging and installation/configuration changes. Under normal operation a rhino node produces very little logging, but can use > 100Mb/s during severe error conditions under load).

Production Minimum Virtual Host Requirements

1 Rhino node per VM, 1 CPU (bound) @2.4+Ghz, 12Gb java heap, 30Gb HD, 0 IOPS. A quorum node is much lighter weight, and would require a vm with 1 vcpu, 512Mb ram, 0 IOPS.

System capacity/performance for each production system

1.08M BHCA, + 10.8K Conference attempts.


Linear to 2.4Ghz, No scaling improvement over 2.4Ghz. (At Maximum load @ 2.4GHz, we reach saturation of Java CMS collector).

Virtual host resource changes while running

Sentinel IPSMGW does not support host resource changes while running.

Virtual network interface requirements

IPSMGW Sentinel requires 1 network interface for each mgmt/signalling interface.

Signalling bandwidth requirements

Sentinel IPSMGW requires 500kbps/BHCA.

Latency added by signalling

Sentinel IPSMGW adds 20ms at 50th percentile.

Previous page Next page
Sentinel IP-SM-GW Version 2.7.0