Guest

Cisco Nexus 1000V Switch for VMware vSphere

Cisco Nexus1000V Release Notes, Release 4.0(4)SV1(3)

  • Viewing Options

  • PDF (286.2 KB)
  • Feedback
Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3)

Table Of Contents

Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3)

Contents

Introduction

Software Compatibility

New and Changed Information

Changed Software Features

New Software Features

Port Profile System MTU Setting for Uplinks

GUI Configuration Set Up

ERSPAN Type-III Format

Cisco Network Analysis Module

Network Management

Limitations and Restrictions

Configuration Limits

Vmotion of VSM

VMware Lab Manager

Virtual Service Domain

Upgrade

Access Lists

NetFlow

Port Security

Port Profile

Telnet Enabled by Default

SSH Support

Cisco NX-OS Commands May Differ from Cisco IOS

Layer 2 Switching

No Spanning Tree Protocol

MAC Address Table

Maximum Allowed VLANs and MAC Addresses per VLAN

Cisco Discovery Protocol

DHCP Not Supported for the Management IP

LACP

MTU Mismatch After ESX Reboot

Caveats

Open Caveats

Resolved Caveats

MIB Support

Available Documents

Obtaining Documentation and Submitting a Service Request


Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3)


Updated: July 22, 2013
OL-21663-01-E0

This document describes the features, limitations, and caveats for the Cisco Nexus 1000V Release 4.0(4)SV1(3) 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-21663-01

A0

April 29, 2010

Created release notes for Release 4.0(4)SV1(3).

B0

May 17, 2010

Added open caveat CSCtg79060.

C0

May 24, 2010

Added restriction, MTU Mismatch After ESX Reboot.

Added new feature, Port Profile System MTU Setting for Uplinks.

D0

June 3, 2010

Added new feature, Network Management.

E0

August 23, 2010

Added open caveat CSCth99337


Contents

This document includes the following sections:

Introduction

Software Compatibility

New and Changed Information

Limitations and Restrictions

Caveats

MIB Support

Available Documents

Obtaining Documentation and Submitting a Service Request

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

The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This is a requirement for running the ESX 4.0 software.

For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3).

New and Changed Information

This section provides the following information about this release:

Changed Software Features

New Software Features

Changed Software Features

No software features were changed in this release.

New Software Features

The following software features are new in this release:

Port Profile System MTU Setting for Uplinks

GUI Configuration Set Up

ERSPAN Type-III Format

Cisco Network Analysis Module

Network Management

Port Profile System MTU Setting for Uplinks

The system mtu command was introduced to configure an MTU of other than 1500 (the default) for system uplink port profiles. If you use an MTU size of other than 1500 (the default), for example, if you use jumbo frames, an ESX reboot will revert the setting on the physical NIC to 1500. This results in a loss of connectivity because the MTU for the physical NIC and virtual NIC do not match. By configuring the MTU in the system uplink port profile, it is preserved through ESX reboots on physical NICS attached to the Cisco Nexus 1000V.

For information about configuring MTU in the system port profile, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.0(4)SV1(3).

GUI Configuration Set Up

A GUI is provided for initial configuration of the VSM after installing the software. The GUI streamlines your configuration of the following:

Creating the SVS connection between the VSM and vCenter Server, and the resulting connection to the DVS.

Creating the following VMware port group and VLANs:

Control

Packet

Management

Enabling Secure Shell (SSH) and configuring an SSH connection.

Creating a Cisco Nexus 1000V plug-in and registering it on the vCenter Server.

Powering off and then restarting the VSM.

Configuring Layer 3 control.

Configuring VSM high-availability.

For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3).

ERSPAN Type-III Format

The ERSPAN Type-III header frame is an extended format that supports key fields useful for applications such as network management, intrusion detection, and lawful intercept. This header frame is particularly useful in applications where information about the original parameters of the mirrored frame, including those not present in the original frame itself, is required.

For information about the ERSPAN Type-III format, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3).

Cisco Network Analysis Module

Cisco Network Analysis Module (NAM) supports historical reporting and trend analysis for the following:

ERSPAN and NetFlow Data Sources

Interface and Entity MIBs

For more information about Cisco Virtual NAM, see the following documentation:

Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3)

Cisco Network Analysis Module Virtual Blades User Guide, 4.2

ERSPAN and NetFlow Data Sources

NAM monitors the following ERSPAN and NetFlow data source statistics:

Application performance monitoring of ERSPAN data sources

Traffic analysis and reporting of ERSPAN and NetFlow data sources. NAM enables all existing traffic analysis views and reports such as hosts, applications, conversations, VLAN, and QoS

Packet analysis of ERSPAN data sources. The Cisco Nexus 1000V packet captures are limited to headers only

Interface and Entity MIBs

NAM monitors the following interface and entity MIB statistics:

Interface MIB for the managed VSM virtual machine interface

Entity MIB health statistics for the Cisco Nexus 1010

Network Management

Cisco Data Center Network Manager (DCNM) is a management tool that automates the provisioning process. Using a client-server architecture and the XML management interface, DCNM manages and monitors Cisco NX-OS devices. For more information about DCNM, see the Cisco Data Center Network Manager documentation:

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

Limitations and Restrictions

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

Configuration Limits

Vmotion of VSM

VMware Lab Manager

Virtual Service Domain

Upgrade

Access Lists

NetFlow

Port Security

Port Profile

Telnet Enabled by Default

SSH Support

Cisco NX-OS Commands May Differ from Cisco IOS

Layer 2 Switching

Cisco Discovery Protocol

DHCP Not Supported for the Management IP

LACP

MTU Mismatch After ESX Reboot

Configuration Limits

The Cisco Nexus 1000V has the following configuration limits shown in Table 1:

Table 1 Configuration Limits for Cisco Nexus 1000V  

Component
Supported Limit

Maximum Modules

66

Virtual Ethernet (VEM)

64

 

Virtual Supervisor (VSM)

2

 

Hosts

64

 

Active VLANs across all VEMs

512

 

MACs over VLAN within a VEM

1024 (1K)

 

vEthernet interfaces per port profile

1024 (1K)

 

PVLAN

512

Distributed Virtual Switches (DVS) per vCenter

12

 
 
Per DVS
Per Host

Virtual Service Domains (VSDs)

64

6

VSD interfaces

2048

214

vEthernet interfaces

2K

216

Port profiles

256

System port profiles

16

Port channel

256

8

Physical trunks

512

Physical NICs

32

vEthernet trunks

256

8

ACL

128

161

ACEs per ACL

128

161

ACL Interfaces

2048

256

NetFlow policies

32

8

NetFlow interfaces

256

32

SPAN/ERSPAN sessions

64

4

QoS policy map

128

16

QoS class map

1024

128

QoS interfaces

2048

256

Port security

1600

216

MultiCast groups

512

64

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


Vmotion of VSM

Vmotion of VSM has the following limitations and restrictions:

Vmotion of a VSM is supported for both the active and standby VSM VMs. For high availability, it is recommended that the active VSM and standby VSM reside on separate hosts. To achieve this, and prevent a host failure resulting in the loss of both the active and standby VSM, it is recommended that distributed resource scheduling (DRS) be disabled for both the active and standby VSMs.

If you do not disable 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 ISO is still mounted. To complete the Vmotion, either click Edit Settings on the VM to disconnect the mounted ISO, or power off the VM. No functional impact results from this limitation.

VMware Lab Manager

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

Virtual Service Domain

The Virtual Service Domain (VSD) has the following limitations and restrictions:

Vmotion is not supported for the service virtual machine (SVM) and should be disabled.

To prevent loops in the network, configure the following before assigning an SVM to a port profile on the vCenter Server:

Inside port

Outside port

VSD

To prevent it from flooding the network with packets, make sure to configure the inside or outside VSD port profile with a service port.

To prevent loops in the network, when making any changes to the SVM port profile, do the following:

First shut down the SVM.

Make the changes to the SVM port profile.

Verify that the changes to the SVM port profile were applied.

Restart the SVM.

You must remove the control and packet VLANs from the allowed VLAN lists for an inside or outside VSD port profile, such as that used for Vshield.

For more information about VSD, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3).

Upgrade

Upgrading the software has the following limitations and restrictions:

After the VSM feature support level is upgraded to support features in the new release, you cannot downgrade it again to a previous release.

Connectivity to the VSM can be lost during a VEM upgrade when the VSM VM interfaces connect to its own DVS.

Connectivity between the active and standby VSM can be lost during a VEM upgrade when the VEM that is being upgraded provides interface connectivity to one of the VSMs in the pair. In this case, both VSMs become active and lose connectivity. Use the following workaround:

Power off the VSM that is connected to the VEM.

Manually upgrade the VEM that provides interface connectivity to one VSM in the pair.

If you use a proxy server to connect VMware Update Manager (VUM) to the Internet, you may need to disable the proxy before starting a VUM upgrade of your VEMs. In the VMware versions before VUM Update 1, the proxy prevents VUM from communicating locally with the VSM. Automatic VEM upgrades may fail if the proxy is not disabled first.

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

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.

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 Profile

Port profiles have the following restrictions or limitations:

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.0(4)SV1(3).

SSH Support

Only SSH version 2 (SSHv2) is supported.

For more information, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3).

Cisco NX-OS Commands May Differ from Cisco IOS

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

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

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

Layer 2 Switching

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

No Spanning Tree Protocol

MAC Address Table

Maximum Allowed VLANs and MAC Addresses per VLAN.

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

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.

MAC Address Table

In the MAC address table, the forwarding table for each VLAN in a VEM can store up to 1024 MAC addresses.

For more information about the Cisco Nexus 1000V MAC address table, see the Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(3).

Maximum Allowed VLANs and MAC Addresses per VLAN

Table 1-2 lists the allowable number of VLANs and MAC addresses per VLAN that can be configured.

Table 1-2 Allowable VLANs and MAC Addresses Per VLAN

Feature
Maximum Limit

VLANs across all VEMs

512

MAC addresses per VLAN within a VEM

1024 (1K)


For more information about the Cisco Nexus 1000V VLAN configuration, see the Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(3).

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 disabled globally, then CDP is also disabled for all interfaces.

For more information about the Cisco Discovery Protocol, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3).

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.


At least two ports must be configured as part of the LACP channel.

The upstream switch ports must be configured in spanning-tree portfast mode. The LACP negotiation causes upstream switch ports to bounce, as per protocol, before starting the port aggregation process.

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

MTU Mismatch After ESX Reboot

If you use an MTU other than 1500 (the default) for a physical NIC attached to the Cisco Nexus 1000V, then reboots of the ESX can result in a mismatch with the VMware kernel NIC and failure of the VSM and VEM. For example, in networks that use jumbo frames, you may manually configure an MTU of other than 1500. During a power cycle, the ESX reboots and the MTU of the physical NIC reverts to the default of 1500 but the VMware kernel NIC does not. To prevent this mismatch and preserve the MTU for the physical NIC across reboots of the ESX, you must configure the system MTU in the system port profile.

For information about configuring MTU in the system port profile, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.0(4)SV1(3).

For information about recovering from a loss of connectivity due to an MTU mismatch, see the Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3).

Caveats

This section includes the following topics:

Open Caveats

Resolved Caveats

Open Caveats

The following are open caveats in Cisco Nexus 1000V Release 4.0(4)SV1(3). The Bug ID links you into the Cisco Bug Toolkit.

Bug ID
Caveat Headline

CSCsq66077

Shutting an Ethernet interface in Cisco Nexus 1000V VSM is not reflected in the Catalyst 6500 series switches.

CSCsw32257

Shutting down a VSM vEthernet interface is not reflected in the VM.

CSCsw49458

A change to the speed or duplex settings on a physical NIC causes a module flap.

CSCsx11210

The Cisco Nexus 1000V is unable to add match criteria in a QoS class map after changing to match-any.

CSCsy88176

Inaccurate show policy-map interface output occurs if there are numerous policy maps

CSCsz21693

Reloading the iVISOR host removes the VIB package.

CSCta09184

The show policy-map and show class-map commands are not compatible with XML API.

CSCtb29215

The control 0 interface is not shown in the IFMIB.

CSCtb64596

XML API output is invalid for IGMP snooping show commands.

CSCtc05201

A network failure during a VUM upgrade causes the upgrade to fail.

CSCtc66797

VUM does not work over IPv6.

CSCtc54895

VSD ports are untrusted in the VSM.

CSCtc66615

Reapplying a host profile causes an uplink loss.

CSCtc86474

An attempt to configure SGID on an Ethernet interface range results in an internal error.

CSCtd05737

The forwarding IP address at the end of a copy command is disregarded by the software.

CSCtd30975

Default DHCP configurations should not be pushed to VSD and VSM control ports.

CSCtd31838

When copying or deleting a file from a server to the standby VSM, a false error is generated.

CSCtd71556

If control VLAN and packet VLAN are allowed on a VSD service VM, on port flaps/module flaps, and on VSM reloads, the VSD service VM will loop the packets.

CSCte19534

Typing the command show interface counters on the VSM displays a very large value for some counters.

CSCte55714

Unable to change the service port action from forward to drop.

CSCte83981

The show boot command displays incorrect output on the Virtual Supervisor Module when there is no HA pair.

CSCte99459

VSM incorrectly shows the IGMP querier router port as the service port.

CSCtf49849

The automated migration process fails during installation of the VSM.

CSCtf74541

When more than 10 modules are present, configuring vPC-HM through a port-profile fails with a 'service not responding' error.

CSCtf75345

When the mode is changed from Layer 2 to Layer 3 without removing the hosts from VC, one of the ports in the LACP channel goes to suspended state.

CSCtf88688

The ESX server becomes unresponsive when multiple VMs are powered on simultaneously.

CSCtg06441

When in Layer 3 mode, during a VSM or VEM reboot, the LACP channel is not formed at the first attempt and the VEM module attaches to the VSM and detaches continuously a few times.

CSCtg06894

Upgrade to software Release 4.0(4)SV1(3) may fail if you load Release 4.0(4)SV1(2) first immediately followed by Release 4.0(4)SV1(3).

CSCtg19547

The clear port-security dynamic interface command returns ERROR: (null).

CSCtg28878

During an upgrade or a switchover, the ACLCOMP process crashes when a QOS configuration is applied on a port-channel.

CSCtg32555

In Layer 3 mode, with LACP configured on the uplink ports, a VSM switchover might result in the VEM module attaching to the VSM and detaching 2-3 times and the LACP channel being re-formed.

CSCtg43391

VSM goes into warm standby mode when the shut or no shut command is applied on an upstream configured with LACP channel.

CSCtg79060

VMs are not communicating outside the VEM, and the virtual ports are not getting pinned.

CSCth32207

Changing the VSM admin password during GUI configuration disrupts the validation process.

CSCth99337

Host disconnect or PSOD on removal of KL.next beta host from DVS.


Resolved Caveats

The following are caveats that were resolved in Cisco Nexus 1000V Release 4.0(4)SV1(3). The Bug ID links you into the Cisco Bug Toolkit.

Bug ID
Caveat Headline

CSCta29037

The vihostupdate command prevents the installation of multiple bundles.

CSCta97063

VUM cannot be configured to use the proxy for VMware patch URLs instead of the proxy for VSM.

CSCtb49891

Powering VMs on or off causes some VEMs to disconnect and connect randomly

CSCtc18601

An atomic change of a physical NIC port group results in a module removal.

CSCtc33685

Lot of input drops on the virtual port channel host mode (vPC-HM) interface.

CSCtc34071

The help strings for the show commands show system and show vdc are displayed twice with different help strings.

CSCtc34170

The vemcmd show card command displays an incorrect number of processors, processor core, processor sockets, and physical memory.

CSCtd27624

An LACP channel is not formed after a reload. The configuration has a native VLAN.

CSCtd72257

Following a switchover, removing a VSD from an APC port channel interface does not work.

CSCtd73576

IGMP snooping report-suppression is not working correctly.

CSCte16627

The per VEM bind entry count is incorrect when a shut or no shut command is issued on an interface.

CSCte28866

Configuring a Cisco Nexus 1000V with the vlan dot1Q tag native command does not result in the desired behavior and traffic on the native VLAN is not tagged when sent across a trunk.

CSCte35765

Excluding VLAN 1 from the uplink port-profile crashes the Port Profile Manager process.

CSCte44240

Unicast or multicast packet drops might seen if IGMP is enabled on setup with vPC-HM ports.

CSCte55716

Multicast traffic is displayed at the VSM but not at the VEM interface.

CSCte55987

vEthernet interfaces are not in the ifName table.

CSCte77182

IP Source Guard does not work on private VLAN.

CSCte81096

When the VEM disconnects from the VSM, the port-channels configured in the physical NICs are rendered in a state where no communication in or out of those ports is possible.

CSCte81115

The VEM is not accepting messages from the active VSM.

CSCte81179

Cannot remove private VLAN mapping from port-profile.

CSCte84635

There is source MAC address overlap.

CSCte84704

Virtual Interface Manager is stuck.

CSCte84735

The VSM installer does not accept white space for the data center name.

CSCte96034

Non-Cisco switches do not update their MAC address tables when seeing the MAC Move multicast packet from the Cisco Nexus 1000V.

CSCtf07382

The port-profile FSM gets stuck while processing interface addresses.

CSCtf19804

If iSCSI multipathing is enabled on a VMware kernel NIC, and the uplinks are configured in VPC-HM, then multipathing fails if iSCSI pinning is different from VPC pinning.

CSCtf37910

VLAN is not synchronized to the standby VSM.

CSCtf43373

In a vPC-HM topology where the VEM is connected to different upstream switches, when one of the switch goes down and comes back up, there might be intermittent connectivity issues.

CSCtf44351

The VSM does not display a warning when a non-VMK interface is attached to a port-profile with capability L3 control configured.

CSCtf54417

After an ESX server reboots, the MTU settings are lost for the pNICs attached to Cisco Nexus 1000V.

CSCtf71598

Trunk VLANs may be unexpectedly removed from a VEM uplink port.

CSCtf72651

IGMP state on the VEMs might reset to enabled even if the startup-config is in a disabled state.


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 1000 and available on Cisco.com at the following url:

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

General Information

Cisco Nexus 1000V Documentation Roadmap, Release 4.0(4) SV1(3)

Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3)

Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4)SP1(1)

Install and Upgrade

Cisco Nexus 1000V Software Installation Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Software Upgrade Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide

Configuration Guides

Cisco Nexus 1000V License Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1010 Software Configuration Guide, Release 4.0(4)SP1(1)

Programming Guide

Cisco Nexus 1000V XML API User Guide, Release 4.0(4)SV1(3)

Reference Guides

Cisco Nexus 1000V Command Reference, Release 4.0(4)SV1(3)

Cisco Nexus 1000V MIB Quick Reference

Cisco Nexus 1010 Command Reference, Release 4.0(4)SP1(1)

Troubleshooting and Alerts

Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Password Recovery Guide

Cisco NX-OS System Messages Reference

Network Analysis Module Documentation

Cisco Network Analysis Module Software Documentation Guide, 4.2

Cisco Nexus 1000V NAM Virtual Service Blade Installation and Configuration Guide

Network Analysis Module Command Reference Guide, 4.2

User Guide for the Cisco Network Analysis Module Virtual Service Blades, 4.2

Cisco Network Analysis Module Software Release Notes, 4.2

Obtaining Documentation and Submitting a Service Request

For information about obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.


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