Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco Nexus 1000V for KVM Port Profile Configuration Guide, Release 5.x

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Nexus 1000V for KVM Port Profile Configuration Guide, Release 5.x

Chapter Title

Creating Basic Port Profiles

Results

Updated:
November 8, 2015

Chapter: Creating Basic Port Profiles

Creating Basic Port Profiles

This chapter contains the following sections:

Information About Creating Port Profiles

You can create Ethernet or virtual Ethernet (vEthernet) type port profiles.

When you configure Ethernet port profiles, you must configure all attributes; however, when you configure vEthernet port profiles, you configure some attributes in the port profile on the Virtual Supervisor Module (VSM) and other attributes in the network profile on the OpenStack controller. For example, you configure the port profiles with VLANs and VXLANs on the OpenStack controller.

After creating and configuring the port profile, you must enable it so that its configuration is applied to the assigned ports and the port profile is placed in an operational state.

Finally, you must publish the port profile. When you publish an Ethernet type port profile, the port profile configuration is pushed to the VEMs. When you publish a vEthernet type port profile, the port profile configuration is pushed to the VEMs as well as to the OpenStack controller, where the port profile and network profile configurations are combined to automatically generate the configuration that is applied to the vEthernet interface. You cannot modify or delete these automatically generated and dynamic port profiles. For more information about these port profiles, see the Cisco Nexus 1000V for KVM Virtual Network Configuration Guide.

Guidelines and Limitations for Creating Port Profiles

  • Once you create a port profile as either an Ethernet or vEthernet type, you cannot change the type.

  • The channel-group command is not supported by vEthernet type port profiles.

  • In an installation where multiple Ethernet port profiles are active on the same Virtual Ethernet Module (VEM), we recommend that they do not carry the same VLAN(s). The allowed VLAN list should be mutually exclusive. You can configure overlapping VLANs but they might cause duplicate packets to be received by virtual machines in the network.

  • To maintain consistency between the port profile definition and what is applied to an interface, if a port profile modification is rejected by any port, the modification is rejected by the port profile too.

  • A maximum transmission unit (MTU) can only be configured for uplink Ethernet type port profiles.

  • User-configured port profile inheritance is not supported on the Cisco Nexus 1000V for KVM.

Default Settings

The following table lists the default settings in the port profile configuration.

Parameter

Default

cdp

Enabled

description

None

max-ports

512

min-ports

1

shutdown

All ports administratively disabled

state

Disabled

type

vEthernet

Creating a Basic Ethernet Port Profile

Before You Begin

  • You are logged in to the CLI in EXEC mode.

  • You know whether the ports need to be initialized with system settings.

  • You have identified the characteristics needed for this port profile.

Procedure
     Command or ActionPurpose
    Step 1switch# configure terminal  

    Enters global configuration mode.

     
    Step 2switch(config)# port-profile type ethernet name  

    Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created. Once configured, the type cannot be changed. Defining an Ethernet type port profile allows the port profile to be used for physical (Ethernet) ports.

     
    Step 3switch(config-port-prof)# channel-group auto mode on   (Optional)

    Configures the port-channels in the port profile.

     
    Step 4switch(config-port-prof)# no shutdown  

    Enables all ports in the port profile.

     
    Step 5switch(config-port-prof)# state enabled  

    Enables the operational state of the port profile.

     
    Step 6switch(config-port-prof)# publish port-profile [name]  

    Pushes the port profile to the VEMs.

     
    Step 7switch(config-port-prof)# copy running-config startup-config   (Optional)

    Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

     

    This example shows how to create a new Ethernet type port profile: 

    switch(config)# port-profile type ethernet UplinkPortChannel
switch(config-port-prof)# channel-group auto mode on
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# publish port-profile
switch(config)# copy running-config startup-config

    Configuring Access Ports Using Port Profiles

    An access port transmits packets on only one untagged VLAN. You can specify the VLAN, and it becomes the access VLAN. If you do not specify a VLAN for an access port, that interface carries traffic only on the default VLAN 1.

    Procedure
      Step 1   switch# configure terminal

      Enters global configuration mode.

      Step 2   switch(config)# [no] vlan vlan-id

      Creates or deletes, and saves in the running configuration, a VLAN or a range or VLANs.

      Step 3   switch(config)# port-profile type ethernet name

      Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics:

      • name—The port profile name can be up to 80 characters and must be unique for each port profile on the Cisco Nexus 1000V.

      • type—(Optional) The default port profile type is Ethernet.

      Step 4   switch(config-port-prof)# switchport mode access

      Sets port mode access.

      Step 5   switch(config-port-prof)# switchport access vlan [vlan-id-access]

      Assigns an access VLAN ID to this port profile.

      Note   

      An access port transmits packets on only one untagged VLAN. You can specify the VLAN, and it becomes the access VLAN. If you do not specify a VLAN for an access port, that interface carries traffic only on the default VLAN 1. If you do not specify a VLAN ID, then VLAN 1 is used automatically.

      Step 6   switch(config-port-prof)# no shutdown

      Administratively enables all ports in the profile.

      Step 7   switch(config-port-prof)# state enabled

      Enables the port profile and applies its configuration to the assigned ports.

      Step 8   switch(config-port-prof)# publish port-profile [name]

      Pushes the port profile to the VEMs.

      Step 9   (Optional)switch(config-port-prof)# copy running-config startup-config

      Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. 

      switch# configure terminal
switch(config)# port-profile mgmt-access
switch(config-port-prof)# switchport mode access
switch(config-port-prof)# switchport access vlan 72
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# publish port-profile
switch(config-port-prof)#

      Configuring Trunk Ports Using Port Profiles

      You can use this procedure to configure a Layer 2 port as a trunk port.

      Before You Begin

      • Before you configure a trunk port, ensure that you are configuring a Layer 2 interface.

      • A trunk port transmits untagged packets for one VLAN plus encapsulated, tagged, packets for multiple VLANs.

      • The device supports 802.1Q encapsulation only.

      • Be aware that the Cisco Nexus 1000V commands may differ from the Cisco IOS commands.

      Procedure
        Step 1   switch# configure terminal

        Enters global configuration mode.

        Step 2   switch(config)# vlan vlan-id

        Creates or deletes, and saves in the running configuration, a VLAN or a range or VLANs.

        Step 3   switch(config)# port-profile [type ethernet] name

        Enters port profile configuration mode for the named port profile. If the port profile does not already exist, it is created using the following characteristics:

        • name—The port profile name can be up to 80 characters and must be unique for each port profile on the Cisco Nexus 1000V.

        • type—(Optional) The default port profile type is vEthernet.

        Step 4   switch(config-port-prof)# switchport mode trunk

        Designates that the interfaces are to be used as a trunking ports.

        A trunk port transmits untagged packets for the native VLAN and transmits encapsulated, tagged packets for all other VLANs.

        Step 5   switch(config-port-prof)# switchport trunk allowed vlan {allowed-vlans | add add-vlans | except except-vlans | remove remove-vlans | all | none}

        Designates the port profile as trunking and defines VLAN access to it as follows:

        • allowed-vlans—Defines VLAN IDs that are allowed on the port.

        • add—Lists VLAN IDs to add to the list of those allowed on the port.

        • except—Lists VLAN IDs that are not allowed on the port.

        • remove—Lists VLAN IDs whose access is to be removed from the port.

        • all—Indicates that all VLAN IDs are allowed on the port, unless exceptions are also specified.

        • none—Indicates that no VLAN IDs are allowed on the port.

        Note   

        If you do not configure allowed VLANs, then the default VLAN 1 is used as the allowed VLAN.

        Step 6   switch(config-port-prof)# no shutdown

        Administratively enables all ports in the profile.

        Step 7   switch(config-port-prof)# state enabled

        Enables the port profile and applies its configuration to the assigned ports.

        Step 8   switch(config-port-prof)# publish port-profile [name]

        Pushes the port profile to the VEMs.

        Step 9   (Optional)switch(config-port-prof)# copy running-config startup-config

        Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

        This example shows how to configure a trunk port profile. 

        switch# configure terminal
switch(config)# port-profile Trunk_To_Cloud
switch(config-port-prof)# switchport mode trunk
switch(config-port-prof)# switchport trunk allowed vlan 72,2315-2350
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# publish port-profile
switch(config-port-prof)# copy running-config startup-config

        Creating a vEthernet Port Profile

        Before You Begin

        • You are logged in to the CLI in EXEC mode.

        • The template profiles should not have the switchport mode access vlan command configured. If the command is configured, the configuration is not applied.

        Procedure
           Command or ActionPurpose
          Step 1switch# configure terminal  

          Enters global configuration mode.

           
          Step 2switch(config)# port-profile type vethernet profile-name  

          Enters port profile configuration mode for the named vEthernet port profile. If the port profile does not already exist, it is created. Once configured, the type cannot be changed. Defining a vEthernet type port profile allows the port profile to be used for virtual (vEthernet) ports.

           
          Step 3switch(config-port-prof)# no shutdown  

          Administratively enables all ports in the profile.

           
          Step 4switch(config-port-prof)# state enabled  

          Enables the port profile and applies its configuration to the assigned ports.

           
          Step 5switch(config-port-prof)# publish port-profile [name]  

          Pushes the port profile to the VEMs as well as to the OpenStack controller.

           
          Step 6switch(config-port-prof)# copy running-config startup-config   (Optional)

          Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

           

          This example shows how to enable a port profile. 

          switch# configure terminal
switch(config)# port-profile type vethernet AccessProf
switch(config-port-prof)# state enabled 
switch(config-port-prof)# no shut
switch(config-port-prof)# publish port-profile 
switch(config-port-prof)# copy running-config startup-config

          Configuring a Trunk Policy Profile for a vEthernet Port

          You can use this procedure to configure a trunk policy profile for a vEthernet port.


          Note

          Native VLAN configuration in the trunk policy profile for vEthernet ports is not supported.

          Procedure
            Step 1   switch# configure terminal

            Enters global configuration mode.

            Step 2   switch(config)# port-profile [type vethernet] TrunkProfile
            Step 3   switch(config-port-prof)# switchport mode trunk

            Designates that the interfaces are to be used as a trunking ports.

            A trunk port transmits untagged packets for the native VLAN and transmits encapsulated, tagged packets for all other VLANs.

            Step 4   switch(config-port-prof)# no shutdown

            Enables all ports in the port profile.

            Step 5   switch(config-port-prof)# state enabled

            Enables the port profile and applies its configuration to the assigned ports.

            Step 6   switch(config-port-prof)# publish port-profile

            Pushes the port profile to the VEMs

            Step 7   (Optional)switch(config-port-prof)# copy running-config startup-config

            Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

            Verifying the Port Profile Configuration

            Use one of the following commands to verify the configuration:

            • show port-profile [brief | expand-interface | usage] [name profile-name]

            • show port-profile virtual usage [name profile-name]

            • show running-config port-profile [prof-name]

            • show interface virtual nsm

            For detailed information about the command output, see the Cisco Nexus 1000V Command Reference.

            show port profile

            switch# show port-profile

port-profile DEFAULT_DATA_VNIC1
 type: Vethernet
 description: 
 status: enabled
 max-ports: 32
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode access
  switchport access vlan 2170
  no shutdown
 evaluated config attributes:
  switchport mode access
  switchport access vlan 2170
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile DEFAULT_DATA_VNIC2
 type: Vethernet
 description: 
 status: enabled
 max-ports: 32
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode access
  switchport access vlan 2167
  no shutdown
 evaluated config attributes:
  switchport mode access
  switchport access vlan 2167
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile DEFAULT_DATA_VNIC3
 type: Vethernet
 description: 
 status: enabled
 max-ports: 32
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode access
  switchport access vlan 2169
  no shutdown
 evaluated config attributes:
  switchport mode access
  switchport access vlan 2169
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile hsrp-1
 type: Vethernet
 description: 
 status: enabled
 max-ports: 32
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode trunk
  disable-loop-detection hsrp
  no shutdown
 evaluated config attributes:
  switchport mode trunk
  disable-loop-detection hsrp
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile uplink_sys
 type: Ethernet
 description: 
 status: enabled
 max-ports: 512
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode trunk
  switchport trunk allowed vlan 2167-2170
  no shutdown
 evaluated config attributes:
  switchport mode trunk
  switchport trunk allowed vlan 2167-2170
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile uplink_sys_pc
 type: Ethernet
 description: 
 status: enabled
 max-ports: 512
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode trunk
  switchport trunk allowed vlan 2167
  channel-group auto mode active
  no shutdown
 evaluated config attributes:
  switchport mode trunk
  switchport trunk allowed vlan 2167
  channel-group auto mode active
  no shutdown
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

port-profile vm_access_sys
 type: Vethernet
 description: 
 status: disabled
 max-ports: 32
 min-ports: 1
 inherit: 
 config attributes:
  switchport mode access
 evaluated config attributes:
  switchport mode access
 assigned interfaces:
 port-group: 
 system vlans: none
 capability l3control: no
 capability iscsi-multipath: no
 capability vxlan: no
 capability l3-vservice: no
 port-profile role: none
 port-binding: static

switch#

            show port-profile name UpLinkProfile3

            switch# show port-profile name UpLinkProfile3
port-profile UpLinkProfile3
  description:
  type: vethernet
  status: disabled
  capability l3control: no
  pinning control-vlan: -
  pinning packet-vlan: -
  system vlans: none
  publish:
  max ports: 32
  inherit:
  config attributes:
    channel-group auto mode on sub-group manual
  evaluated config attributes:
    channel-group auto mode on sub-group manual
  assigned interfaces:
switch#

            show port-profile brief

            switch# show port-profile brief
-------------------------------------------------------------------------------
-
Port                          Profile    Profile  Conf   Eval   Assigned  Child
 
Profile                       Type       State    Items  Items  Intfs     Profs
 
-------------------------------------------------------------------------------
-
DEFAULT_DATA_VNIC1            Vethernet  1        3      3      0         0    
 
DEFAULT_DATA_VNIC2            Vethernet  1        3      3      0         0    
 
DEFAULT_DATA_VNIC3            Vethernet  1        3      3      0         0    
 
hsrp-1                        Vethernet  1        3      3      0         0    
 
mx-nlb                        Vethernet  0        0      0      0         0    
 
N1K_Cloud_Default_Trunk       Vethernet  1        2      2      0         0    
 
uplink_sys                    Ethernet   1        3      3      0         0    
 
uplink_sys_pc                 Ethernet   1        4      4      0         0    
 
vm_access_sys                 Vethernet  0        1      1      0         0    
 
vrrp-1                        Vethernet  1        3      3      0         0    
 
-------------------------------------------------------------------------------
-
Profile    Assigned  Total  Sys    Parent Child  UsedBy
Type       Intfs     Prfls  Prfls  Prfls  Prfls  Prfls 
-------------------------------------------------------------------------------
-
Vethernet  0         10     0      12     0      0     
Ethernet   0         2      0      3      0      0     
switch#

            show port-profile virtual usage

            switch# show port-profile virtual usage
-------------------------------------------------------------------------------
Port Profile               Port        Adapter        Owner
-------------------------------------------------------------------------------
PVLAN_Macpin               Po2
                           Po4
                           Po6
                           Po8
                           Po9
                           Eth3/1      vmnic0         NODE-135
                           Eth3/2      vmnic1         NODE-135
                           Eth4/1      vmnic0         NODE-137
                           Eth4/2      vmnic1         NODE-137
                           Eth5/2      vmnic1         NODE-139
                           Eth5/3      vmnic2         NODE-139
                           Eth6/1      vmnic0         NODE-141
                           Eth6/2      vmnic1         NODE-141
                           Eth7/1      vmnic0         NODE-UCS-158
                           Eth7/2      vmnic1         NODE-UCS-158
dynpp_03ac7d00-933d-4fc6-8 Veth1                      LINUX-RHEL-01
                           Veth2                      LINUX-RHEL-02
                           Veth3                      LINUX-RHEL-03
                           Veth4                      LINUX-RHEL-04
                           Veth5                      LINUX-RHEL-05
                           Veth6                      LINUX-RHEL-06
                           Veth7                      LINUX-RHEL-07
switch#

            show port-profile expand-interface name PVLAN_Macpin

            switch# show port-profile expand-interface name  PVLAN_Macpin

port-profile lacp-uplink
port-channel2
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown
port-channel4
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown
Ethernet3/1
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown
Ethernet3/3
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown
Ethernet4/2
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown
Ethernet4/5
  switchport mode trunk
  switchport trunk allowed vlan 2000-2200
  channel-group auto mode active
  no shutdown

switch#

            show port-profile expand-interface

            switch# show port-profile expand-interface
port-profile DATA-Lacp
 port-channel3
  switchport mode trunk
  switchport trunk allowed vlan 150,205,207,209,211,213,215,217,219,221
  switchport trunk allowed vlan add 223,225,227,229,231,233,235,237,239
  switchport trunk allowed vlan add 241,243,245,247,249,251,253,255,257
  switchport trunk allowed vlan add 261-263,265,267,269,271,273,275,277
  switchport trunk allowed vlan add 281,283,285,287,289,291,293,295,297
  switchport trunk allowed vlan add 299
  channel-group auto mode active
  no shutdown
 port-channel5
  switchport mode trunk
  switchport trunk allowed vlan 150,205,207,209,211,213,215,217,219,221
  switchport trunk allowed vlan add 223,225,227,229,231,233,235,237,239
  switchport trunk allowed vlan add 241,243,245,247,249,251,253,255,257
  switchport trunk allowed vlan add 261-263,265,267,269,271,273,275,277
  switchport trunk allowed vlan add 281,283,285,287,289,291,293,295,297
  switchport trunk allowed vlan add 299
  channel-group auto mode active
  no shutdown
Ethernet4/3
  switchport mode trunk
  switchport trunk allowed vlan 150,205,207,209,211,213,215,217,219,221
  switchport trunk allowed vlan add 223,225,227,229,231,233,235,237,239
switch#

            show port-profile expand-interface name

            switch# show port-profile expand-interface name vmn_f58d3545-a0a1-4441-8b7e-1a7c8339524b_0200362d-0d69-44bc-8f2d-40685f474ddf
port-profile vmn_f58d3545-a0a1-4441-8b7e-1a7c8339524b_0200362d-0d69-44bc-8f2d-40685f474ddf
Vethernet33
  switchport mode access
  switchport access vlan 63
  no shutdown
Vethernet157
  switchport mode access
  switchport access vlan 63
  no shutdown

            show running-config port-profile

            switch# show running-config port-profile

!Command: show running-config port-profile
!Time: Mon Aug 26 09:04:05 2013

version 5.2(1)SK1(1.1)
port-profile default max-ports 32
port-profile default port-binding static
port-profile type vethernet N1K_Cloud_Default_Trunk
  switchport mode trunk
  no shutdown
  guid 51e1095a-61ea-50b5-9f3c-19842dcff6e7
  max-ports 64
  description Port Profile created for Nexus 1000V internal usage. Do not use.
  state enabled
port-profile type ethernet uplink_sys
  switchport mode trunk
  switchport trunk allowed vlan 2167-2170
  no shutdown
  guid 53502d18-9ffb-411a-b665-d830081136e5
  max-ports 512
  state enabled
port-profile type ethernet uplink_sys_pc
  switchport mode trunk
  switchport trunk allowed vlan 2167
  channel-group auto mode active
  no shutdown
  guid 7aa26801-1e00-2684-97ec-a7cc1a4615af
  max-ports 512
  state enabled
port-profile type vethernet vm_access_sys
  switchport mode access
  guid 78dc356e-1fe5-7c72-8c2c-6286065720a8
port-profile type vethernet DEFAULT_DATA_VNIC1
  switchport mode access
  switchport access vlan 2170
  no shutdown
  guid 5cb014fe-3d4f-014a-b673-869700f70425
  state enabled
port-profile type vethernet DEFAULT_DATA_VNIC2
  switchport mode access
  switchport access vlan 2167
  no shutdown
  guid 42dbc174-30ec-2ab7-8796-c92e15ea4167
  state enabled
port-profile type vethernet DEFAULT_DATA_VNIC3
  switchport mode access
  switchport access vlan 2169
  no shutdown
  guid 090dc703-caca-102c-869a-86e433531d77
  state enabled
port-profile type vethernet mx-nlb
  guid 2505614c-2107-5f97-9f21-45d70b57aa3e
port-profile type vethernet hsrp-1
  switchport mode trunk
  disable-loop-detection hsrp
  no shutdown
  guid 6d2b8903-94c5-2e9a-923d-182408301feb
  state enabled
port-profile type vethernet vrrp-1
  disable-loop-detection vrrp
  switchport mode trunk
  no shutdown
  guid 3262b6ec-1333-2665-bc78-37a31ea6a71e
  state enabled

switch#

            Enabling a Port Profile

            You enable a port profile to apply its configuration to the assigned port.

            Before You Begin

            • You are logged in to the CLI in EXEC mode.

            • You have already created the port profile.

            Procedure
               Command or ActionPurpose
              Step 1switch# configure terminal  

              Enters global configuration mode.

               
              Step 2switch(config)# port-profile [type {vethernet}] profile-name  

              Enters port profile configuration mode for the named vEthernet port profile.

               
              Step 3switch(config-port-prof)# state enabled  

              Enables the port profile and applies its configuration to the assigned ports.

               
              Step 4switch(config-port-prof)# show port-profile [brief | expand-interface | usage] [name profile-name]  

              Displays the configuration for verification.

               
              Step 5switch(config-port-prof)# copy running-config startup-config   (Optional)

              Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

               

              This example shows how to enable a port profile. 

              switch# configure terminal
switch(config)# port-profile AccessProf
switch(config-port-prof)# state enabled
switch(config-port-prof)# show port-profile name AccessProf
port-profile AccessProf
  description: allaccess4
  status: enabled
capability l3control: no
  pinning control-vlan: -
  pinning packet-vlan: -
  system vlans: none
  port-group:
  max ports: 32
  inherit:
  config attributes:
    channel-group auto mode on
  evaluated config attributes:
    channel-group auto mode on
  assigned interfaces:
switch(config-port-prof)#

              Publishing a Port Profile

              You publish an Ethernet port profile to push its configuration to the VEMs. You publish a vEthernet port profile to publish its configuration to the OpenStack controllerwhere it can be created and implemented in a virtual network.

              Before You Begin

              • You are logged in to the CLI in EXEC mode.

              • You have already created and enabled the port profile.

              Procedure
                 Command or ActionPurpose
                Step 1switch# configure terminal  

                Enters global configuration mode.

                 
                Step 2switch(config)# port-profile [type {vethernet}] profile-name  

                Enters port profile configuration mode for the named port profile.

                 
                Step 3switch(config-port-prof)# publish port-profile [name]   If you are publishing an Ethernet port profile, the port profile configuration is pushed to the VEMs. If you are publishing a vEthernet port profile, the port profile configuration is published to the OpenStack controller.  
                Step 4
                                  		 
                Step 5switch(config-port-prof)# show port-profile [brief | expand-interface | usage] [name profile-name]  

                Displays the configuration for verification.

                 
                Step 6switch(config-port-prof)# copy running-config startup-config   (Optional)

                Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

                 

                This example shows how to publish a port profile. 

                switch# configure terminal
switch(config)# port-profile AccessProf
switch(config-port-prof)# publish port-profile
switch(config-port-prof)#

                Removing a Port Profile

                Before You Begin

                • You are logged in to the CLI in EXEC mode.

                • You must remove all associations to the vEthernet port profile in the OpenStack controller before removing the port profile from the VSM.

                Procedure
                   Command or ActionPurpose
                  Step 1switch(config)# show interface virtual nsm   (Optional)

                  Shows policy port profile usage for all interfaces.

                  Note   

                  You cannot remove a port profile if there are active interfaces associated with it.

                   
                  Step 2switch# configure terminal  

                  Enters global configuration mode.

                   
                  Step 3switch(config)# no port-profile profile_name  

                  Removes the port profile configuration and operational settings. When a port profile is removed from the VSM, you have to refresh the extension manager from the OpenStack controller to remove the port profile from the OpenStack controller. If the extension manager from the OpenStack controller is not refreshed, the profile is displayed as Marked for Deletion in the OpenStack controller.

                   
                  Step 4switch(config)# copy running-config startup-config   (Optional)

                  Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

                   

                  This example shows how to remove a port profile: 

                  switch# show port-profile virtual usage
-------------------------------------------------------------------------------
Port Profile               Port        Adapter        Owner
-------------------------------------------------------------------------------
trunk-uplink               Po1                                                 
                           Po3                                                 
                           Po5                                                 
                           Eth3/6      eth3           site1-uvem               
                           Eth4/6      eth3           site2-uvem               
                           Eth5/1      eth3           site3-uvem               
                           Eth5/4      eth2           site3-uvem               
                           Eth5/6      eth4           site3-uvem               
vm-access-vlan-1601        Veth14      vnet6          85badf15-244d-4719-a2da-8
                           Veth73      vnet2          85badf15-244d-4719-a2da-8
                           Veth99      vnet4          85badf15-244d-4719-a2da-8
vm-access-vlan-1701        Veth3       vnet1          85badf15-244d-4719-a2da-8
                           Veth8       vnet6          85badf15-244d-4719-a2da-8
                           Veth11      vnet8          85badf15-244d-4719-a2da-8
                           Veth15      vnet1          85badf15-244d-4719-a2da-8
                           Veth125     vnet1          85badf15-244d-4719-a2da-8
                           Veth171     vnet104        85badf15-244d-4719-a2da-8
vm-access-vlan-1801        Veth9       vnet7          85badf15-244d-4719-a2da-8
                           Veth20      vnet9          85badf15-244d-4719-a2da-8
1G-uplink                  Eth3/4      eth5           site1-uvem               
                           Eth4/4      eth5           site2-uvem               
                           Eth5/5      eth5           site3-uvem               
                           Eth6/1      eth1           test-vem1                
                           Eth7/1      eth1           test-vem2                
                           Eth8/1      eth1           test-vem3                
                           Eth9/1      eth1           test-vem4                
                           Eth10/1     eth1           test-vem5                
                           Eth11/1     eth1           test-vem6                
                           Eth12/1     eth1           test-vem7                
                           Eth13/1     eth1           test-vem8                
                           Eth14/1     eth1           test-vem101              
                           Eth15/1     eth1           test-vem102              
                           Eth16/1     eth1           test-vem103              
                           Eth17/1     eth1           test-vem104              
                           Eth18/1     eth1           test-vem105              
vm-access-vlan-2000        Veth4       vnet2          85badf15-244d-4719-a2da-8
                           Veth18      vnet2          85badf15-244d-4719-a2da-8
vm-access-vlan-2001        Veth5       vnet3          85badf15-244d-4719-a2da-8
                           Veth19      vnet3          85badf15-244d-4719-a2da-8
vm-access-vlan-1611        Veth17      vnet7          85badf15-244d-4719-a2da-8
                           Veth22      vnet14         85badf15-244d-4719-a2da-8
                           Veth173     vnet3          85badf15-244d-4719-a2da-8
lacp-uplink                Po2                                                 
                           Po4                                                 
                           Eth3/1      eth4           site1-uvem               
                           Eth3/3      eth2           site1-uvem               
                           Eth4/2      eth4           site2-uvem               
                           Eth4/5      eth2           site2-uvem               
vm-access-vlan-2100        Veth6       vnet4          85badf15-244d-4719-a2da-8
                           Veth13      vnet4          85badf15-244d-4719-a2da-8
10G-uplink                 Eth3/5      eth0           site1-uvem               
                           Eth4/3      eth0           site2-uvem               
                           Eth5/3      eth0           site3-uvem               
vm-access-vlan-2           Veth1       vnet0          85badf15-244d-4719-a2da-8
                           Veth12      vnet0          85badf15-244d-4719-a2da-8
                           Veth31      vnet0          85badf15-244d-4719-a2da-8
vm-access-vlan-1602        Veth126     vnet5          85badf15-244d-4719-a2da-8
vm-access-vlan-1603        Veth127     vnet6          85badf15-244d-4719-a2da-8
vm-access-vlan-1604        Veth169     vnet7          85badf15-244d-4719-a2da-8
.
.
.
vm-access-vlan-1747        Veth151     vnet150        85badf15-244d-4719-a2da-8
vm-access-vlan-1748        Veth134     vnet151        85badf15-244d-4719-a2da-8
vm-access-vlan-1749        Veth107     vnet152        85badf15-244d-4719-a2da-8
1G-VXLAN-uplink            Eth3/2      eth6           site1-uvem               
                           Eth4/1      eth6           site2-uvem               
                           Eth5/2      eth6           site3-uvem               
vm-access-vlan-1799        Veth2       vxlan-nic0                              
                           Veth10      vxlan-nic0                              
bd1                        Veth7       vnet5          85badf15-244d-4719-a2da-8
                           Veth16      vnet5          85badf15-244d-4719-a2da-8
mcast-access-port          Veth177     vnet8          85badf15-244d-4719-a2da-8
                           Veth178     vnet10         85badf15-244d-4719-a2da-8
                           Veth179     vnet156        85badf15-244d-4719-a2da-8
                           Veth180     vnet9          020b89af-9fba-0118-0013-0
switch# configure terminal
switch(config)# no port-profile trunk-uplink
switch(config)# copy running-config startup-config
switch(config)#

                  Feature History for Port Profiles

                  Feature Name

                  Releases

                  Feature Information

                  Port profiles

                  Release 5.2(1)SK1(2.1)

                  This feature was introduced.

                  Was this Document Helpful?

                  FeedbackFeedback

                  Contact Cisco

                  Related Cisco Community Discussions

                  About Us
                  Contact Us
                  Work with Us