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.
This chapter contains the following sections:
You can define global VLANs in the domain group root, or a domain group below the root. Global VLANs can only be common or global. You cannot assign them to a specific fabric interconnect.
Resolution of global VLANs takes place prior to the deployment of global service profiles. If a global service profile references a global VLAN, and that VLAN does not exist, deployment of the global service profile fails due to insufficient resources. All global VLANs created in a Cisco UCS Central account must be resolved before deploying the global service profile.
All global VLANs configured in a Cisco UCS Central account are common to the domains in which they are created. However, organization permissions must first be assigned before the Cisco UCS domains that are part of the organizations can consume the resources. By default, no organization permissions are assigned when you create a global VLAN. Once organization permissions have been granted to a VLAN, it becomes visible to those organizations. It is also available to be referenced in service profiles that are part of those organizations.
A global VLAN is visible to a Cisco UCS Manager account only if you deploy a global service profile that references the VLANs. Once a VLAN that is deployed with a global service profile becomes available in a Cisco UCS Manager account, you can include it in a local service profile and policy. You cannot turn a global VLAN into a local VLAN.
A global VLAN is not deleted when you delete a global service profile that references it. Delete the global VLAN from the Cisco UCS Central account.
Global VLANs can be published to the associated domains, and those VLANs are then available at domain level. For a VLAN associated to a domain group (x), it can be published to any of the domains linked with the same domain group (x).
IP pools are a collection of IP addresses. You can use IP pools in Cisco UCS Central in one of the following ways:
A MAC pool is a collection of network identities, or MAC addresses, that are unique in their Layer 2 environment and are available to be assigned to vNICs on a server. If you use MAC pools in service profiles, you do not have to manually configure the MAC addresses to be used by the server associated with the service profile.
In a system that implements multitenancy, you can use the organizational hierarchy to ensure that MAC pools can be used only by specific applications or business services. Cisco UCS uses the name resolution policy to assign MAC addresses from the pool.
To assign a MAC address to a server, you must include the MAC pool in a vNIC policy. The vNIC policy is then included in the service profile assigned to that server.
You can specify your own MAC addresses or use a group of MAC addresses provided by Cisco.
Step 1 | On the menu bar, choose . | ||||||||||||
Step 2 | In the left pane, expand Multi-Domain Managers. | ||||||||||||
Step 3 | In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account. | ||||||||||||
Step 4 | In the right pane, click the Organizations tab. | ||||||||||||
Step 5 | Click the organization in which you want to create the pool and then click View Details. | ||||||||||||
Step 6 | Click the MAC Pools tab. | ||||||||||||
Step 7 | Click Add. | ||||||||||||
Step 8 | In the
Add MAC
Pool dialog box, complete the following fields:
| ||||||||||||
Step 9 | Click Submit. |
Step 1 | On the menu bar, choose . | ||||||||
Step 2 | In the left pane, expand Multi-Domain Managers. | ||||||||
Step 3 | In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account. | ||||||||
Step 4 | In the right pane, click the Organizations tab. | ||||||||
Step 5 | Click the organization in which you want to modify the pool and then click View Details. | ||||||||
Step 6 | Click the MAC Pools tab. | ||||||||
Step 7 | Click the pool to which you want to add a block of addresses and then click Create a Block of MAC Addresses. | ||||||||
Step 8 | In the
Add MAC
Pool Block dialog box, complete the following fields:
| ||||||||
Step 9 | Click Submit. |
This policy defines how a vNIC on a server connects to the LAN. This policy is also referred to as a vNIC LAN connectivity policy.
A VM-FEX port profile is not automatically created with the correct settings when you create a vNIC template. If you want to create a VM-FEX port profile, you must configure the target of the vNIC template as a VM.
You need to include this policy in a service profile for it to take effect.
Note | If your server has two Emulex or QLogic NICs (Cisco UCS CNA M71KR-E or Cisco UCS CNA M71KR-Q), you must configure vNIC policies for both adapters in your service profile to get a user-defined MAC address for both NICs. If you do not configure policies for both NICs, Windows still detects both of them in the PCI bus. Because the second Ethernet interface is not part of your service profile, Windows assigns it a hardware MAC address. If you then move the service profile to a different server, Windows sees additional NICs because one NIC did not have a user-defined MAC address. |
One or more of the following resources must exist:
Step 1 | On the menu bar, choose . | ||||||||||||||||
Step 2 | In the left pane, expand Multi-Domain Managers. | ||||||||||||||||
Step 3 | In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account. | ||||||||||||||||
Step 4 | In the right pane, click the Organizations tab. | ||||||||||||||||
Step 5 | Click the organization in which you want to create the policy and then click View Details. | ||||||||||||||||
Step 6 | Click the vNIC Templates tab. | ||||||||||||||||
Step 7 | Click Add. | ||||||||||||||||
Step 8 | In the Add vNIC Template dialog box, enter a unique name and description for the policy. | ||||||||||||||||
Step 9 | From the Fabric ID drop-down list, choose the fabric interconnect that you want to associate with vNICs created from this template. | ||||||||||||||||
Step 10 | Check the
Enable
Failover check box if you want vNICs created from this template to
be able to access the other fabric interconnect if the chosen one is
unavailable.
| ||||||||||||||||
Step 11 | Check one or both of the following Target check boxes to determine whether or not a VM-FEX port profile is automatically created with the appropriate settings for the vNIC template: | ||||||||||||||||
Step 12 | From the Template Type drop-down list, choose one of the following: | ||||||||||||||||
Step 13 | In the
VLANs area, do the following to select the VLAN to
be assigned to vNICs created from this template:
| ||||||||||||||||
Step 14 | To associate
policies with vNICs created from this template, complete the following fields:
| ||||||||||||||||
Step 15 | Click Submit. |
Include the vNIC template in a vNIC policy.
Make sure that at least one of the following exists in the Cisco UCS Central account and organization to which this policy applies:
Step 1 | On the menu bar, choose, Policies > Physical Infrastructure Policies > UCS Central |
Step 2 | Click the vNIC Policy tab. |
Step 3 | Click Add. |
Step 4 | In the
Create
UCS Central vNIC Policy dialog box, do the following:
|
Include the vNIC policy in a network policy.
LAN connectivity policies determine the connections and the network communication resources between the server and the LAN on the network. These policies use pools to assign MAC addresses to servers and to identify the vNICs that the servers use to communicate with the network.
Note | We do not recommend that you use static IDs in connectivity policies because these policies are included in service profiles and service profile templates and can be used to configure multiple servers. |
Step 1 | On the menu bar, choose . |
Step 2 | In the left pane, expand Multi-Domain Managers. |
Step 3 | In the left pane, expand UCS Central Accounts and then click the Cisco UCS Central account. |
Step 4 | In the right pane, click the Organizations tab. |
Step 5 | Click the organization in which you want to create the policy and then click View Details. |
Step 6 | Click the LAN Connectivity Policies tab. |
Step 7 | Click Add. |
Step 8 | In the LAN Connectivity Policy dialog box, enter a name and description for the policy. |
Step 9 | In the
vNICs table, click
Add and do the following:
Repeat this step if you want to add more vNICs to the policy. |
Step 10 | After you have created all vNICs required for the policy, click Submit. |
The network policy is a Cisco UCS Director policy that configures the connections between a server and the LAN, including the virtual network interface cards (vNICs) used by the server. Depending upon the configuration you choose, this policy can be used to configure two or more vNICs for the server. You can choose to create the vNICs in this policy or use a LAN connectivity policy to determine the vNIC configuration.
You must include this policy in a service profile and that service profile must be associated with a server for it to take effect.
Step 1 | On the menu bar, choose Policies > Physical Infrastructure Policies > UCS Central | ||||||||||||
Step 2 | Click the Network Policy tab. | ||||||||||||
Step 3 | Click Add. | ||||||||||||
Step 4 | In the Create UCS Central Network Policy dialog box, enter a name and description for the policy. | ||||||||||||
Step 5 | Complete the following fields to specify the Cisco UCS Central connections for the policy: | ||||||||||||
Step 6 | If this policy is to be assigned to service profiles for servers that support dynamic vNICs, choose a dynamic vNIC connection policy from the Dynamic vNIC Connection Policy drop-down list. | ||||||||||||
Step 7 | From the
LAN
Connectivity Type drop-down list, choose one of the following
connectivity types:
| ||||||||||||
Step 8 | If you chose the expert LAN option, do the following: | ||||||||||||
Step 9 | If you chose the
simple LAN option, do the following:
| ||||||||||||
Step 10 | If you chose the LAN connectivity policy option, choose the policy that you want to associate with the server from the LAN Connectivity Policy drop-down list. | ||||||||||||
Step 11 | Click Submit. |
Include the network policy in a service profile.