Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.1

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.1

Chapter Title

Configuring a Service Profile with VM-FEX

Results

Updated:
November 16, 2012

Chapter: Configuring a Service Profile with VM-FEX

Configuring a Service Profile with VM-FEX

This chapter includes the following sections:

Configuring Dynamic vNIC Connection Policies

Dynamic vNIC Connection Policy


Note

In an SR-IOV topology, such as a Hyper-V or KVM cluster, a Virtual Function (VF) takes the place of the dynamic vNIC. The VF is essentially a restricted version of the dynamic vNIC, in which all system communication and configuration of the VF is performed through the associated physical function (PF).

The dynamic vNIC connection policy determines how the connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS domains that include servers with VIC adapters on which you have installed VMs and configured dynamic vNICs.

Ethernet Adapter Policy

Each dynamic vNIC connection policy includes an Ethernet adapter policy and designates the number of vNICs that can be configured for any server associated with a service profile that includes the policy.

For KVM, use the predefined Ethernet adapter policy named Linux.

Static vNICs


Note

In a VM-FEX deployment, a VM will attach to a dynamic vNIC only if the VIC adapter has two static vNICs, one for each fabric. If a server contains more than one VIC adapter, each adapter must have two static vNICs configured.

Server Migration


Note

If you migrate a server that is configured with dynamic vNICs, the dynamic interface used by the vNICs fails and notifies you of that failure.

When the server comes back up, assigns new dynamic vNICs to the server. If you are monitoring traffic on the dynamic vNIC, you must reconfigure the monitoring source.

Creating a Dynamic vNIC Connection Policy

You can create a dynamic vNIC connection policy.

Procedure
    Step 1   In the Navigation pane, click the LAN tab.
    Step 2   On the LAN tab, expand LAN > Policies.
    Step 3   Expand the node for the organization where you want to create the policy.

    If the system does not include multitenancy, expand the root node.

    Step 4   Right-click the Dynamic vNIC Connection Policies node and choose Create Dynamic vNIC Connection Policy.
    Step 5   In the Create Dynamic vNIC Connection Policy dialog box, complete the following fields:
    Name Description

    Name field

    The name of the policy.

    This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved.

    Note   

    Do not specify "default" as the value for the dynamic vNIC connection policy name. Cisco UCS Manager automatically resolves any empty policy references to "default". Any service profiles or service profile templates with only static vNICS defined will automatically reference the policy "default" when it is present. If you specify “default” for the dynamic vNIC connection policy name, then unexpected dynamic vNICs might be created on those service profiles or service profile templates.

    Description field

    A description of the policy. We recommend that you include information about where and when the policy should be used.

    Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

    Number of Dynamic vNICs field

    The number of dynamic vNICs that this policy affects.

    Enter an integer between 0 and 256. The default is 54.

    Note   

    Components of your system might limit this number to fewer than 256 vNICs.

    Adapter Policy drop-down list

    The adapter profile associated with this policy. The profile must already exist to be included in the drop-down list.

    Protection field

    Dynamic vNICs are always protected in Cisco UCS, but this field allows you to select a preferred fabric, if any. You can choose one of the following:

    • Protected Pref A—Cisco UCS attempts to use fabric A but fails over to fabric B if necessary
    • Protected Pref B—Cisco UCS attempts to use fabric B but fails over to fabric A if necessary
    • Protected—Cisco UCS uses whichever fabric is available
    Step 6   Click OK.
    Step 7   If a confirmation dialog box appears, click Yes.

    Changing a Dynamic vNIC Connection Policy

    You can change a dynamic vNIC connection policy.

    Procedure
      Step 1   In the Navigation pane, click the LAN tab.
      Step 2   On the LAN tab, expand LAN > Policies.
      Step 3   Expand the node for the organization that contains the policy that you want to change.

      If the system does not include multitenancy, expand the root node.

      Step 4   Expand the Dynamic vNIC Connection Policies node and click the policy that you want to change.
      Step 5   In the Work pane, click the General tab.
      Step 6   Change one or more of the following fields:
      Name Description

      Description field

      A description of the policy. We recommend that you include information about where and when the policy should be used.

      Number of Dynamic vNICs field

      The number of dynamic vNICs that this policy affects.

      Adapter Policy drop-down list

      The adapter profile associated with this policy. The profile must already exist to be included in the drop-down list.

      You cannot change the other properties of the policy, such as the Name field.
      Step 7   Click Save Changes.
      Step 8   If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

      Deleting a Dynamic vNIC Connection Policy

      You can delete a dynamic vNIC connection policy.

      Procedure
        Step 1   In the Navigation pane, click the LAN tab.
        Step 2   On the LAN tab, expand LAN > Policies > Organization_Name.
        Step 3   Expand the Dynamic vNIC Connection Policies node.
        Step 4   Right-click the policy that you want to delete and choose Delete.
        Step 5   If the Cisco UCS Manager GUI displays a confirmation dialog box, click Yes.

        Viewing Dynamic vNIC Properties in a VM

        You can view dynamic vNIC properties in a VM.

        Before You Begin

        The VM must be operational.

        Procedure
          Step 1   In the Navigation pane, click the VM tab.
          Step 2   On the VM tab, expand All > Clusters.
          Step 3   Expand Virtual Machines.
          Step 4   Expand the virtual machine that contains the dynamic vNIC.
          Step 5   Choose the dynamic vNIC.
          Step 6   In the Work pane, click the General tab.

          In the Properties area, the vNIC properties appear.

          Was this Document Helpful?

          FeedbackFeedback

          Contact Cisco