Virtualized Deployment Requirements

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

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

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

Sentinel IPSMGW does make use of Uncontended RAM.

Sentinel IPSMGW does not require Uncontended disk I/O.

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 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.

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.

Sentinel IPSMGW does not support VMWare Fault Tolerance.

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

Sentinel IPSMGW does not support App High Availability.

Sentinel IPSMGW does not support VMWare vMotion.

Sentinel IPSMGW supports Data Protection with the exception of RAM.

Sentinel IPSMGW supports Stretched Clustering.

Sentinel IPSMGW does not support Suspend/Resume.

Sentinel IPSMGW does not support Snapshots.

Sentinel IPSMGW does not support Cloning.

Sentinel IPSMGW supports all power management.

Sentinel IPSMGW does not require clock synchronization.

Sentinel IPSMGW does not require SR-IOV.

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).

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.

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).

Sentinel IPSMGW does not support host resource changes while running.

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

Sentinel IPSMGW requires 500kbps/BHCA.

Sentinel IPSMGW adds 20ms at 50th percentile.