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:
To install the SBC on a virtual machine (VM), you must first create a VM and allocate its resources (for example CPU, memory, and NICs), as well as configure a datastore to contain the SBC operating system and application software.
You must follow the BIOS settings recommendations for the particular server. Refer to BIOS Setting Recommendations section for guidance.
Make sure all your NICs are physically plugged in (link light on) before creating your VM. Otherwise, when you perform the ISO, an incorrect port mapping occurs (logical to physical), and your SBC does not function properly.
Perform the following steps to create new SBC VM.
Login as user root on VMware vSphere client.
The vSphere Client main window appears.
The figures shown in this procedure are intended as examples of the user interface and might not match the presented images exactly.
In VMware vSphere Client main window, click Getting Started tab. Click Create a new virtual machine.
Select Custom in Configuration window, and click Next. Provide a Name for your SBC. The name can be up to 80 characters. Click Next.
Avoid special characters for name.
From the Storage screen, select a datastore1 and click Next. Ensure datastore has at least 100 GB or more space. This datastore is required to store all log-related data files.
Select Virtual Machine Version: 11. Refer to For VMware for more information.
From Guest Operating System screen, make the following selections, and then click Next:
Select Linux as the Guest Operating System.
Select Debian GNU/Linux 9 (64-Bit) from Version drop-down menu.
From CPUs screen, make following selections, and click Next. (In the following screenshot example, 4 cores are chosen). For CPU, memory configuration details, see For VMware.
Number of Virtual sockets: 1
Number of cores per virtual socket: 4 (depending on whether all virtual NICs are used)
From the Memory screen, assign memory for the virtual machine, and then click Next. Refer to Hardware and Software Requirements > For VMware for memory size requirements.
The figures shown in this procedure are intended as examples of the user interface and might not match the presented images exactly.
Define Virtual Machine network interface connections (NICs) using following options from the drop-down menus. Then click Next to continue.
Select first network adapter (NIC 1:) for management interface. For example, the label can be MGMT which is created using Configuring vNetwork Standard Switches (vSwitches).
Select fourth network adapter (NIC 4:) for packet interface 1. For example, the label can be PKT1.
These network adapters and labels are already created on the ESX host server. If you are installing for the first time on new ESX host server, these network adapters and corresponding labels (MGMT, HA, PKT0, PKT1) needs to be created. For details, see Configuring vNetwork Standard Switches (vSwitches).
Make sure that Network Adapters are mapped exactly in the following order as shown below:
Select Adapter type as VMXNET 3 for all interfaces (The VMXNET 3 virtual network adapter has no physical counterpart. VMXNET is optimized for performance in a virtual machine).
Ensure all Connect at Power On check boxes are checked. This must be Power On always.
From the SCSI Controller screen, select LSI Logic Parallel as the SCSI Controller option, then click Next to continue.
From the Select a Disk screen, select Create a new virtual disk option, then click Next to continue.
From the Create a Disk screen (not shown), make the selections described in the substeps below.
In the Capacity section, assign at least 100 GB or more disk space.
In the Disk Provisioning section, choose only the Thick provisioning Eager Zeroed option:
Thick Provision Lazy Zeroed - Allocates the requested hard disk (virtual) during the VM creation. This type of disk pre-allocates and dedicates a pre-defined amount of a space for a virtual machine's disk operations, but it does not write zeroes to a virtual machine file system block until the first write within that region at run time.
Thick Provision Eager Zeroed (recommended) - Pre-allocates and dedicates a user defined amount of space for a VM disk operations.
Thin Provision - Creates virtual hard disk during runtime (on write operations). This provides more optimal hard disk usage, but it has some performance impact until it creates maximum requested virtual hard disk.
In the Location section, select Specify a datastore or datastore cluster and click Browse... The Select a datastore or datastore cluster screen (below) opens. Select the datastore or NFS where the ISO image is available and click OK.
Click Next to continue.
From the Advanced Options screen, keep the default value SCSI (0:0) and click Next. The default virtual device node is SCSI (0:0).
From the summary screen, review your VM settings and click Finish. If needed, click Back to return to the screen in question and make necessary adjustments
When you are satisfied with your settings, click Finish to complete the VM creation.
The virtual machine is created under host IP address with the specified configuration. See example screen:
This creates the virtual machine.
Select the host IP address from left-pane and click Configuration Tab. The Virtual Machine Startup/Shutdown section is displayed.
Click Properties link displayed towards the top-right window.
In System Settings pane, you must ensure to select the Allow virtual machine to start and stop automatically with the system check box. By default it is selected.
In Startup Order pane, select the VM, which you want to automatically start and click Move Up.
The selected VM is displayed underneath Automatic Startup.