3.2.3 Configure Remaining DSR Guests Based on Resource Profile and Configure Network (KVM/OpenStack Only)

This procedure adds network addresses for all VMs.

Note:

This procedure provides an example for creating an SOAM. Follow the same steps to create other guests with their respective VM names and profiles.
  1. Name the new VM instance.
    1. Create an informative name for the new instance: SOAM1.
    2. Examine the DSR Network to Device Assignments defined in DSR Cloud Benchmarking Guide.
  2. Create and boot the SOAM VM instance from the glance image.
    1. Get the following configuration values.
      The image ID
      $ glance image-list
      The flavor ID
      $ nova flavor-list
      The network ID(s)
      $ neutron net-list
      An informative name for the instance:
      • SOAM1
      • SOAM2
    2. Create and boot the VM instance.
      The instance must be owned by the DSR tenant user, not the admin user. Source the credentials of the DSR tenant user and issue the following command. Use one --nic argument for each IP/interface. Number of IP/interfaces for each VM type must conform with the DSR Network to Device Assignments defined in DSR Cloud Benchmarking Guide.

      Note:

      IPv6 addresses should use the v6-fixed-ip argument instead of v4‑fixed-ip.
      $ nova boot --image <image ID> --flavor <flavor id> --nic net-id=<first network id>,v4-fixed-ip=<first ip address> --nic net-id=<second network id>,v4-fixed-ip=<second ip address> <instance name>
    3. View the newly created instance using the nova tool.
      $ nova list --all-tenants
      The VM takes approximately 5 minutes to boot and may be accessed through both network interfaces and the Horizon console tool.
  3. Configure SOAM VIP.
    This is an optional step.

    Note:

    Refer to Allowed Address Pairs for more information on VIP.
    If an SOAM VIP is needed, run the following commands:
    1. Find the port ID associated with the SOAM instance XMI interface.
      $ neutron port-list
    2. Add the VIP IP address to the address pairs list of the SOAM instance XMI interface port.
      $ neutron port-update <Port ID> --allowed_address_pairs list=true type=dict ip_address=<VIP address to be added>
  4. Check if interface is configured.
    If DHCP is enabled on Neutron subnet, VM configures the VNIC with the IP address provided in step 2 above.
    To verify, ping the XMI IP address provided with nova boot… command (step 2):
    $ ping <XMI-IP-Provided-During-Nova-Boot>
    If the ping is successful, ignore step 5.
  5. Manually configure interface, if not already done.
    This is an optional step.

    Note:

    If the instance is already configured with an interface and successfully pinging (step 4), then ignore this step to configure the interface manually.
    1. Log in to the Horizon GU I as the DSR tenant user.
    2. Go to the Compute/Instances section.
    3. Click the Name field of the newly created instance.
    4. Select the Console tab.
    5. Log in as the admusr user.
    6. Configure the network interfaces, conforming with the DSR Network to Device Assignments defined in DSR Cloud Benchmarking Guide.
      $ sudo netAdm add --onboot=yes --device=eth0 --address=<xmi ip> --netmask=<xmi net mask>
      
      $ sudo netAdm add --route=default --device=eth0 --gateway=<xmi gateway ip>

      Verify network connectivity by pinging Gateway of XMI network.

      $ ping –c3 <XMI Gateway>

      Under some circumstances, it may be necessary to configure as many as 6 or more interfaces.

  6. Reboot the SOAM 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 Horizon consoles.

  7. Verify network connectivity.
    1. Access the SOAM1 VM console using OpenStack.
    2. Log in as the admusr user.
    3. Ping the NOAM1.
      $ ping –c3 <IP Address in External Management Network>
    Repeat above for the following VMs. Use unique labels for the VM names. Assign addresses to all desired network interfaces:
    • MP(s)
    • IPFE(s)
    • MP vSTP (For vSTP configuration) (Optional Components)
    • SOAM(s)
    • Session SBRs, Binding SBR (Optional Components)
    • DR NOAMs (Optional Components)