Guest

Cisco Nexus 1000V Switch for VMware vSphere

Cisco Nexus1000V Release Notes, Release 4.2(1) SV1(4a)

  • Viewing Options

  • PDF (526.2 KB)
  • Feedback

Table of Contents

Cisco Nexus 1000V Release Notes, Release 4.2(1) SV1(4a)

Contents

Introduction

Software Compatibility

Software Compatibility with VMware

Software Compatibility with Cisco Nexus 1000V

New and Changed Information

Changed Software Features

Scalability Limits

New Software Features

Support for vSphere 5.0.0

In Service Software Upgrade

Distributed Virtual Switch Deletion

VSM Backup and Recovery

Dynamic Port Management

Unknown Unicast Flood Blocking

SMNP ACL

Virtual Port Channel - Host Mode Enhancements

Backup Subgroups

High Availability Enhancements

Virtualized Workload Mobility (DC to DC vMotion)

Limitations and Restrictions

Configuration Limits

Single VMware Data Center Support

vMotion of VSM

VMware Lab Manager

Upgrades

Access Lists

NetFlow

Port Security

Port Profiles

Telnet Enabled by Default

SSH Support

Cisco NX-OS Commands Might Differ from Cisco IOS

Layer 2 Switching

No Spanning Tree Protocol

Cisco Discovery Protocol

DHCP Not Supported for the Management IP

LACP

Upstream Switch Ports

DNS Resolution

Interfaces

Caveats

Open Caveats

Platform, Infrastructure, Ports, Port Channel, and Port Profiles

Quality of Service

Features

VMware

Resolved Caveats

MIB Support

Available Documents

Cisco Nexus 1000V Release Notes, Release 4.2(1) SV1(4a)

Updated: March 21, 2014

OL-22822-A1-J0

This document describes the features, limitations, and caveats for the Cisco Nexus 1000V Release 4.2(1)SV1(4a) software. Use this document in combination with documents listed in the “Available Documents” section. The following is the change history for this document.

 

Part Number
Revision
Date
Description

OL-22822-A1

J0

08/02/13

Updated the “LACP” section and added the “Upstream Switch Ports” section.

OL-22822-A1

I0

4/12/12

Added CSCtr55673 to the Resolved Caveats.

OL-22822-A1

H0

4/02/12

Added CSCto00715 to the Resolved Caveats.

OL-22822-A1

G0

12/21/11

Added CSCtn37614 and CSCto15203 to the Closed Caveats.

OL-22822-A1

F0

10/18/11

Added CSCts80394 to the Open VMware Caveats table.

OL-22822-A1

E0

10/14/11

Added DHCP Snoop Binding Entries to the Configuration Limits.
Revised wording of Single VMware Data Center Support.

OL-22822-A1

D0

10/3/11

Updated Resolved Caveats list.

OL-22822-A1

C0

9/15/11

Updated for CSCts05309

OL-22822-A1

B0

8/25/11

Added VMware ESXi 5.0.0

OL-22822-A1

A0

7/29/11

Created release notes for Release 4.2(1)SV1(4a).

Introduction

The Cisco Nexus 1000V provides a distributed, Layer 2 virtual switch that extends across many virtualized hosts. The Cisco Nexus 1000V manages a data center defined by the vCenter Server. Each server in the data center is represented as a line card in Cisco Nexus 1000V and can be managed as if it were a line card in a physical Cisco switch.

Cisco Nexus 1000V consists of the following two components:

  • Virtual Supervisor Module (VSM), which contains the Cisco CLI, configuration, and high-level features.
  • Virtual Ethernet Module (VEM), which acts as a line card and runs in each virtualized server to handle packet forwarding and other localized functions.

Software Compatibility

This section includes the following topics:

Software Compatibility with VMware

The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This release of Cisco Nexus 1000V supports vSphere 4.0.0, 4.1.0 and 5.0.0 release trains. For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4a) .


Note All virtual machine network adapter types that VMware vSphere supports are supported with Cisco Nexus 1000V. Refer to the VMware documentation when choosing a network adapter. For more information, see the VMware Knowledge Base article #1001805.


Software Compatibility with Cisco Nexus 1000V

This release supports hitless upgrades from Release 4.0(4)SV1(3a) and later releases. Upgrades are supported from 4.0(4)SV1(3) and earlier releases. For additional information, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a) .

New and Changed Information

This section provides the following information about this release:

Changed Software Features

The following software features were changed in this release:

Scalability Limits

Scalability limits for multiple features have been increased in this release; refer to the “Configuration Limits” section for updated limits.

Support for vSphere 5.0.0

This release is compatible with all features of vSphere 5.0.0 including Stateless ESXi. Download the compatible VEM from the location specified in the Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.2(1)SV1(4a) .

In Service Software Upgrade

VSM upgrades from Release 4.2(1)SV1(4) to Release 4.2(1)SV1(4a) and later use the In Service Software Upgrade (ISSU) install feature that was introduced in Release 4.2(1)SV1(4). You can now use this functionality in Release 4.2(1)SV1(4a). The ISSU install feature upgrades the VSM images while preserving the configuration and state of the VSM. It does not interrupt operations. For more information, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a) .

Distributed Virtual Switch Deletion

The Cisco Nexus 1000V provides the capablity for the privileged users to remove a stale distributed virtual switch (DVS) on the host. For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4a) .

VSM Backup and Recovery

Support for backing up the VSM VM and its configuration so that it can be restored at a later time in case of accidental VSM deletions or disk corruptions has been implemented. The VSM backup and recovery operation requires coordination between the network and server administrators. For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4a) .

Dynamic Port Management

Cisco Nexus 1000VV has the capability to dynamicaly adjust the number of ports consumed at the vCenter vDS. For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4a) .

Unknown Unicast Flood Blocking

Unknown Unicast Flood Blocking (UUFB) allows you to configure the system to drop the unknown Unicast packets coming from the uplink ports. For more information, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4a) .

SMNP ACL

Standard Simple Network Management Protocol (SNMP) supports source-based filtering from the SNMP-COMMUNITY-MIB. This requires the configuration of the SNMP community table. By integrating with the existing access control list (ACL) feature in NX-OS, you can easily apply source-based filtering. You can configure ACL to be associated with all the incoming requests for a particular community. SNMP matches the community and ACL, and processes the request accordingly. If the ACL denies access to SNMP, then SNMP prints a syslog at error level. If ACL permits processing of the message, SNMP processes the packet as usual. This ACL is applied both for IPv4 and IPv6 over both User Datagram Protocol (UDP) and Transmission Control Protocol (TCP).

Virtual Port Channel - Host Mode Enhancements

Virtual Port Channel - Host Mode (vPC-HM) enhancements supports the logical numbering of subgroups in the port channel mac-pinning mode. For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4a) .

Backup Subgroups

This feature allows for the assignment of up to seven backup subgroups. For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4a) .

High Availability Enhancements

The behavior of some error handling functionality in High Availability (HA) has been modified from earlier releases. When communication over the control interface is interrupted, the standby VSM is reset once and only after the active and standby VSMs have lost syncronization. If communication over the control interface is not available, the standby VSM will wait for communication to be restored before initiating the synchronization with the active VSM.

Virtualized Workload Mobility (DC to DC vMotion)

This feature allows for a single Cisco Nexus 1000V instance spanning across two data centers. The maximum support latency is 5ms. See Table 1 for the supported limits across two data centers. For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4a) .

Limitations and Restrictions

The Cisco Nexus 1000V has the following limitations and restrictions:

Configuration Limits

Table 1 shows the Cisco Nexus 1000V configuration limits:

 

Table 1 Configuration Limits for Cisco Nexus 1000V

Component
Supported Limits for Cisco Nexus 1000V in the Same Datacenter
Supported Limits for Cisco Nexus 1000V Across Two Datacenters

Maximum Modules

66

34

Virtual Ethernet Module(VEM)

64

32

Virtual Supervisor Module (VSM)

2 in an HA Pair (active-standby hosted in the same datacenter)

2 in an HA Pair (active-standby hosted in the same datacenter)

vCenter Server Datacenters per VSM

1

1

Hosts

64

32

Active VLANs across all VEMs

2048

1024

MACs per VEM

32000

32000

MACs per VLAN per VEM

4000

4000

vEthernet interfaces per port profile

1024

1024

PVLAN

512

128

Distributed Virtual Switches (DVSes) per vCenter

12

12

vCenter Server connections

1 per VSM HA Pair1

1 per VSM HA Pair 1

Maximum latency between VSMs and VEMs

5 ms

Per DVS
Per Host
Per DVS
Per Host

Virtual Service Domains (VSDs)

64

6

32

3

VSD interfaces

2048

216

1024

108

vEthernet interfaces

2048

216

1024

108

Port profiles

2048

1024

System port profiles

32

32

16

16

Port channels

256

8

128

4

Physical trunks

512

256

Physical NICs

32

16

vEthernet trunks

256

8

128

4

ACLs

128

162

64

8 2

ACEs per ACL

128

128 2

64

64 2

ACL interfaces

2048

256

1024

128

NetFlow policies

32

8

16

4

NetFlow interfaces

256

32

128

16

SPAN/ERSPAN sessions

64

64

32

32

QoS policy maps

128

128

64

64

QoS class maps

1024

1024

512

512

QoS interfaces

2048

256

1024

128

Port security

2048

216

1024

108

Multicast groups

512

512

256

256

DHCP snoop binding entries (static + dynamic)

2048

2048

1024

1024

1.Only one connection to vCenter server is permitted at a time.

2.This number can be exceeded if VEM has available memory.

Single VMware Data Center Support

The Cisco Nexus 1000V can be connected to a single VMware vCenter Server data center object. Note that this virtual data center can span across multiple physical data centers.

vMotion of VSM

vMotion of the VSM has the following limitations and restrictions:

  • vMotion of a VSM is supported for both the active and standby VSM VMs. For high availability, we recommend that the active VSM and standby VSM reside on separate hosts.
  • If you enable Distributed Resource Scheduler (DRS), then you must use the VMware anti-affinity rules to ensure that the two virtual machines are never on the same host, and that a host failure cannot result in the loss of both the active and standby VSM.
  • VMware vMotion does not complete when using an open virtual appliance (OVA) VSM deployment if the CD image is still mounted. To complete the vMotion, either click Edit Settings on the VM to disconnect the mounted CD image, or power off the VM. No functional impact results from this limitation.
  • If you are adding one host in a DRS cluster that is using vSwitch to a VSM, you must move the remaining hosts in the DRS cluster to the VSM. Otherwise, the DRS logic does not work, the VMs that are deployed on the VEM could be moved to a host in the cluster that does not have VEM, and the VMs lose network connectivity.

For more information about vMotion of VSM, see the Cisco Nexus 1000V Software Installation Guide, Release 4.2(1)SV1(4a) .

VMware Lab Manager

VMware Lab Manager does not support using the Cisco Nexus 1000V.

Upgrades

Upgrading the software has the following limitations and restrictions:

  • The upgrade procedure to Release 4.2(1)SV1(4a) has changed depending on the version you are upgrading from.
  • Unlike previous upgrades, disruption free upgrades from Release 4.0(4)SV1(3) and later to Release 4.2(1)SV1(4a) require the VEMs to be upgraded prior to upgrading the VSM.
  • VEM upgrade to Release 4.2(1)SV1(4a) requires a minimum ESX/ESXi version of 4.0 Update 1 Patch 04 or later.
  • VEM Upgrade using VMware Update Manager (VUM) requires vCenter Update 1, VUM Patch 2 or later.

For more information about VMware compatibility, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4a) .

For more information about upgrades, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4a) .

Access Lists

ACLs have the following limitations and restrictions:

Limitations:

  • IPV6 ACL rules are not supported.
  • VLAN-based ACLs (VACLs) are not supported.
  • ACLs are not supported on port channels.

Restrictions:

  • IP ACL rules do not support the following:

fragments option

addressgroup option

portgroup option

interface ranges

  • Control VLAN traffic between the VSM and VEM does not go through ACL processing.

NetFlow

The NetFlow configuration has the following support, limitations, and restrictions:

  • Layer 2 match fields are not supported.
  • NetFlow Sampler is not supported.
  • NetFlow Exporter format V9 is supported
  • NetFlow Exporter format V5 is not supported.
  • The multicast traffic type is not supported. Cache entries are created for multicast packets, but the packet/byte count does not reflect replicated packets.
  • NetFlow is not supported on port channels.

The NetFlow cache table has the following limitation:

  • Immediate and permanent cache types are not supported.

Note The cache size that is configured using the CLI defines the number of entries, not the size in bytes. The configured entries are allocated for each processor in the ESX host and the total memory allocated depends on the number of processors.


Port Security

Port security has the following support, limitations, and restrictions:

• Port security is enabled globally by default.
The feature/no feature port-security command is not supported.

  • In response to a security violation, you can shut down the port.
  • The port security violation actions that are supported on a secure port are Shutdown and Protect . The Restrict violation action is not supported.
  • Port security is not supported on the PVLAN promiscuous ports.

Port Profiles

Port profiles have the following restrictions or limitations:

  • There is a limit of 255 characters in a port-profile command attribute.
  • We recommend that you save the configuration across reboots, which will shorten the VSM bringup time.
  • We recommend that if you are altering or removing a port channel, you should migrate the interfaces that inherit the port channel port profile should migrate to a port profile with the desired configuration, rather than editing the original port channel port profile directly.
  • If you attempt to remove a port profile that is in use, that is, one that has already been auto-assigned to an interface, the Cisco Nexus 1000V generates an error message and does not allow the removal.
  • When you remove a port profile that is mapped to a VMware port group, the associated port group and settings within the vCenter Server are also removed.
  • Policy names are not checked against the policy database when ACL/NetFlow policies are applied through the port profile. It is possible to apply a nonexistent policy.

Telnet Enabled by Default

The Telnet server is enabled by default.

For more information about Telnet, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4a) .

SSH Support

Only SSH version 2 (SSHv2) is supported.

For more information, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4a) .

Cisco NX-OS Commands Might Differ from Cisco IOS

Be aware that the Cisco NX-OS CLI commands and modes might differ from those commands and modes used in the Cisco IOS software.

For information about CLI commands, see the Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(4) .

For more information about the CLI command modes, see the Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4a)

Layer 2 Switching

This section lists the Layer 2 switching limitations and restrictions and includes the following topics:

For more information about Layer 2 switching, see the Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(4) .

No Spanning Tree Protocol

The Cisco Nexus 1000V forwarding logic is designed to prevent network loops so it does not need to use the Spanning Tree Protocol. Packets that are received from the network on any link connecting the host to the network are not forwarded back to the network by the Cisco Nexus 1000V.

Cisco Discovery Protocol

The Cisco Discovery Protocol (CDP) is enabled globally by default.

CDP runs on all Cisco-manufactured equipment over the data link layer and does the following:

• Advertises information to all attached Cisco devices.

• Discovers and views information about those Cisco devices.

CDP can discover up to 256 neighbors per port if the port is connected to a hub with 256 connections.

If you disable CDP globally, then CDP is also disabled for all interfaces.

For more information about CDP, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4a) .

DHCP Not Supported for the Management IP

DHCP is not supported for the management IP. The management IP must be configured statically.

LACP

The Link Aggregation Control Protocol (LACP) is an IEEE standard protocol that aggregates Ethernet links into an EtherChannel.

Cisco Nexus 1000V has the following restrictions for enabling LACP on ports carrying the control and packet VLANs:


Note These restrictions do not apply to other data ports using LACP.


  • If LACP offload is disabled, at least two ports must be configured as part of LACP channel.

Note This restriction is not applicable if LACP offload is enabled. You can check the LACP offload status using the show lacp offload status command.


  • The upstream switch ports must be configured in spanning-tree port type edge trunk mode. For more information about this restriction, see the “Upstream Switch Ports” section.

Upstream Switch Ports

All upstream switch ports must be configured in spanning-tree port type edge trunk mode.

Without spanning-tree portfast on upstream switch ports, it takes approximately 30 seconds to recover these ports on the upstream switch. Because these ports are carrying control and packet VLANs, VSM loses connectivity to the VEM.

The following commands are available to use on Cisco upstream switch ports in interface configuration mode:

  • spanning-tree portfast
  • spanning-tree portfast trunk
  • spanning-tree portfast edge trunk

DNS Resolution

The Cisco Nexus 1010 (1000V) cannot resolve a domain name or hostname to an IP address.

Interfaces

When the maximum transmission unit (MTU) is configured on an operationally up interface, the interface goes down and comes back up.

Caveats

This section includes the following topics:

Open Caveats

The following are descriptions of the caveats in Cisco Nexus 1000V Release 4.2(1)SV1(4a). The ID links you into the Cisco Bug Toolkit.

The caveats are listed in the following categories:

Platform, Infrastructure, Ports, Port Channel, and Port Profiles

 

ID
Open Caveat Headline

1.

CSCti39155

Need to send traffic from the destination VM to learn the vns-binding.

2.

CSCti85986

Cisco Nexus 1000Vcannot support more than 245 port (physical + virtual) per VEM.

3.

CSCti88131

VSM process reloads. Inconsistent state on loss of its remote storage.

4.

CSCti98977

Not able to migrate VC/VSM and normal VM when adding host to DVS.

5.

CSCtj70071

SNMP V3 traps are not getting generated.

6.

CSCtk61730

Incorrect iSCSI multipathing configuration causes module flap or vMotion failure.

7.

CSC tl06194

UCS Blade Oplin adapter comes up with timing issue during Fl reboot.

8.

CSCtl 12586

After VIB upgrade, some of the palo NICs go into INIT state on Fl.

9.

CSCtl75073

The no channel-group command displays the following:
ERROR:No profile matching given profile name.

10.

CSCtn62514

LACP offload configuration is not persisting in stateless.

11.

CSCto02296

Initial installation summary missing in app before migrating.

12.

CSCto11939

AIPC fragment timeout and errors cause module flapping with 2048 VLANs configured.

13.

CSCto76004

L3 Control/ERSPAN vmknic flaps when another vmknic with L3 control is removed.

14.

CSCto80086

PPM inherit error while attaching module with LACP uplink.

15.

CSCtq04886

Eth_port_sec crash during migration in VC with int override in VSM.

16.

CSCtq34977

Intface in "NoPortProfile" state on mode change from LACP to MAC pinning.

17.

CSCtq39502

Adding new veths goes to NoPortProfile during ISSU.

18.

CSCtq71304

ISSU aborted if services memory is full.

19.

CSCtq92519

CDP does not work for certain NIC cards without VLAN 1 allowed.

20.

CSCtq97983

Need to block add/remove of PVLANs on int with no explicit VLANs all.

21.

CSCtr26447

Native VLAN missing in OD if PP is configured as pvlan trunk promiscuous.

22.

CSCtr51078

Backward compatibility of VEMs fails with UUFB feature.

23.

CSCtr55311

Legacy LACP takes 30 minutes to come up after a link flap.

Quality of Service

 

ID
Open Caveat Headline

1.

CSCtl67678

Queueing not programmed on flapping Ethernet port not in a port channel.

2.

CSCtl70759

Addition of new NIC to port-channel fails if profile has queueing policy.

3.

CSCtq34938

Applying policy fails sharing ACL between two class-maps of same policy.

Features

 

ID
Open Caveat Headline

1.

CSCtk65252

PSEC with multiple MAC addresses and PVLAN not supported.

2.

CSCtl00949

Configuring child with no service policy command is causing inherit to fail.

3.

CSCtl04632

Port migration with switchover causing ports to go to "No port-profile".

4.

CSCtr06833

Split brain causes pending ACL/QoS transactions into err-disabled.

5.

CSCtq89961

Snooping does not get applied on sec VLANs if executed in different order

6.

CSCtr09746

Interface configuration fails when veths are nonparticipating due to unreachable module.

VMware

 

ID
Open Caveat Headline

1.

CSCti34737

Removing host with Intel Oplin from DVS causes all ports to reset.

2.

CSCtk02322

After an ESX host exception, the port group configuration on PNIC is changed.

3.

CSCtk07337

Fully qualified domain name/user with port-profile visibility fails.

4.

CSCtk10837

Port-profile visibility feature is not able to update permissions.

5.

CSCtk53802

Improper sync with vCenter when port-profile names have special characters.

6.

CSCts80394

VEM upgrade fails when the scrach space is a network file system.

Resolved Caveats

The following are descriptions of caveats that were resolved in Cisco Nexus 1000V Release 4.2(1)SV1(4a). The ID links you into the Cisco Bug Toolkit.

 

ID
Resolved Caveat Headline

1.

CSCtf97549

VSM-VC communication lost.

2.

CSCth21083

show cdp neighbors command does not display the uplink switch.

3.

CSCti68109

Content missing from HA and Redundancy Configuration Guide.

4.

CSCti87927

VSM Upgrade from 4.0(4)SV1(3) or 4.0(4)SV1(3a) using Upgrade Application.

5.

CSCtj32577

Powering on large numbers of VMs or mass migration of port profiles fails with ACL/QoS

6.

CSCtj73683

Stuck module FSM causes continuous VEM flap.

7.

CSCtk12280

Static/secured MAC address not being learned in the MAC table.

8.

CSCtk12886

VEM sitting before active VSM keeps flapping.

9.

CSCtk19017

Back-to-back clear counters (in < 35s) can move active port to inactive state.

10.

CSCtk34637

Owner field missing for Ethernet ports in show port-profile virtual usage command.

11.

CSCtk36277

ARP reply from VSM is going on cntrl and mgmt.

12.

CSCtk36394

Only system VLANs programmed on PC after rapid LACP member flaps.

13.

CSCtk36811

show interface brief command throws error post change of uplinks.

14.

CSCtk58968

Module does not attach after mode change from access to trunk.

15.

CSCtk59233

GUI installer creates uplink profiles with static port channels.

16.

CSCtk59886

MTU not getting set after port channel is up.

17.

CSCtk60655

HA switchover during PP migration causes Initializing on Veth Intf.

18.

CSCtk62416

SPAN session not going down when last source/destination goes down.

19.

CSCtk65237

VEM not able to attach with two standalone uplinks.

20.

CSCtk67553

Ethernet port goes to admin down state while changing port profiles.

21.

CSCtk70131

VPC subgroup manual comes up though subgroup IDs are not configured.

22.

CSCtk82033

Traffic stops on upgrade when PLAN configuration under port channel.

23.

CSCtk94380

vEthernets going down and auto-deleted on switchover with port profile migration.

24.

CSCtk96758

Installer application GUI layout improper on some Linux hosts.

25.

CSCtk96773

The no feature private-vlan command does not remove switchport mode private vlan.

26.

CSCtl12557

The show vmware vem upgrade status command always displays "in progress".

27.

CSCtl12963

QoS policy on port channel is not getting updated when percentage policer is used.

28.

CSCtl44096

Queue-limit parameter for QoS queueing is not supported.

29.

CSCtl46979

MTU not getting set in VEM when inherited from a parent system port profile.

30.

CSCtl51406

After upgrade, interface is no longer shut down.

31.

CSCtl67124

Ethernet interface inheriting wrong port-profile.

32.

CSCtl80191

Change in queueing parameters while VEM is offline does not take effect.

33.

CSCtl84889

Unable to span TX packets when source port-profile has port-channel configuration.

34.

CSCtl85029

Interfaces up in old PC after removing channel-group command in PP.

35.

CSCtl86903

Remote Secure MACs not installed in PVLAN Host Mode.

36.

CSCtn37614

Fixed stun_set_tunnel_mode() to validate arguments.

37.

CSCtn83745

Single primary VLAN allowed to be associated with 2 isolated VLANs.

38.

CSCto00715

The VEM may stop learning MAC addresses in the Layer 2 table.

39.

CSCto02140

vEthernet trunk MAC's are not programming on all VLANs

40.

CSCto15203

MSP crash on 1.3a to 1.4 on svs upgrade complete command.

41.

CSCto51780

MSP : Switchport cmd getting split and leaking onto PO interface

42.

CSCto90338

Unable to edit existing ACLs when configured to the maximum limit of ACLs.

43.

CSCtr07768

Multicast groups are not programmed on the VEM.

44.

CSCtr55673

Incorrect vendor code is present in offline installation bundles.

MIB Support

The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 1000V Series switch.

The MIB Support List is available at the following FTP site:

ftp://ftp.cisco.com/pub/mibs/supportlists/nexus1000v/Nexus1000VMIBSupportList.html

Available Documents

This section lists the documents used with the Cisco Nexus 1000V and available on Cisco.com at the following url:

http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html

Virtual Network Management Center

Cisco Virtual Network Management Center

This document is to be used in conjunction with the documents listed in the “Available Documents” section.