1. DSR Cloud Installation Guide
  2. Software Installation Procedure
  3. Configure Virtual Machines (OVM-S/OVM-M)

3.4 Configure Virtual Machines (OVM-S/OVM-M)

This procedure creates virtual machines. Repeat this procedure for each DSR VM guest that needs to be created.
Prerequisites:
This procedure requires values for these variables:
  • <OVA VM name_vm_vm>
  • <ServerPool name>
  • <VM name>
  • <OVM network ID for XMI>
  • <OVM network ID for IMI>
  • <OVM network ID for XSI#> where # is a numeric from 1-16, for the signaling networks
  • <OVM network ID for Replication XSI#>
  • <URL for OVM GUI>
  • <VM IP in XMI> from the NAPD
  • <Gateway for XMI> from the NAPD
  • <NetMask for XMI> from the NAPD
Running this procedure discovers and uses the values of these variables:
  • <VM ID>
  • <vCPUs Production>
  • <VNIC 1 ID>
  • <interface name> defined in DSR Cloud Benchmarking Guide
  1. In OVM-M CLI, create a VM for each guest from the VM in the OVA virtual appliance.
    1. Get the site-specific text for these variables (overwrite example).

      <OVA VM name_vm_vm> = 11145510c0_vm_vm

    2. Use the respective values for <OVA VM name> in the command.
      OVM> createVmFromVirtualApplianceVm VirtualApplianceVm name=<OVA VM name>
      Example:
      OVM> createVmFromVirtualApplianceVm VirtualApplianceVm name=11145510c0_vm_vm
    3. Run the command and validate success.
    4. Examine the screen results to find site-specific text for variables in these locations. 
      createVmFromVirtualApplianceVm VirtualApplianceVm name=11145510c0_vm_vm
Status: Success
Time: 2017-04-18 16:02:09,141 EDT
JobId: 1492545641976
Data:  
id: 0004fb00000600004a0e02bdf9fc1bcd 
name: DSR-8.6.0.0.0_95.14.0.ova_vm
    5. Use the respective values for these variables (overwrite example).

      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd

  2. In OVM-M CLI, add the VM to the server pool.
    1. Get the site-specific text for these variables (overwrite example).

      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd

      <ServerPool name> = XLab Pool 01

    2. Use the respective values for <VM ID> and <ServerPool name> in the command.
      OVM> add Vm id=<VM id> to ServerPool name=”<ServerPool name>”
      Example:
      OVM> add Vm id=0004fb00000600004a0e02bdf9fc1bcd to ServerPool name="XLab Pool 01"
    3. Run the command and validate success. 
      add Vm id=0004fb0000060000beb93da703830d3c to ServerPool name="XLab Pool 01"
Status: Success
Time: 2017-04-19 21:05:10,950 EDT
JobId: 1492650310802

      Note:

      Refer to Server Pool for more information.
  3. In OVM-M CLI, edit VM to apply required profile or resources.
    1. Get the site-specific text for these variables (overwrite example).

      <VM ID> = 0004fb00000600004a0e02bdf9fc1bcd

      <VM name > = na-noam-na-2a

      <vCPUs Production> = 4

    2. Refer to DSR Cloud Benchmarking Guide for recommended resource.

      Table 3-2 Recommended Resource

      VM Name vCPUs Lab RAM (GB) Lab vCPUs Production RAM (GB) Production Storage (GB) Lab and Production
      Type of guest host # # # # 3
    3. Use the respective values for <VM ID>, <VM name>, and <vCPUs Production> into the command.
      OVM> edit Vm id=<VM id> name=<VM name> memory=6144 memoryLimit=6144 cpuCountLimit=<vCPUs Production> cpuCount=<vCPUs Production> domainType=XEN_HVM description="<VM name>"
      Example:
      OVM> edit Vm id=0004fb00000600004a0e02bdf9fc1bcd name=na-noam-na-2a memory=6144 memoryLimit=6144 cpuCountLimit=4 cpuCount=4 domainType=XEN_HVM description="na-noam-na-2a"
    4. Run the command and validate success. 
      edit Vm id=0004fb00000600004a0e02bdf9fc1bcd name=na-noam-na-2a memory=6144 memoryLimit=6144 cpuCountLimit=4 cpuCount=4 domainType=XEN_HVM description="na-noam-na-2a"
Status: Success
Time: 2017-04-18 17:55:25,645 EDT
JobId: 1492552525477
      Now, the VM has a name and resources.
  4. In OVM-M CLI, determine VNIC ID.
    1. Get the site-specific text for these variables (overwrite example).

      <VM name> = na-noam-na-2a

    2. Use the respective value for <VM name> into the command.
      OVM> show Vm name=<VM name>
      Example:
      OVM> show Vm name=na-noam-na-2a
    3. Run the command and validate success.
    4. Examine the screen results to find site-specific text for variables in these locations.
      Status = Stopped
Memory (MB) = 6144
Max. Memory (MB) = 6144
Processors = 4
Max. Processors = 4
Priority = 50
Processor Cap = 100
High Availability = No
Operating System = Oracle Linux 6
Mouse Type = PS2 Mouse
Domain Type = Xen HVM
Keymap = en-us
Start Policy = Use Pool Policy
Origin = http://10.240.155.70/iso/DSR/8.6/ova/DSR-8.6.0.0.0_95.14.0.ova
Disk Limit = 4
Huge Pages Enabled = No
Config File Absolute Path = 192.168.5.5:/storage/ovm01/repository/VirtualMachines/0004fb00000600004a0e02bdf9fc1bcd/vm.cfg
Config File Mounted Path = /OVS/Repositories/0004fb0000030000da5738315337bfc7/VirtualMachines/0004fb00000600004a0e02bdf9fc1bcd/vm.cfg
Server Pool = 0004fb00000200009148c8926d307f05  [XLab Pool 01]
Repository = 0004fb0000030000da5738315337bfc7  [XLab Utility Repo01]
Vnic 1 = 0004fb0000070000091e1ab5ae291d8a [Template Vnic]
VmDiskMapping 1 = 0004fb0000130000a1996c6074d40563  [Mapping for disk Id (79def426328a4127b5bf9f7ae53d3f48.img)]
VmDiskMapping 2 = 0004fb00001300002db3d4b67a143ab5  [Mapping for disk Id (EMPTY_CDROM)]
Restart Action On Crash = Restart
Id = 0004fb00000600004a0e02bdf9fc1bcd [na-noam-na-2a]
Name = na-noam-na-2a
Description = na-noam-na-2a
Locked = false
DeprecatedAttrs = [Huge Pages Enabled (Deprecated for PV guest)]
    5. Use the respective values for these variables (overwrite example).

      <Vnic 1 ID> = 0004fb0000070000091e1ab5ae291d8a

  5. Determine network interfaces for the type of guest host.
    Refer to DSR Cloud Benchmarking Guide to learn which network interfaces need to be configured for each guest type. The following table provides details about the type of guest host:

    Table 3-3 Network Interfaces

      OAM (XMI) Local (IMI) Sig A (XSI1) Sig B (XSI2) Sig C (XSI3-16) Rep (SBR) DIH Internal
    Type of guest host eth# eth# eth# eth# eth# eth# eth#

    Note:

    The VNICs need to be created in the correct order so the interfaces are associated with the correct network.
  6. In OVM-M CLI, attach XMI VNIC (if required by guest host type).
    1. Get the site-specific text for these variables (overwrite example).

      <VNIC 1 ID> = 0004fb0000070000091e1ab5ae291d8a

      <OVM network ID for XMI> = 10345112c9

    2. Use the respective values for <VNIC 1 ID> and <OVM network ID for XMI> into the command.
      OVM> add Vnic ID=<Vnic 1 ID> to Network name=<OVM network ID for XMI>
      Example:
      OVM> add Vnic ID=0004fb0000070000091e1ab5ae291d8a to Network name=10345112c9
    3. Run the following command and validate success. 
      add Vnic id=0004fb0000070000091e1ab5ae291d8a to Network name=10345112c9
Status: Success
Time: 2017-04-19 19:08:59,496 EDT
JobId: 1492643339327
  7. In OVM-M CLI, create and attach IMI VNIC (if required by guest host type).
    1. Get the site-specific text for these variables (overwrite example).

      <VM name> = na-noam-na-2a

      <OVM network ID for IMI> = 102e89a481

    2. Use the respective values for <OVM network ID for IMI> and <VM name> into the command.
      OVM> create Vnic network=<OVM network ID for IMI> name=<VM name>-IMI on VM name=<VM name>
      Example:
      OVM> create Vnic network=102e89a481 name=na-noam-na-2a-IMI on Vm name=na-noam-na-2a
    3. Run the command and validate success.

      Command:

      create Vnic network=102e89a481 name=na-noam-na-2a-IMI on Vm name=na-noam-na-2a
Status: Success
Time: 2017-04-19 21:21:57,363 EDT
JobId: 1492651317194
Data:
id: 0004fb00000700004f16dc3bfe0750a7 
name:na-noam-na-2a-IMI
  8. In OVM-M CLI, create and attach XSI VNIC(s) (if required by guest host type).

    Note:

    Repeat this step if the VM has multiple signaling networks, specifying the number of the network.
    1. Get the site-specific text for these variables (overwrite example).

      <VM name> = hostname

      <OVM network ID for XSI#> = 1053a604f0

      <#> = the number of the XSI network [1-16]

    2. Use the respective values for <OVM network ID for XSI#> and <VM name> into the command.
      OVM> create Vnic network=<OVM network id for XSI#> name=<VM name>-XSI<#> on Vm name=<VM name>
      Example:
      OVM> create Vnic network=1053a604f0 name=hostname-XSI1 on Vm name=hostname
    3. Run the command and validate success.
  9. In OVM-M CLI, create and attach replication VNIC (if required by guest host type).
    1. Get the site-specific text for these variables (overwrite example).

      <VM name> = hostname

      <OVM network ID for Replication XSI#> = 10486554b5

      <OVM network name for Replication XSI#> = XSI7

      <#> = the number of the XSI Replication network [1-16]

    2. Use the respective values for <OVM network ID for Replication XSI#>, <OVM network name for Replication XSI#>, and <VM name> into the command.
      OVM> create Vnic network=<OVM network id for Replication XSI#> name=<VM name>-<OVM network name for Replication XSI#> on Vm name=<VM name>
      Example:
      OVM> create Vnic network=10486554b5 name= hostname-XSI7 on Vm name=hostname
    3. Run the command and validate success.
  10. In OVM-M CLI, start VM.
    1. Get the site-specific text for these variables (overwrite example).
      <VM name> = na-noam-na-2a
    2. Use the respective values for <VM name> into the command.
      OVM> start Vm name=<VM name>
      Example:
      OVM> start Vm name=na-noam-na-2a
    3. Run the command and validate success.
      Command:
      start Vm name=na-noam-na-2a
Status: Success
Time: 2017-04-19 19:29:35,376 EDT
JobId: 1492644568558
  11. In OVM-M GUI, configure the XMI network interface for this VM.
    1. Get the site-specific text for these variables (overwrite example).

      <URL for OVM GUI> = https://100.64.62.221:7002/ovm/console/faces/resource/resourceView.jspx

      <interface name> = from the table in DSR Cloud Benchmarking Guide

      <VM IP in XMI> = from the NAPD

      <Gateway for XMI> = from the NAPD

      <NetMask for XMI> = from the NAPD

    2. Access the CLI of the console for the VM.
    3. Log into the OVM-M GUI by typing the <URL for OVM GUI> into a browser.
      1. Navigate to the Servers and VMs tab.
      2. Expand and select the <ServerPool name>.
      3. From the Perspective list, select Virtual Machines.
      4. Select the <VM name> from the rows listed, and click the Launch Console icon.
      5. In the Console window, log into the VM as the admusr.
    4. Use the respective values for <interface name>, <VM IP in XMI>, <Gateway for XMI>, and <NetMask for XMI> into the commands.
      XMI:
      $ sudo netAdm set --onboot=yes --device=<interface name> --address=<VM IP in XMI> --netmask=<NetMask for XMI>
$ sudo netAdm add --route=default --device=<interface name> -–gateway=<Gateway for XMI>
      Example:
      $ sudo netAdm set --onboot=yes --device=eth0 --address=10.75.158.189 --netmask=255.255.255.128
      Example:
      $ sudo netAdm add --route=default --device=eth0 --gateway=10.75.158.129
    5. Run the command and validate success.
    6. Verify network connectivity by pinging Gateway of network.
      $ ping –c3 <Gateway for XMI>
    7. Reboot the VM. It takes approximately 5 minutes for the VM to complete rebooting.
      $ sudo init 6
      The new VM should now be accessible through both network and console.