Guest

Cisco Nexus 1000V Switch for VMware vSphere

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

  • Viewing Options

  • PDF (293.1 KB)
  • Feedback
Cisco Nexus 1000V Release Notes, Release 4.2(1) SV1(4b)

Table Of Contents

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

Contents

Introduction

Software Compatibility

Software Compatibility with VMware

Software Compatibility with Cisco Nexus 1000

New and Changed Information

Changed Software Features

High Availability

New Software Features

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

Obtaining Documentation and Submitting a Service Request


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


Updated: August 1, 2013
Part Number: OL-22822-03 E0

This document describes the features, limitations, and caveats for the Cisco Nexus 1000V Release 4.2(1)SV1(4b) 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-03

A0

4/16/2012

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

B0

5/06/2012

Added a link to caveat CSCty78076.

C0

6/15/2012

Updated descriptions in configuration limits table.

D0

6/29/2012

Added open caveats CSCty59712 and CSCua16092.

E0

8/01/2013

Updated the "LACP" section and added the "Upstream Switch Ports" section.


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, page 16

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

Software Compatibility with Cisco Nexus 1000

Software Compatibility with VMware

The servers that run the Cisco Nexus 1000 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(4b).


Note All virtual machine network adapter types that VMware vSphere supports are supported with Cisco Nexus 1000. 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 1000

This release supports nondisruptive software upgrades from Release 4.0(4)SV1(3) 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(4b).

New and Changed Information

This section provides the following information about this release:

Changed Software Features

New Software Features

Changed Software Features

The following software features are changed in NX-OS Release 4.2(1)SV1(4b):

High Availability.

High Availability

The behavior of the high availability feature has changed in NX-OS Release 4.2(1)SV1(4b):

You can clear the secondary VSM configuration and add it to the existing primary VSM.

You can clear the primary VSM configuration and add it to the existing secondary VSM.

For more information, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.2(1)SV1(4b).

New Software Features

Cisco NX-OS Release 4.2(1)SV1(4b)is a maintenance release that includes bug fixes. It does not include new software features.

Limitations and Restrictions

The Cisco Nexus 1000V has the following 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

Cisco Discovery Protocol

DHCP Not Supported for the Management IP

LACP

Upstream Switch Ports

DNS Resolution

Interfaces

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 Pair1

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

82

ACEs per ACL

128

1282

64

642

ACL instances

2048

256

1024

128

NetFlow policies

32

8

16

4

NetFlow instances

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 instances

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(4b).

VMware Lab Manager

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

Upgrades

When you upgrade to Cisco NX-OS Release 4.2(1)SV1(4b), you need to follow a different upgrade path depending on whether you start from Release 4.0(4)SV1(3) and its maintenance updates, or from Release 4.2(1)SV1(4) and its updates. In the former case, you must upgrade the VEMs before the VSM; in the latter case, you should follow the regular ISSU flow of upgrading the VSM first.

For detailed information and step-by-step instructions, see the Cisco Nexus 1000v Software Installation and Upgrade Guide, Release 4.2(1)SV1(4b).

For upgrade assistance, see the interactive upgrade tool Cisco Nexus 1000V and VMware ESX/ESXi Upgrade Utility.

For additional information about software installation, watch the video Installing VSMs and VEMs Using the Nexus 1000V Installation Manager Center.

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


Note If you need to upgrade from Cisco NX-OS Release 4.0(4)SV1(3x) to Cisco NX-OS Release 4.2(1)SV1(5.1), you must first upgrade to Release 4.2(1)SV1(4b) and then upgrade immediately to Release 4.2(1)SV1(5.1). In this upgrade path, Release 4.2(1)SV1(4b) serves only as a transitory release.



Note If customers are running Release 4.2(1)SV1(4b) in a production environment and they want to upgrade to a 4.2(1)SV1(5.x) release, we recommend upgrading to Release 4.2(1)SV1(5.2) or a later release.


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.

Port-profile migration can fail if you attempt to migrate 100 or more ports from one port group to another on the same host. This issue can occur if there are 160 vEth interfaces present on a host and you attempt to move 100 or fewer port profiles on the same host. To avoid this issue, reduce the number of interfaces being migrated at one time. Approximately 10 interfaces can be migrated at one time.

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(4b).

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(4b).

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(4b)

Layer 2 Switching

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

No Spanning Tree Protocol

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(4b).

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 Upstream Switch Ports.

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

Resolved Caveats

Open Caveats

The following are descriptions of the caveats in Cisco Nexus 1000V Release 4.2(1)SV1(4b). 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

Quality of Service

Features

VMware

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 1000cannot support more than 245 port (physical + virtual) per VEM.

3.

CSCti98977

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

4.

CSCtj70071

SNMP V3 traps are not getting generated.

5.

CSCtk61730

Incorrect iSCSI multipathing configuration causes module flap or vMotion failure.

6.

CSCtl06194

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

7.

CSCtl12586

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

8.

CSCtl75073

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

9.

CSCtn62514

LACP offload configuration is not persisting in stateless.

10.

CSCto02296

Initial installation summary missing in app before migrating.

11.

CSCto11939

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

12.

CSCto76004

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

13.

CSCtq04886

Eth_port_sec failure during migration in VC with interface override in VSM.

14.

CSCtq34977

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

15.

CSCtq39502

Adding new vEth interface goes to NoPortProfile during ISSU.

16.

CSCtq71304

ISSU aborted if services memory is full.

17.

CSCtq92519

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

18.

CSCtq97983

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

19.

CSCtr26447

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

20.

CSCtr34519

Continuous SNMP polling causes high CPU usage.

21.

CSCtr36181

Integrate Apache with netstack.

22.

CSCtr51078

Backward compatibility of VEMs fails with UUFB feature.

23.

CSCtr55311

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

24.

CSCts24105

The load-interval counter command configuration is not working.

25.

CSCts50066

Post module flap violated port is secured and the secured port is violated.

26.

CSCts58719

After a write erase command, the user is forced to reregister the extension on a VC.

27.

CSCtu10144

A virtual Ethernet interface as trunk has pinning issue in MN ESX hosts.

28.

CSCtu14575

An ICMP packet size of 8922 to 8972 does not work with the Layer 2 VSG and VXLAN.

29.

CSCtu31037

An ICMP packet size of 1423to 1427 does not work with Layer 2 VSG and VXLAN.

30.

CSCtv00064

An ICMP packet size greater than 1378 does not work with Layer 3 VSG.

31.

CSCtw56889

Cisco Nexus 1000V does not recompute the UDP checksum when option 82 is inserted.

32.

CSCtw69713

A module does not come up if the lowest numbered vmnic on Cisco Nexus 1000V is down.

33.

CSCtw93579

Active VSMs CPU utilization is more than 50% when there are 512 groups.

34.

CSCtw96064

The show tech-support dvs command does not have output related to DHCP snooping.

35.

CSCtx02138

ERSPAN supports an MTU larger than 1500 bytes.

36.

CSCtx03892

Migrating to Cisco Nexus 1000V multicast with 224.0.0.1 address stopped working.

37.

CSCtx06864

A native VLAN configured on the interface port channel, is not programmed on VEM.

38.

CSCtx30435

After upgrading the VEM to Cisco NX-OS Release 4.2(1)SV1(5.1), two Cisco VIBs are installed.

39.

CSCtx32992

Multicast drops count as vEth output drops.

40.

CSCtx39449

Observing module flaps and disconnection of the SVS connection.

41.

CSCtx41516

Disable the snmp trap link-status command on a vEthernet interface.

42.

CSCtx61013

The vMotion syslog is missing while doing a vMotion.

43.

CSCty40233

Following VSM reload, an incorrect native VLAN displays for a port-channel interface.

44.

CSCty41817

vEth interfaces with port security enabled go to error disabled state.

45.

CSCty55882

vEth interfaces with port security configured fail to ping following a vMotion.

46.

CSCty59712

If you add a primary PVLAN as the SPAN/ERSPAN source, its promiscuous trunk members are not added to the SPAN session.

47.

CSCtz01790

Free memory check needs to be corrected while checking for ISSU.

48.

CSCtz25589

An error message appears while launching the installer application.

49.

CSCua16092

If you add a PVLAN promiscuous trunk port channel or Ethernet interface as the SPAN/ERSPAN source, some of the VLANs allowed on the port might not be spanned.


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.


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".

1.

CSCtl67678

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

2.

CSCtq34432

The service-policy command leaks to veth-no service-policy command with the wrong policy name.

3.

CSCtq34938

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

4.

CSCtq89961

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

5.

CSCtr06833

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

6.

CSCtr09746

Interface configuration fails when vEthernet interfaces are nonparticipating due to unreachable module.

7.

CSCtu36119

QoS marking limitation is VCD environment.

8.

CSCtw72196

Queues are not created when adding a class map in a policy map that has no cl.


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 scratch space is a network file system.

7.

CSCty78076

The VUM fails on an upgrade from Cisco NX-OS Release 4.0(4)SV1(3d) to Cisco NX-OS Release 4.2(1)SV1(4b).


Resolved Caveats

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

 
ID
Resolved Caveat Headline

1.

CSCti88131

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

2.

CSCto80086

PPM inherit error while attaching module with LACP uplink.

3.

CSCtq06479

MSP fails while a module comes up and the port-channel interface is changed from one to the other.

4.

CSCtr26721

LACP port channel goes to errdisabled state with large VLAN configurations.

5.

CSCtr83664

The vem-swiscsi process fails to exit when no software iSCSI device is found.

6.

CSCtt38036

Reloading the VSM removes nonsystem VLANs from one port-channel interface.

7.

CSCtt44038

Adding a second pnic using mac-pinning degrades network performance.


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.2(1)SV1(4a)

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

Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4b)

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

Install and Upgrade

Cisco Nexus 1000V Software Installation Guide, Release 4.2(1)SV1(4b)

Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4b)

Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.2(1)SV1(4b)

Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide

Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1)SP1(4)

Configuration Guides

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

Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4b)

Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.2(1)SV1(4b)

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

Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(4)

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

Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.2(1)SV1(4)

Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4b)

Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4b)

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

Programming Guide

Cisco Nexus 1000V XML API User Guide, Release 4.2(1)SV1(4)

Reference Guides

Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(4)

Cisco Nexus 1000V MIB Quick Reference

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

Troubleshooting and Alerts

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

Cisco Nexus 1000V Password Recovery Guide

Cisco NX-OS System Messages Reference

Virtual Security Gateway Documentation

Cisco Virtual Security Gateway for Nexus 1000V Series Switch

Virtual Network Management Center

Cisco Virtual Network Management Center

Network Analysis Module Documentation

Cisco Prime Network Analysis Module Software Documentation Guide, 5.1

Cisco Prime Network Analysis Module (NAM) for Nexus 1010 Installation and Configuration Guide, 5.1

Cisco Prime Network Analysis Module Command Reference Guide 5.1

Cisco Prime Network Analysis Module Software 5.1 Release Notes

Cisco Prime Network Analysis Module Software 5.1 User Guide

Obtaining Documentation and Submitting a Service Request

For information on 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.