Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide, Release 5.x

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 Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide, Release 5.x

Chapter Title

Creating Port Profiles

Results

Updated:
December 18, 2014

Chapter: Creating Port Profiles

Creating Port Profiles

This chapter contains the following sections:

Information About Port Profiles

Information About Port Profile States

The following table describes port profile behavior.

State

Behavior

Disabled (the default)

When disabled, a port profile behaves as follows:

  • Its configuration cannot be applied to assigned ports.

  • The port profile is not published to the Microsoft SCVMM server.

Enabled

When enabled, a port profile behaves as follows:

  • Its configuration is applied to assigned ports.

  • The port profile is published to the Microsoft SCVMM server.

Guidelines and Limitations for Creating Port Profiles


Note

When you define a port profile, do not configure the port mode, VLAN, or PVLAN configurations. The publish command is used to publish the user-created profiles to the Microsoft SCVMM Server. For auto-generated port profiles, see the Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide.

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

  • In an installation where multiple Ethernet port profiles are active on the same VEM, it is recommended that they do not carry the same VLAN(s). The allowed VLAN list should be mutually exclusive. Overlapping VLANs can be configured but may 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.

  • MTU can only be configured for uplink Ethernet type port profiles.

  • A default vEthernet port profile can also be created for Nexus 1000V deployment on the Microsoft SCVMM. This can be achieved by marking a port classification on the Logical Switch (on SCVMM) as “default”.

Default Settings

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

Parameter

Default

description

-

administrative state

all ports disabled

type

vethernet

publish port-profile name

Port profile name

Configuring Port Profiles

Creating and Enabling an Ethernet Type 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 | vethernet}] 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.

    • type—(Optional) The port profile type can be Ethernet or vEthernet. Once configured, the type cannot be changed. The default is the vEthernet type.

      Defining a port profile type as Ethernet allows the port profile to be used for physical (Ethernet) ports.

      Note   

      If a port profile is configured as an Ethernet type, then it cannot be used to configure the virtual ports.

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

    Configure the ports and channels in the port profile.

    Note   

    The channel-group command is not supported for vEth port profiles.

     
    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 

    Publishes the port profile.

    Note   

    The publish port-profile command is not required for the Ethernet port profiles.

     

    This example shows how to create a new port profile:

    switch(config)# port-profile type ethernet UplinkNoPortChannel
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# show port-profile name UplinkNoPortChannel 
port-profile UplinkNoPortChannel
type: Ethernet
description: 
status: enabled
max-ports: 512
min-ports: 1
inherit: 
config attributes:
no shutdown
evaluated config attributes:
no shutdown
assigned interfaces:
port-group: 
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none
port-binding: static 
switch(config-port-prof)#

    Creating and Enabling a vEthernet Type Port Profile

    Before You Begin

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

    • You have already created the port profile using Creating a Port Profile.


      Note

      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.

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

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

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

      Publishes the port profile. This command is not required for the Ethernet port profiles.

       
      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 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)# end
switch# show port-profile name Accessprof

port-profile AccessProf
type: Vethernet
description: 
status: enabled
max-ports: 32
min-ports: 1
inherit: 
config attributes:
no shutdown
evaluated config attributes:
no shutdown
assigned interfaces:
port-group: AccessProf
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none
port-binding: static

switch(config-port-prof)#

      Removing a Port Profile

      Before You Begin

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

      • If the port profile is inherited by another port profile, you need to remove the inheritance from the other port profile before removing this port profile. If you do not remove the inheritance first, the procedure fails. See Removing Inherited Policies from a Port Profile.

      Procedure
         Command or ActionPurpose
        Step 1switch(config)# show port-profile virtual usage  (Optional)

        Verifies if active interfaces use this port profile.

        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 Microsoft SCVMM to remove the port profile from Microsoft SCVMM. If the extension manager from Microsoft SCVMM is not refreshed, the profile is displayed as Marked for Deletion on Microsoft SCVMM.

         
        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
-------------------------------------------------------------------------------
MAC_PIN		                  Po2
                           Po3
																											Po5
                           Eth3/1      vmnic0         WIN-37
LACP_PIN		                 Po1
                           Po4
																											Po5
                           Eth4/1      vmnic0         WIN-37
switch(config)# no port-profile AccessProf
switch(config)#end
switch(config)#

        Standards for Creating Port Profiles

        No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

        Feature History for Port Profiles

        Feature Name

        Releases

        Feature Information

        Creating port profiles

        5.2(1)SM1(5.1)

        This feature was introduced.

        Was this Document Helpful?

        FeedbackFeedback

        Contact Cisco