3.1.3 Configure Remaining DSR Guests Based on Resource Profile and Configure Network

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. Create the SOAM1 VM from the OVA image.
   1. Browse to the library or repository where the OVA image is placed.
   2. Deploy the OVA Image by using vSphere Client or vSphere Web Client.
   3. Name the SOAM1 VM and select the data store.
2. Configure the SOAM1 VM as per the resource profiles defined in DSR Cloud Benchmarking Guide for the DSR SO using the vSphere Client or vSphere Web Client. Interfaces must be added per the OCDSR Network to Device Assignments defined in DSR Cloud Benchmarking Guide.
3. Power ON SOAM1 VM.
   1. Power ON the DSR SOAM1 VM with the vSphere Client or vSphere Web Client.
   2. Monitor the vApps screen’s Virtual Machines tab until the DSR VM reports Powered On in the Status column.
4. Configure XMI interface.
   1. Access the VM console through the vSphere Client or vSphere Web Client.
   2. Login as the admusr user.
   3. Set the ethX device:

      $ sudo netAdm add --device=<ethX> --address=<IP Address in External Management Network> --netmask=<Netmask> --onboot=yes --bootproto=none

      Note:

      Where ethX is the interface associated with the XMI network.
   4. Add the default route for ethX:

      $ sudo netAdm add --route=default --gateway=<gateway address for the External management network> --device=<ethX>

5. Verify network connectivity.
   1. Access the SOAM1 VM console using the vSphere Client or vSphere Web Client.
   2. Login as the admusr user.
   3. Ping the NOAM1.

      $ ping –c3 <IP Address in External Management Network>

Note:

Repeat the above procedure for the following VMs. Use unique labels for the VM names:

• MP(s)
• IPFE(s)
• SOAM(s)
• Session SBRs, Binding SBR (Optional Components)
• DR NOAMs (Optional Components)