Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

...

width24px

...

...

Back to Table of Contents

Back to Installing SBC SWe Software

Back to Configuring Your Network for SBC SWe

Back to Creating Virtual Machine using vNetwork Standard Switch (vSwitch)

In this section:

Table of Contents
maxLevel2

 

To install the 

Spacevars
0product
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
Spacevars
0product
operating system and application software.

Note

You must follow the BIOS settings recommendations for the particular server.  Refer to BIOS Setting Recommendations section for guidance.

Note

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.

Create a Virtual Machine (VM)

Perform the following steps to create new

Spacevars
0product
VM.

  1. Login as user root on VMware vSphere client.

    1. Enter VM Ware host machine IP Address.
    2. Enter your VMware vSphere administrator user name.
    3. Enter your VMware vSphere administrator password. 
    Caption
    0Figure
    1VMware VSphere Client Login
    Image Modified

    The vSphere Client main window appears.

  2. In VMware vSphere Client main window, click Getting Started tab. Click Create a new virtual machine.

    Caption
    0Figure
    1New Virtual Machine Main
    Image Modified
  3. Select Custom in Configuration window, and click Next. Provide a Name for your

    Spacevars
    0product
    . The name can be up to 80 characters. Click Next.

    Note

    Avoid special characters for name. 

    Caption
    0Figure
    1Custom Configuration

    Image Modified



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

    Caption
    0Figure
    1Storage
    3

...

  1. Storage
    Image Modified



  2. Select Virtual Machine Version: 11. Refer to For VMware for more information.

    Caption
    0Figure
    1Selecting Virtual Machine Version

    Image Modified

  3. From Guest Operating System screen, make the following selections, and then click Next:

    1. Select Linux as the Guest Operating System.

    2. Select Debian GNU/Linux 6 (64-Bit) from Version drop-down menu.

      Caption
      0Figure
      1Guest Operating System

      Image Modified



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

    1. Number of Virtual sockets: 1

    2. Number of cores per virtual socket: 4 (depending on whether all virtual NICs are used)

      Caption
      0Figure
      1Creating Virtual CPUs

      Image Modified


      The following table provides the examples of socket determination based on the CPU and Cores per Socket:

      Caption
      0Table
      1Number of Sockets Determined by the vSphere Web Client
      Total Number of virtual CPUs (CPU)Cores per SocketNumber of Sockets Determined by the vSphere Web Client
      111
      221
      212
      441

...

    1. 422
      414
      881
      824
      842
      818

    2. From the Memory screen, assign memory for the virtual machine, and

...

    1. then click Next. Refer to Hardware and Software Requirements > For VMware for memory size requirements.

       

  1. Define Virtual Machine network interface connections (NICs) using following options from the drop-down menus. Then click Next to continue.

    Caption
    0Figure
    1Assigning NICs

    Image Modified

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

    2. Select second network adapter (NIC 2:) for HA interface. For example, the label can be HA.
    3. Select third network adapter  (NIC 3:) for packet interface 0. For example, the label can be PKT0.
    4. Select fourth network adapter (NIC 4:) for packet interface 1. For example, the label can be PKT1.

      Note

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

      Warning

      Make sure that Network Adapters are mapped exactly in the following order as shown below:

      • First network adapter (Network Adapter 1) for management interface
      • Second network adapter (Network Adapter 2) for high availability
      • Third network adapter (Network Adapter 3) for packet interface 0
      • Fourth network adapter (Network Adapter 4) for packet interface 1
    5. 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).

       

    6. Ensure all Connect at Power On check boxes are checked. This must be Power On always.

  2. From the SCSI Controller screen, select LSI Logic Parallel as the SCSI Controller option, then click Next to continue.

    Caption
    0Figure
    1Selecting SCSI Controller

    Image Modified



  3. From the Select a Disk screen, select Create a new virtual disk option, then click Next to continue.

  4. From the Create a Disk screen, make the selections described in the substeps below.

    Caption
    0Figure
    1Selecting Disk Provisioning Option

    Image Modified

    1. In Capacity section, assign

...

    1. at least 100 GB or more disk space.

       

    2. In Disk Provisioning section, choose only Thick provisioning Eager Zeroed option:

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

      2. ThickProvision Eager Zeroed (recommended) - Pre-allocates and dedicates a user defined amount of space for a VM disk operations.

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

    3. In Location section, select Specify a datastore or datastore cluster and click Browse...  Select the datastore or NFS where ISO image is available.

      Caption
      0Figure
      1Specifying Datastore

      Image Modified

    4. Click Next to continue.

  1. From the Advanced Options screen, keep the default value SCSI (0:0) and click Next. The default virtual device node is SCSI (0:0).

    Caption
    0Figure
    1Selecting Advance Option

    Image Modified



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

    Caption
    0Figure
    1Review and Complete

    Image Modified



  3. When you are satisfied with your settings, click Finish to complete the VM creation.

  4. The virtual machine is created under host IP address with the specified configuration. See example screen:

    Caption
    0Figure
    1Created VM

    Image Modified


    This creates the virtual machine.
     

  5. After VM is created, you must manually enable autostart and autostop of the Virtual Machine. Enabling the autostop/autostart of Virtual Machine is useful, in scenarios where power is lost and later regained. This setting of VM helps autostart of VMs when the host machine is powered ON.
    To autostart the VM, perform the following steps:
    1. Select the host IP address from left-pane and click Configuration Tab.

...

    1. The Virtual Machine Startup/Shutdown

...

    1. section is displayed.

      Caption
      0Figure
      1Virtual Machine Startup/Shutdown
      3Virtual Machine Startup/Shutdown

      Image Modified

    2. Click Properties link displayed towards the top-right window.

...

      1. In System Settings pane, you must ensure to select the Allow virtual machine to

...

      1. start and stop automatically with the system check box.

...

      1. By default it is selected.

        Caption
        0Figure
        1Enabling Auto Startup and Auto Shutdown of VM
        3Enabling Auto Startup and Auto Shutdown of VM

        Image Modified

...

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

        Caption
        0Figure
        1Moving VM to AutoStartup
        3Moving VM to AutoStartup
        Image Modified
      2. Click OK.
        This completes the autostartup and autoshutdown settings for the Virtual Machine.
Noprint
Panel

...

bgColortransparent
borderWidth2

 Continue to Adjust Resource Allocations for VM

 

Pagebreak