Thursday Jun 26, 2014

Creating A Secondary I/O domain with Ops Center 12.2

Contributed by Juergen Fleischer and Mahesh Sharma.

The purpose of this blog is to show you how to create a Secondary I/O domain. The First I/O domain is commonly known as Control Domain (CDOM). There are various terms that are used for a Secondary domain, like alternative I/O domain or redundant I/O domain.

The secondary I/O domain will have been assigned some physical I/O devices, which may be a PCIe bus root complex, a PCI device, or a SR-IOV (Single Root I/O Virtualization) virtual function.

Within Ops Center when creating a Secondary Domain we also use the terms Physical I/O Domain and Root Domain. The Physical I/O Domain maps PCI device end points, and the Root Domain maps PCIe buses, which also has an option to create SR-IOV functions.

In this blog we will show you how to create a Root Domain by assigning PCIe buses, so that we have a redundant I/O domain which will enable us to shutdown the CDOM without affecting any of our guests.

Our host a T5-2 (we’re using the same host as in the previous blogs) has two free PCIe buses that have not been assigned to domains (pci_2 and pci_3). So let’s create a Secondary I/O domain (Root Domain) with these buses and give the domain two whole cores with 4 GB of Memory.

We’ll start by creating a Logical Domain Profile. This is created from:

Navigation -> Plan Management -> Profiles and Polices, then click on Logical Domain. On the right under Actions select Create Profiles

From the Identify Profile screen, give the Profile a name (Secondary-I/O in our case) and select Root Domain in the Sub-type, as shown above. Click Next.

Step 2: is where we provide a name for our Secondary I/O domain, we called ours secondary and click Next to continue.

The next screen, show below, we entered the amount of cores and memory.

 Step 4: is where we specify how many PCIe buses we will assign to this secondary domain. In our cases we have specified two for  pci_2 and pci_3.

The next few steps are optional and are not required for this example.

Step 7: Is the Summary, if everything looks correct click Finish.

Note: The Metadata is on the local disk (file://guest). This is fine for the Secondary Domain as it will not be migrated. It’s just the Logical domains and their Guests that will get migrated, therefore making it mandatory to have the metadata on shared storage for these – if you want migration to succeed!

Now that we have created the Profile, we will create our Secondary domain (Root domain).

This is done from Navigation -> Plan Management -> Deployment Plans – Create Logical Domain and select the plan we have just created. From the Actions panel on the right select "Apply Deployment Plan".

From the Select Target Asset pop-up, select the CDOM and move it to the Target list. Select Next.

Complete Step 1, by specifying the secondary name.

Step 2, we pick the PCIe Buses that will be assigned to the secondary domain.

In step 3: we kept the default Virtual Disk Sever (vds) name.

The next few screens are not required in this example.

From the Summary screen click Finish. This will create the Secondary Domain.

Once the Secondary Domain has been created we can check if it’s built as we specified. We can check via the Ops Center BUI and also command line.

Let’s do both:

And from the command line

While on the command line we can also check if the buses have been assigned correctly.