DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
This document describes the steps to configure VMware ESXi for GPU passthrough and launch the GPU SBC instance with recommended performance settings.
This document is based on VMware ESXI 6.7.0 Update 3, as this version supports V100 GPU device passthrough.
The GPU SBC VM is supported from VMware ESXI 6.7.0 Update 3 onwards.
Before creating a VM and installing the SBC SWe software, create the virtual environment on the host as described in the section Configuring Your Network for SBC SWe on VMware. For GPU accelerated solutions, configure the GPU passthrough from VMware ESXi host as described in the following section.
Use the following procedure to enable GPU PCIe Passthrough:
In the list of available PCI devices, select the GPU devices for passthrough using the search option as shown in the following screen:
This screenshot shows the PCI devices after the GPU passthrough is completed. Therefore, the Passthrough attribute is shown as Active. Initially, the Passthrough attribute of the PCI devices is set to Disabled, as shown in the steps that follow.
To enable the PCI passthrough for the GPU devices, select the corresponding GPU device and select Toggle passthrough, as shown in the following screen:
The PCIe device displays a message indicating the change was performed successfully and prompts for a reboot to enable the applied settings.
For GPU accelerated solutions, associate the GPU to the SBC VM as described in the following section.
For GPU accelerated solutions, use the following steps to associate the GPU to the SBC VM.
On the Customize Settings screen, select Add other device > PCI device as shown below:
In the New PCI device drop-down option, select the GPU PCI device to associate with the instance.
Before starting the SBC for ISO installation, configure the following required settings on the SBC instance.
Settings | Description |
---|---|
Boot option | Edit instance settings > VM options > Boot Options > Firmware = EFI Note: GPU support is not present with VMware OVA. |
Instance additional attributes | Edit instance settings > VM options > Advanced > Configuration parameters > edit configurations Add the following attribute: pciPassthru.use64bitMMIO : TRUE Note: For 32GB variant GPU device, add the following attribute pciPassthru.64bitMMIOSizeGB : 64 |
Configure the SBC based on the required call sessions, required cps, and the codec mix.
An example codec mix is shown in the table below:
Passthrough | Percentage: 70% Codec Mix:
| ||||||||||||
Codec | Packetization time | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
G711u | 20 ms | ||||||||||||
Transcode | Percentage: 30% Codec Mix (Call Legs):
|
Use the following steps to activate a traffic profile on the GPU SBC.
Create a codec mix profile for the targeted transcode codec mix.
admin@vsbc1% set system sweCodecMixProfile loadProfile amrwb p20 percentage 15 [ok][2020-06-15 11:48:15] [edit] admin@vsbc1% set system sweCodecMixProfile loadProfile g729 p20 percentage 35 [ok][2020-06-15 11:48:33] [edit] admin@vsbc1% set system sweCodecMixProfile loadProfile g711 p20 percentage 50 [ok][2020-06-15 11:48:46] [edit] admin@vsbc1% commit Commit complete. [ok][2020-06-15 11:48:47] [edit] admin@vsbc1%
Create a custom traffic profile with targeted transcode percentage and associate the transcode codec mix profile.
admin@vsbc1% set system sweTrafficProfiles loadTrafficProfile passthroughCodecProfile G711_20ms transcodePercent 30 transcodingCodecProfile loadProfile callHoldTime 25 useGPUForTranscoding true [ok][2020-06-15 11:52:09] [edit] admin@vsbc1% commit
admin@vsbc1% set system sweActiveProfile name loadTrafficProfile [ok][2020-06-15 11:52:56] [edit] admin@vsbc1% commit The following warnings were generated: 'system sweActiveProfile': To Activate the Profile system will be rebooted.All active calls will be lost during this process. Do you wish to continue? Proceed? [yes,no] yes
The instance reboots after activating the traffic profile. The SBC restarts with the loadTrafficProfile as the activated profile.