System Requirements for a Virtualized SRC Software
The system requirements for a virtualized SRC software are:
We recommend you to allocate CPU cores, RAM, and hard disk space as same as that of C Series Controllers to attain better performance.
Hard Disk Requirement
The qcow2 image and vmdk image (of subtype monolithicSparse) grow in size up to 250 GB when used on a virtual machine, so you must have more than 250 GB of disk space in the host operating system if you use the qcow2 or vmdk image.
If you are using an SRC iso image, we recommend you to have around 250 GB of disk space allocated to the virtualized SRC software to have enough space for system and component logs.
Table 1 lists the default heap size allocated for SRC components on a virtualized SRC software.
Table 1: Heap Allocation for SRC Components on a Virtualized SRC Software
Default Heap Size on Virtualized SRC Software
Heap Size Adjustable or Not
Web application server
External subscriber monitor
IMS Services Gateway
1 GB or smaller than one-fourth of physical memory
70% of free memory
In a virtualized SRC software, the default heap size is set only for the Java components and not for the non-Java components such as redirect server.
The memory requirements of the virtualized SRC software based on the default heap size allocation are:
At least 2927 MB of memory is required for all Java components other than the SAE and license server.
Subscriber management capacity of the virtualized SRC software depends on the heap size of the SAE. We recommend you to allocate enough heap size for SAE.
1 GB of memory is required for the license server.
You must allocate a minimum of one CPU core for a virtualized SRC software. You can allocate CPU cores same as that of C Series Controller to attain better performance. The CPU cores available in C Series Controllers are: