Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1) SV1(4a)

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

Results

Updated:: January 31, 2011

Chapter: New and Changed Information

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:

•Release Notes.

•Command Reference.


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 vEthernet Port Profiles"
Port binding	You can configure a port binding with the dynamic [auto] option.	4.2(1)SV1(4a)	"Configuring Port Binding for vEthernet Port Profiles"
Port channel	The Creating a Port Profile for a Port Channel chapter was moved into the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4a).	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 vEthernet Port Profiles"
Restrict the visibility of Port Profiles	Restricts port profile visibility by user or user group.	4.2(1)SV1(4)	"Restricting Port Profile Visibility"
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)	"Overview"
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)	"Overview"
Interface Quarantine	After a configuration failure, interfaces are shut down to maintain accurate configuration.	4.2(1)SV1(4)	"Overview"
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, Release 4.2(1)SV1(4a)
Configuration limits	Added configuration limits for vEthernet interfaces, vEthernet trunks, port profiles, system profiles, and PVLANs.	4.0(4)SV1(2)

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)