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
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) |
|
Port binding |
You can configure a port binding with the dynamic [auto ] option . |
4.2(1)SV1(4a) |
|
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) |
|
Port binding |
You can configure port binding for vEthernet port profiles that affects how VMware port IDs are assigned. |
4.2(1)SV1(4) |
|
Restrict the visibility of Port Profiles |
Restricts port profile visibility by user or user group. |
4.2(1)SV1(4) |
|
mtu command added |
The mtu command replaces the system mtu command for uplink, Ethernet type port profiles. |
4.2(1)SV1(4) |
|
system mtu command removed |
The system mtu command is removed and replaced by the mtu command for port profiles. |
4.2(1)SV1(4) |
|
show port-profile sync-status command added |
Displays interfaces that are out of sync with the port profile. |
4.2(1)SV1(4) |
|
show port-profile virtual usage command added |
Displays the port profile usage by interface. |
4.2(1)SV1(4) |
|
Atomic Inheritance |
Port profile configuration applied to member interfaces. |
4.2(1)SV1(4) |
|
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) |
|
Interface Quarantine |
After a configuration failure, interfaces are shut down to maintain accurate configuration. |
4.2(1)SV1(4) |
|
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) |
|
show running-config port-profile |
New command for displaying the port profile configuration. |
4.0(4)SV1(2) |
|
Uplink port profile |
Port profiles are not classified as uplinks, but are configured as Ethernet or vEthernet links. |
4.0(4)SV1(2) |
|
Configuration limits |
Added configuration limits for vEthernet interfaces, vEthernet trunks, port profiles, system profiles, and PVLANs. |
4.0(4)SV1(2) |
|
vPC-Host Mode |
Support for the following:
|
4.0(4)SV1(2) |
|
MAC Pinning |
Connecting to upstream switches that do not support port channels using the MAC-pinning command. |
4.0(4)SV1(2) |
|
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) |
|
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 profile is created as a vEthernet type. |
4.0(4)SV1(2) |
|
[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 an uplink capability, configure the port profile as an Ethernet type. |
4.0(4)SV1(2) |
|
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) |
|
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) |