Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV2(1.1)
New and Changed Information
Downloads: This chapterpdf (PDF - 383.0KB) The complete bookPDF (PDF - 1.65MB) | The complete bookePub (ePub - 492.0KB) | Feedback

New and Changed Information

New and Changed Information

This chapter contains the following sections:

New and Changed Information

This section lists new and changed content in this document by software release.

To find additional information about new features or command changes, see the following:

  • Cisco Nexus 1000V Release Notes
  • Cisco Nexus 1000V Command Reference
Table 1 New and Changed Information

Feature

Description

Changed in release

Where Documented

Port binding

You can configure a static port binding with the auto option.

4.2(1)SV1(4a)

Configuring Port Binding for a vEthernet Port Profile

Port binding

You can configure a port binding with the dynamic [auto] option.

4.2(1)SV1(4a)

Configuring Port Binding for a vEthernet Port Profile

Port channel

The "Creating a Port Profile for a Port Channel" chapter was moved into the Cisco Nexus 1000V Interface Configuration Guide.

4.2(1)SV1(4)

Configuring Port Channels

Port binding

You can configure port binding for vEthernet port profiles that affects how VMware port IDs are assigned.

4.2(1)SV1(4)

Configuring Port Binding for a vEthernet Port Profile

Restrict the visibility of Port Profiles

Restricts port profile visibility by user or user group.

4.2(1)SV1(4)

Restricting Port Profile Visibility on the VSM

mtu command added

The mtu command replaces the system mtu command for uplink, Ethernet type port profiles.

4.2(1)SV1(4)

Creating a System Port Profile

system mtu command removed

The system mtu command is removed and replaced by the mtu command for port profiles.

4.2(1)SV1(4)

Creating a System Port Profile

show port-profile sync-status command added

Displays interfaces that are out of sync with the port profile.

4.2(1)SV1(4)

Verifying the Port Profile Configuration

show port-profile virtual usage command added

Displays the port profile usage by interface.

4.2(1)SV1(4)

Verifying the Port Profile Configuration

Atomic Inheritance

Port profile configuration applied to member interfaces.

4.2(1)SV1(4)

Information About Atomic Inheritance

Port Profile Rollback

After configuration failure, a port profile and its member interfaces are rolled back to the last good configuration.

4.2(1)SV1(4)

Information About Rollback to a Consistent Configuration

Interface Quarantine

After a configuration failure, interfaces are shut down to maintain accurate configuration.

4.2(1)SV1(4)

Information About Interface Quarantine

system mtu command

This command allows you to preserve a non-default MTU setting on the PNIC attached to the Cisco Nexus 1000V across reboots of the ESX server.

4.0(4)SV1(3)

Creating a System Port Profile

show running-config port-profile

New command for displaying the port profile configuration.

4.0(4)SV1(2)

Verifying the Port Profile Configuration

Uplink port profile

Port profiles are not classified as uplink, but are, instead, configured as Ethernet or vEthernet.

4.0(4)SV1(2)

Cisco Nexus 1000V Interface Configuration Guide

Configuration limits

Added configuration limits for vEthernet interfaces, vEthernet trunks, port profiles, system profiles, and PVLANs.

4.0(4)SV1(2)

Port Profile Configuration Limits

vPC-Host Mode

Support for the following:

  • Manual creation of subgroups.
  • Connecting to upstream switches that do not support port channels using MAC Pinning.

4.0(4)SV1(2)

Cisco Nexus 1000V Interface Configuration Guide

MAC Pinning

Connecting to upstream switches that do not support port channels using the MAC-pinning command.

4.0(4)SV1(2)

Cisco Nexus 1000V Interface Configuration Guide

Static Pinning

Support for pinning or directing traffic for a vEthernet interface, control VLAN, or packet VLAN to a specific port channel subgroup.

4.0(4)SV1(2)

Cisco Nexus 1000V Interface Configuration Guide

Port Profile Type

Creation of port-profiles includes the optional type field, which specifies the port profile as either Ethernet or vEthernet. By default, a port profiles is created as a vEthernet type.

4.0(4)SV1(2)

Creating a Port Profile

[no] capability uplink command

The capability uplink command has been superseded by the port-profile [type {ethernet | vethernet}] name command. To configure a port profile with uplink capability, configure the port profile as an Ethernet type.

4.0(4)SV1(2)

Creating a Port Profile

show running-config command

This command now shows the port profile type (Ethernet or vEthernet). Also, you can optionally specify to show only the port profile configurations.

4.0(4)SV1(2)

Verifying the Port Profile Configuration

show port-profile name command

This command shows the port profile type and does not show the capability uplink. This command also shows the pinning and channel-group configuration.

4.0(4)SV1(2)

Verifying the Port Profile Configuration