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 describes how to configure port profile inheritance, including the following:
•Information About Port Profile Inheritance
•Inheriting a Configuration from a Port Profile
•Removing Inherited Policies from a Port Profile
You can apply the configuration from an existing port profile as the default configuration for another port profile. This is called inheritance. The configuration of the parent port profile is copied to and stored in the child port profile. You can also override the inheritance by configuring the attributes explicitly in the child port profile.
Table 3-1 lists the port profile settings and shows whether they can be inherited.
Follow these guidelines and limitations when configuring port profile inheritance:
•Inherited port profiles cannot be changed or removed from an interface using the Cisco Nexus 1000V CLI. This can only be done through the vCenter Server.
•Inherited port profiles are automatically configured by the Cisco Nexus 1000V when the ports are attached on the hosts. This is done by matching up the VMware port group assigned by the system administrator with the port profile that created it.
•You can change a setting directly on a port profile to override the inherited settings.
•You can also explicitly remove port profile inheritance, so that a port profile returns to the default settings, except where there has been a direct configuration. For more information, see the "Removing Inherited Policies from a Port Profile" procedure.
•The Cisco Nexus 1000V software must be initially configured. For information, see the Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4).
•The Cisco Nexus 1000V must be connected to the vCenter Server.
•Once a port profile is created, you cannot change its type (Ethernet or vEthernet).
You can use this procedure to apply the configuration from an existing port profile as the default configuration for another port profile.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•To identify the port profile with a configuration you want to use, use the following command to view your existing port profiles:
–show port profiles
•You are familiar with the port profile characteristics shown in Table 3-1, and whether they can be inherited.
•The port profile type cannot be inherited from another port profile.
1. config t
2. port-profile [type {ethernet | vethernet}] name
3. inherit port-profile name
4. show port-profile [brief | expand-interface | usage] [name profile-name]
5. copy running-config startup-config
This example shows how to inherit the port profile configuration of another port profile:
n1000v# config t
n1000v(config)# port-profile AllAccess2
n1000v(config-port-prof)# inherit port-profile AllAccess1
n1000v(config-port-prof)# show port-profile name AllAccess2
port-profile AllAccess2
description:
type: vethernet
status: disabled
capability l3control: no
pinning control-vlan: -
pinning packet-vlan: -
system vlans: none
port-group:
max ports: 32
inherit: port-profile AllAccess1
config attributes:
evaluated config attributes:
assigned interfaces:
n1000v(config-port-prof)#
You can use this procedure to remove the inherited policies from a port profile.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in configuration mode.
•If you have configured policies independently of inheritance, then they will not be removed when you remove the inheritance. Only the policies that are configured solely through the inheritance are removed.
1. config t
2. (Optional) show port-profile virtual usage name profile_name
3. no inherit port-profile profile_name
4. (Optional) show port-profile virtual usage name profile_name
5. copy running-config startup-config