When deploying a VNF, you configure CPU core settings using system-config parameters. This configuration is based on the specific needs of individual implementations. These parameters allow you to set and change the number of cores they want to assign to forwarding, DoS, and transcoding functionality. The system determines which cores perform those functions automatically.

You determine and manage your core configuration based on the services you need. The system allocates cores to signaling upon installation. You add forwarding cores to match their needs for handling media. You also add DoS and/or transcoding cores if you need those functions in your deployment. Reboot the system for core configuration changes to take effect.

Note the following:

• By default, core 0 is always set to signaling.
• The system selects cores based on function; users do not assign cores.
• The system sets unassigned cores to signaling, with a maximum of 24.

When you make core assignments, the Oracle Communications Subscriber-Aware Load Balancer (OCSLB) provides an error message if the system detects an issue. In addition, the system performs a check when the user issues the verify-config command to ensure that the total number of forwarding, plus DOS, plus transcoding cores does not exceed the maximum number of physical cores. After you save and activate a configuration that includes a change to the core configuration, the system displays a prompt to remind you that a reboot is required for the changes to take place.

You can verify core configuration from the ACLI, using the show datapath-config command or after core configuration changes during the save and activation processes. When using hyperthreading, which divides cores into a single physical (primary) and a single logical (secondary) core, this display may differ. Bear in mind that the OCSLB binds functions to primary or secondary cores using its own criteria, with secondary cores performing signaling functions only. Hypervisors that provide a view into the type of core assigned to a function allow show datapath-config to display primary cores in upper-case letters and secondary cores in lower-case letters. Other hypervisors show all cores as physical.

The OCSLB uses the following lettering (upper- and lower-case) in the ACLI to show core assignments:

• S - Signaling
• D - DoS
• F - Forwarding

The system-config element includes the following parameters for core assignment:

• dos-cores— Sets the number of cores the system must allocate for DOS functionality. A maximum of one core is allowed. It is recommended that the virtual OCSLB has a DoS core configured.
• forwarding-cores—Sets the number of cores the system must allocate for the forwarding engine.

To change core assignments, access the system-config, as follows.

ORACLE# configure terminal
ORACLE(configure)# system
ORACLE(system)# system-config
ORACLE(system-config)# 

Change existing core assignment settings using the system-config parameters listed above. For example, to reserve a core for DoS processing:

ORACLE#(system-config) dos-cores 1

The OCSLB VNF has no system-based maximum number of cores, other than the range of the system-config parameters.

The system checks CPU core resources before every boot, as configuration can affect resource requirements. Examples of such resource requirement variations include:

• There is at least 1 CPU assigned to signaling (by the system).
• If DoS is required, then there are at least 1 CPU assigned to forwarding and 1 to DoS.
• If DoS is not required, then there is at least 1 CPU assigned to forwarding.

The system performs resource utilization checks every time it boots for CPU, memory and hard-disk to avoid configuration/resource conflicts.

Core configuration is supported by HA. For HA systems, resource utilization on the backup must be the same as the primary.