Table Of Contents
Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(5.1)
Software Compatibility with VMware
Software Compatibility with Cisco Nexus 1000
Microsoft Network Load Balancing
Full Integration with vCloud Director
Cisco Nexus 1000V Support, vCloud Director, vShield Manager Support Matrix
Single VMware Data Center Support
Cisco NX-OS Commands Might Differ from Cisco IOS
DHCP Not Supported for the Management IP
Platform, Infrastructure, Ports, Port Channel, and Port Profiles
VMware vShield Manager Issues Specific to Cisco Nexus 1000V
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(5.1)
Published: August 1, 2013Part Number: OL-25393-01This document describes the features, limitations, and caveats for the Cisco Nexus 1000V Release 4.2(1)SV1(5.1) software. Use this document in combination with documents listed in the "Related Documentation" section. The following is the change history for this document.
Part Number Revision Date DescriptionOL-25393-01
A0
01/31/2012
Created release notes for Release 4.2(1)SV1(5.1).
B0
02/07/2011
Added resolved caveat CSCtx50236.
C0
02/09/2012
Removed CSCtn62136 from the Resolved Caveats.
D0
04/10/2012
Updated the following sections:
•Full Integration with vCloud Director
•Cisco Nexus 1000V Support, vCloud Director, vShield Manager Support Matrix
•VMware vShield Manager Issues Specific to Cisco Nexus 1000V
E0
04/24/2012
Revised the description of the Cisco Network Segmentation Manager in the "Full Integration with vCloud Director" section.
F0
05/01/2012
Added open caveat CSCtz12186.
G0
06/01/2012
Added VXLAN configuration limits.
H0
06/15/2012
Updated descriptions in configuration limits table.
I0
06/29/2012
Added open caveats CSCty59712 and CSCua16092.
J0
08/24/2012
Removed the reference to the Getting Started Guide.
K0
09/25/2012
Added open caveat CSCub22714.
L0
02/04/2013
Added sentence in Microsoft Network Load Balancing section that, Microsoft NLB in unicast mode is the only mode currently supported.
M0
06/06/2013
Added open caveat CSCud38040
N0
08/01/2013
Updated the "LACP" section and added the "Upstream Switch Ports" section.
Contents
This document includes the following sections:
•Obtaining Documentation and Submitting a Service Request, page 21
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 the Cisco Nexus 1000V and can be managed as if it were a line card in a physical Cisco switch.
The 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 the Cisco Nexus 1000V supports vSphere 4.1.0 and 5.0.0 release trains.
Support for vSphere 4.0.0 is discontinued in this release of the Cisco Nexus 1000V. For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(5.1).
Note All virtual machine network adapter types that VMware vSphere supports are supported with the 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 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(5.1).
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.
New Software Features
The following new software features are included in this release:
•Microsoft Network Load Balancing
•Full Integration with vCloud Director
•Cisco Nexus 1000V Support, vCloud Director, vShield Manager Support Matrix
Installer Enhancements
The Cisco Nexus1000V Installation Management Center is now a standalone Java application that can install the Cisco Nexus1000V VSM or VEM.
The Cisco Nexus1000V Installation Management Center supports a single flow for installing the Cisco Nexus1000V VSM in an HA pair, and can migrate the host on which it was deployed as a module.
For more information, see the Cisco Nexus 1000V Installation and Upgrade Guide, Release 4.2(1)SV1(5.1).
VXLAN
A Virtual Extensible Local Area Network (VXLAN) is a new LAN segmentation technology that enables scalable network isolation in the cloud. In a VXLAN, an entire Layer 2 frame is encapsulated in UDP, and a 24-bit VXLAN identifier is included. A VXLAN offers the following advantages:
•Support for 16 million logical networks
•Ability to cross Layer 3
•Tunneling between VEMs
•Virtualized network services with vPath 1.5
In addition, the VXLAN has been submitted to the IETF for standardization.
For more information, see the Cisco Nexus 1000V VXLAN Configuration Guide, Release 4.2(1)SV1(5.1).
Microsoft Network Load Balancing
Microsoft Network Load Balancing (NLB) is a clustering technology offered by Microsoft as part of the Windows server operating systems. Clustering enables a group of independent servers to be managed as a single system for higher availability, easier manageability, and greater scalability.
You can configure virtual Ethernet interface (vEths) to run Microsoft NLB in (default) unicast mode. You must configure the Cisco Nexus 1000V before you configure Microsoft NLB on Windows virtual machines (VMs). Microsoft NLB in unicast mode is the only mode currently supported, multicast mode and IGMP multicast mode is not supported on the Cisco Nexus 1000V.
For more information, see the Cisco Nexus 1000VLayer 2 Switching Configuration Guide, Release 4.2(1)SV1(5.1).
Redundant Routing Protocols
In Cisco Nexus 1000V Release 4.2(1)SV1(5.1), you can configure a virtual Ethernet interface and port profile to support the following redundant routing protocols:
•VRRP (Virtual Router Redundancy Protocol)
•CARP (Common Address Redundancy Protocol)
•HSRP (Hot Standby Router Protocol)
•User-defined custom routing protocols (identified by control packet header fields)
For more information, see the Cisco Nexus 1000VLayer 2 Switching Configuration Guide, Release 4.2(1)SV1(5.1).
ACL Logging
The ACL Logging feature allow users to monitor flows that hit specific ACLs. The ACLs can be configured with the optional log keyword in each of the ACEs. When the option is configured, statistics for each flow that matches the permit or deny conditions of the ACL entry are logged in software. You can also choose to log entries that matches the implicit deny rule of the ACL.
Full Integration with vCloud Director
The Cisco Nexus 1000V is fully integrated with VMware vCloud Director 1.5.1. The vCloud Director provides an abstraction layer that enables cloud service providers to provide an infrastructure as a service (IaaS) to various tenant organizations. vCloud Director also allows the tenant organizations to manage resources such as virtual data centers (vdcs), vApps, networks, and network pools.
The Cisco Network Segmentation Manager (NSM) feature of Cisco Nexus 1000V enables integration with VMware's vCloud Director and supports the following type of Network Pools:
•Port-group backed pools
•VLAN backed pools
•Network isolation backed pools (via the VXLAN)
For more information, see the Cisco Nexus 1000V Network Segmentation Manager Configuration Guide, Release 4.2(1) SV1(5.1).
Cisco Nexus 1000V Support, vCloud Director, vShield Manager Support Matrix
The first Cisco Nexus 1000V release that works with vCloud Director 1.5.1 and vShield Manager 5.0.1 to support three types of networks is Cisco NX-OS Release 4.2(1)SV1(5.1a) which will be released in Q2 CY 2012. More details will be provided in the Release notes of Release 4.2(1)SV1(5.1a).
Table 1 shows the support matrix.
For a list of open caveats related to VMware vShield Director and Cisco Nexus 1000V, see the "VMware vShield Manager Issues Specific to Cisco Nexus 1000V" section.
Limitations and Restrictions
The Cisco Nexus 1000V has the following limitations and restrictions:
•Single VMware Data Center Support
•Cisco NX-OS Commands Might Differ from Cisco IOS
•DHCP Not Supported for the Management IP
•LACP
Configuration Limits
Table 2 shows the Cisco Nexus 1000V configuration limits:
Table 2 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 DatacentersMaximum 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 or VXLANs across all VEMs
2048 (any combination of VLANs and VXLANs)
1024 (any combination of VLANs and VXLANs)
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 (DVS) per vCenter with VMware vCloud Director (vCD)
12
12
Distributed Virtual Switches (DVS) per vCenter without VMware vCloud Director (vCD)
32
32
vCenter Server connections
1 per VSM HA Pair1
1 per VSM HA Pair1
Maximum latency between VSMs and VEMs
5ms
5ms
Per DVS Per Host Per DVS Per HostVirtual 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 channel
256
8
128
4
Physical trunks
512
—
256
—
Physical NICs
—
32
—
16
vEthernet trunks
256
8
128
4
ACL
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 map
128
128
64
64
QoS class map
1024
1024
512
512
QoS instances
2048
256
1024
128
Port security
2048
216
1024
108
MultiCast groups
512
512
256
256
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 datacenter object. Note that this virtual datacenter 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), 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 a 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(5.1).
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 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(5.1).
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(5.1).
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(5.1).
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(5.1).
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, 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(5.1).
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.
The 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 by 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, the 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:
•VMware vShield Manager Issues Specific to Cisco Nexus 1000V
Open Caveats
The following are descriptions of the caveats in Cisco Nexus 1000V Release 4.2(1)SV1(5.1). 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
Platform, Infrastructure, Ports, Port Channel, and Port Profiles
Quality of Service
Features
VMware
Resolved Caveats
The following are descriptions of caveats that were resolved in Cisco Nexus 1000V Release 4.2(1)SV1(5.1). The ID links you into the Cisco Bug Toolkit.
ID Resolved Caveat Headline1.
Add support for the show port-channel load-bal forwarding-path command.
2.
The module vem no execute vemcmd show l2 command truncates output.
3.
There is an erroneous message from dhcpd when the VSM boots up.
4.
The system update vem feature level command needs improvement.
5.
The current nightly image is unable to dump netstack core file.
6.
Syslog detection of duplicate IP addresses in the active VSM is needed.
7.
Prevent or warn users from using duplicate VLANs across port profiles.
8.
The SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED error message has an invalid error ID.
9.
The enhancement to ensure /var/sysmgr partition does not get filled up.
10.
The show port-channel load-balance command shows B: ERROR: bad format: non escaped %.
11.
VSM process reloads. Inconsistent state on loss of its remote storage.
12.
Port-channel numbers are missing from the show interface brief command output.
13.
A stuck module FSM causes continuous VEM flaps.
14.
Static or secured MAC addresses are not learned in the MAC address table.
15.
The ip domain-lookup command is repeated twice in the show running-config command output.
16.
CSCtl12586
After VIB upgrade, some of the palo NICs go into INIT state on Fl.
17.
The vem-swiscsi process fails to exit when no "Software iSCSI" device is found.
18.
Addition of new NIC to port-channel fails if profile has queueing policy.
19.
The show port-channel load-balance command output is incorrect for the hashing algorithm.
20.
A single primary VLAN is allowed to be associated with two isolated VLANs.
21.
The show interface command shows incorrect duplex when using Virtual Connect.
22.
There is inconsistent usage of no shutdown in the monitor session command.
23.
The install all command fails for final images.
24.
A PPM inherit error occurs while attaching a module with a LACP uplink.
25.
Port-profiles with a forward slash are unable to associate to vEth.
26.
MSP fails while a module comes up -- the port channel interface changed.
27.
The Cisco Nexus 1000V VSM OVA installs have locked ISO mounted.
28.
VEM-support is missing the show l2-emergency-aging-stats command.
29.
A port-channel member goes to NoPortProfile-moved across different port profiles.
30.
Adding new veths goes to NoPortProfile during ISSU.
31.
A VM is not reachable via the network after vMotion with IPSG enabled.
32.
A vEth interface goes to NoPortProfile with no error in the ACC log.
33.
Control packets should be dropped if the signature does not match.
34.
ISSU aborted if services memory is full.
35.
A validation check is needed when removing pVLAN mapping command from a child port profile.
36.
A Cisco Nexus1000V cseSysCPUUtilization.0 not reflect CPU usage.
37.
Need to block add/remove of PVLANs on int with no explicit VLANs all.
38.
Multicast groups are not programmed on the VEM.
39.
Dummy entries and an AIPC packet drop exist in the show SVS neighbor command.
40.
Native VLAN missing in OD if PP is configured as PVLAN trunk promiscuous.
41.
Monitor session with a port channel as a destination fails to send traffic.
42.
Backward compatibility of VEMs fails with UUFB feature.
43.
Monitor session with a port-profile destination causes a service failure.
44.
The vem-swiscsi process fails to exit when no "Software iSCSI" device is found.
45.
Implement sanity-check in the sfqosagent when the same global policy is received.
46.
Entering the default switch trunk native vlan command results in an interface flap.
47.
The Cisco Nexus 1000V VSB cannot send a %SYSMGR-2-HASWITCHOVER_START message to a syslog server.
48.
The show process cpu history command does not give correct data.
49.
Interfaces added to a monitor session port profile receive a VLAN_MISCONFIG error.
50.
VEM-health: line 170 receives an error on a fresh install.
51.
Port disconnect callback must never return failure.
52.
The VMS reports an error message when zero virtual Ethernet interfaces exists on the Cisco Nexus 1000V.
53.
The show running-config command displays the svs license volatile command as svs volatile license.
54.
Memory Leak in port-profile process.
55.
VEM uses 1.3 opcode after an upgrade to NX-OS release 4.2(1)SV1(4a).
56.
Platform changes to remove CD mount dependency.
57.
VMs must be pinned to same the SGID for SPAN to work.
58.
The Cisco Nexus 1000V show license usage package command does not display all licensed VEMs.
59.
VSM crashed when SNMP polling for system LEDs MIB.
60.
An interface comes up with speed settings as unknown enum 110.
61.
Reloading the VSM removes non-system VLANs from one port-channel interface.
62.
Adding a second pNIC using mac-pinning degrades network performance.
63.
A virtual Ethernet interface has an Internal-Fail errDisable after VEM bring up.
64.
Delete failures for an ACL must be handled.
65.
A port-profile went to out-of-sync state.
66.
Time change may result in unnecessary transmission of LACP PDUs.
67.
The underscore character (_) appears in the Cisco Nexus 1000V switch name.
68.
A VM named "management" is unable to attach to a Cisco Nexus 1000V.
69.
TCP connections may fail or hang with "tcp state-checks" enabled on the VSM.
70.
Designated SG_ID does not getting elected in the upstream port channel.
71.
A PSOD occurs when a VM uses DHCP option 82 for IP assignment.
VMware vShield Manager Issues Specific to Cisco Nexus 1000V
The following open caveats are specific to VMware vShield Manager and the Cisco Nexus 1000V.
•CSCtx69398 - Unable to change the segment ID range on vShield Manager under certain conditions.
Symptom: A new segment ID range is rejected if it does not exclude IDs that already have been in use.
Conditions: This symptom might be seen when you try to change the segment ID range that excludes IDs that have already been in use.
Workaround: Use a new segment ID range that is a superset of the existing segment ID range.
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
Related Documentation
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(5.1)
Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(5.1)
Cisco Nexus 1010 Management Software Release Notes, Release 4.2(1)SP1(3)
Install and Upgrade
Cisco Nexus 1000V Installation and Upgrade Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1010 Virtual Services Appliance Hardware Installation Guide
Cisco Nexus 1010 Software Installation and Upgrade Guide, Release 4.2(1)SP1(3)
Configuration Guides
Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V License Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Network Segmentation Manager Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V VXLAN Configuration Guide, Release 4.2(1)SV1(5.1)
Cisco Nexus 1010 Software Configuration Guide, Release 4.2(1)SP1(3)
Programming Guide
Cisco Nexus 1000V XML API User Guide, Release 4.2(1)SV1(5.1)
Reference Guides
Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(5.1)
Cisco Nexus 1000V MIB Quick Reference
Cisco Nexus 1010 Command Reference, Release 4.2(1)SP1(3)
Troubleshooting and Alerts
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV1(5.1)
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
Virtual Wide Area Application Services (vWAAS)
Cisco Virtual Wide Area Application Services (vWAAS)
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 What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Internet Protocol (IP) addresses used in this document are for illustration only. Examples, command display output, and figures are for illustration only. If an actual IP address appears in this document, it is coincidental.
© 2012-2013 Cisco Systems, Inc. All rights reserved.