Creating a New SBC SWe VM Instance

Creating a New SBC SWe VM Instance To install SBC SWe 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 SWe operating system and application software. Create a Virtual Machine (VM) Perform the following steps to create new SBC SWe VM. 1. Login as user root on VMWare vsphere client. a. b. c. Enter VM Ware host machine IP Address. Enter your VMWare vsphere administrator user name. Enter your VMWare vsphere administrator password. Figure 1: VMWare VSphere Client Login The vsphere Client main window appears. 2. In VMWare vsphere Client main window, click Getting Started tab. Click Create a new virtual machine. Figure 2: New Virtual Machine Main Copyright 2017 Sonus Networks. All rights reserved. Page 1

3. Select Custom in Configuration window, and click Next. Provide a Name for your SBC SWe. The name can be up to 80 characters. Click Ne xt. Avoid special characters for name. Figure 3: Custom Configuration Copyright 2017 Sonus Networks. All rights reserved. Page 2

4. From the Storage screen, select a datastore1 and click Next. Ensure datastore has at least 100 GB free space. This datastore is required to store all log-related data files. Figure 4: Datastore 5. Select Virtual Machine Version: 8. The SBC SWe can be installed only on VMware ESXi version 5.0 or later. Figure 5: Selecting Virtual Machine Version Copyright 2017 Sonus Networks. All rights reserved. Page 3

6. From Guest Operating System screen, make the following selections, and then click Next: a. Select Linux as the Guest Operating System. b. Select Debian GNU/Linux 6 (64-Bit) from Version drop-down menu. Figure 6: Guest Operating System 7. From CPUs screen, make following selections, and click Next. For CPU, memory configuration details, see Hardware and Software Requirements and Recommendations. a. Number of Virtual sockets: 1 Copyright 2017 Sonus Networks. All rights reserved. Page 4

b. Number of cores per virtual socket: 4. Figure 7: Creating Virtual CPUs c. From the Memory screen, assign memory for the virtual machine, and click Next. A minimum of 16 GB memory is required for each virtual machine. If the RAM is less than 5 GB, the host checker will fail the installation. 8. Define Virtual Machine network interface connections ( NICs) using following options from the drop-down menus. Then click Next to continue. Figure 8: Assigning NICs Copyright 2017 Sonus Networks. All rights reserved. Page 5

a. b. c. d. Select first network adapter ( NIC 1: ) for management interface. For example, the label can be MGMT which is created using Configur ing vnetwork Standard Switches (vswitches). Select second network adapter ( NIC 2: ) for HA interface. For example, the label can be HA. Select third network adapter ( NIC 3: ) for packet interface 0. For example, the label can be PKT0. 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: 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 e. f. 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. 9. From the SCSI Controller screen, select LSI Logic Parallel as the SCSI Controller option, then click Next to continue. Figure 9: Selecting SCSI Controller Copyright 2017 Sonus Networks. All rights reserved. Page 6

10. 11. From the Select a Disk screen, select Create a new virtual disk option, then click Next to continue. From the Create a Disk screen, make the following selections: Figure 10: Selecting Disk Provisioning Option a. In Capacity section, assign a minimum of 300 GB of disk space. If the disk size is less than 65 GB, the host checker will fail the installation. b. In Disk Provisioning section, choose only thick provisioning option: i. 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 Copyright 2017 Sonus Networks. All rights reserved. Page 7

zeroes to a virtual machine file system block until the first write within that region at run time. c. ii. ThickProvision Eager Zeroed (recommended) - Pre-allocates and dedicates a user defined amount of space for a VM disk operations. iii. 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 Location section, select Specify a datastore or datastore cluster and click Browse... Select the datastore or NFS where ISO image is available. Figure 11: Specifying Datastore 12. d. 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). Figure 12: Selecting Advance Option Copyright 2017 Sonus Networks. All rights reserved. Page 8

13. 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 Figure 13: Review and Complete 14. When you are satisfied with your settings, click Finish to complete the VM creation. 15. The virtual machine is created under host IP address with the specified configuration. See example screen: Copyright 2017 Sonus Networks. All rights reserved. Page 9

Figure 14: Created VM This creates the virtual machine. Adjust the resources depending on performance recommendations. Adjust Resource Allocations After creating VM, you have to adjust the VM resources depending on the Hardware and Software Requirements and Recommendations. Adjust the resource by executing the following steps: 1. Click your VM name. Click Resource Allocation tab. Click Edit in the CPU box. Figure 15: Selecting Resource Allocations Copyright 2017 Sonus Networks. All rights reserved. Page 10

3. Click Browse... Select the ISO image software file. For example, the ISO file name is sbc-v03.02.00r000-connexip-os_02.00.04-r000_am d64.iso. Click OK. Figure 17: Browse Datastore 4. Check the box to Connect at power on. Verify the ISO <sbc-xxx> file is listed. Figure 18: Verifying the ISO File Copyright 2017 Sonus Networks. All rights reserved. Page 12

5. Force the boot option to boot from ISO image and enter to BIOS setup screen. Click Edit in Resource Allocation tab and select Options tab. Select Boot Options. and check the Force BIOS Setup option. Figure 19: Force BIOS Selection 6. Reserve CPU speed. For details, see Hardware and Software Requirements and Recommendations. To allocate CPU speed, select Resourc Copyright 2017 Sonus Networks. All rights reserved. Page 13

es tab and select CPU as shown. In Reservation field enter the value or drag the reservation bar. Also ensure Unlimited check box is checked. Set CPU reservation to equal physical processor CPU speed multiplied by number of vcpus assigned to VM. For example, for 4 CPUs configuration, reserve "2932 * 4 = 11728 MHz". Figure 20: Reserve CPU Speed 7. Reserve minimum memory. For hardware requirements, see Hardware and Software Requirements and Recommendations. To reserve memory, select Resources tab and select Memory as shown. In Reservation field enter the value or drag the reservation bar and click OK. Also ensure Unlimited check box is checked. Configure a minimum Physical memory of 5 GB to allow the SWe Application to come up and make a test call. Sonus recommends reserving 16 GB of memory for the production environment. Figure 21: Reserve Memory Copyright 2017 Sonus Networks. All rights reserved. Page 14