Download Cisco Nexus 1000V

Contents Cisco Nexus 1000V Release NotesCisco Nexus 1000V for VMwareSoftware Compatibility with VMwareSoftware Compatibility with Cisco Nexus 1000VNew Features and EnhancementsConfiguration Scale LimitsCisco Nexus 1000V Configuration Scale LimitsCisco VSG Configuration Scale LimitsAVS Configuration Scale LimitsVDP Configuration Scale LimitsImportant Notes and LimitationsConfiguration Container Names Must Be UniqueSingle VMware Datacenter SupportVDPDFAERSPANVMotion of VSMAccess ListsNetFlowPort SecurityPort ProfilesSSH SupportLACPCisco NX-OS Commands Might Differ from Cisco IOSNo Spanning Tree ProtocolCisco Discovery ProtocolDHCP Not Supported for the Management IPUpstream Switch PortsInterfacesLayer 3 VSGCopy Running-Config Startup-Config CommandSNMP User Accounts Must Be Reconfigured After an UpgradeUsing the Bug Search ToolOpen BugsResolved BugsAccessibility Features in Cisco Nexus 1000V MIB SupportObtaining Documentation and Submitting a Service RequestFirst Published: September 22, 2015Last Updated: July 15, 2016 Cisco Nexus 1000V Release NotesThis document describes the features, limitations, and caveats for the Cisco Nexus 1000V, Release 5.2(1)SV3(1.5b) software. Cisco Nexus 1000V for VMwareThe Cisco Nexus 1000V for VMware provides a distributed, Layer 2 virtual switch that extends across many virtualized hosts. The Cisco Nexus 1000V manages a datacenter defined by the vCenter Server. Each server in the datacenter 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 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 with VMwareThe servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This release of the Cisco Nexus 1000V supports vSphere 6.0, 5.5, 5.1, and 5.0 release trains. For additional compatibility information, see the Cisco Nexus 1000V and VMware Compatibility Information. Note VSM hardware versions 7, 8, 9, and 10 are supported. VSM hardware version 11 is not supported. The Cisco Nexus 1000V supports all virtual machine network adapter types that VMware vSphere supports. 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 1000VThis release supports hitless upgrades from Release 4.2(1)SV2(1.1) and later. For more information, see the Cisco Nexus 1000V Installation and Upgrade Guide. New Features and EnhancementsCisco Nexus 1000V 5.2(1)SV3(1.5b) includes the following features, enhancements, and support: Configuration Scale LimitsThe following topics provide configuration scale limit information: Cisco Nexus 1000V Configuration Scale Limits Cisco VSG Configuration Scale Limits AVS Configuration Scale Limits VDP Configuration Scale Limits Cisco Nexus 1000V Configuration Scale Limits The following table lists the configuration scale limit information for the Cisco Nexus 1000V Advanced edition. Note The scale limits for the Cisco Nexus 1000V Essential edition are half of what is stated in the following table. Feature VEM DVS Other Hosts/DVS — 250 (includes gateways) — Total vEth ports 1000 10,240 — Ports per port profile 1024 2048 — Port profiles 6144 6144 — Physical NICs 32 2000 — Physical trunks

This document describes the features, limitations, and caveats for the Cisco Nexus 1000V, Release 5.2(1)SV3(1.3) software. Cisco Nexus 1000V for VMwareThe Cisco Nexus 1000V for VMware provides a distributed, Layer 2 virtual switch that extends across multiple 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 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 with VMwareThe servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This release of the Cisco Nexus 1000V supports vSphere 5.5, 5.1, and 5.0 release trains. For additional compatibility information, see the Cisco Nexus 1000V and VMware Compatibility Information. Note The Cisco Nexus 1000V supports all virtual machine network adapter types that VMware vSphere supports. 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 1000VThis release supports hitless upgrades from Release 4.2(1)SV2(1.1) and later. For more information, see the Cisco Nexus 1000V Installation and Upgrade Guide. New Features and EnhancementsCisco Nexus 1000V 5.2(1)SV3(1.3) includes the following features, enhancements, and support: Configuration Scale LimitsThe following topics provide configuration scale limit information: Cisco Nexus 1000V Configuration Scale Limits Cisco VSG Configuration Scale Limits Cisco AVS Configuration Scale Limits VDP Configuration Scale Limits Cisco Nexus 1000V Configuration Scale Limits The following table lists the configuration scale limit information for the Cisco Nexus 1000V Advanced edition. Note The scale limits for the Cisco Nexus 1000V Essential edition are half of the values stated in the following table. Feature VEM DVS Other Hosts/DVS — 250 (includes gateways) — Total vEth ports 1000 10,240 — Ports per port profile 1024 2048 — Port profiles 6144 6144 — Physical NICs 32 2000 — Physical trunks 32 2000 — vEthernet trunks 32 1024 — Port channels 8 1024 — Active VLANs 4094 4094 — VXLANs (bridge domains) 6144 6144 — VXLAN gateway pairs 1 8 — VXLAN mappings 512/GW 4094 — VXLAN trunks 32 1024 — VXLAN mappings per trunk 512 — — VXLAN VNI 1044 6144 — VTEPs 4 1024 512 per bridge domain BGP peers 8 VSM — — Route reflectors — — 2 per VXLAN control plane MAC addresses 32,000 — — MAC address per VLAN 4094 4094 — DHCP IP bindings 1024 10,240 — ACLs 128 128 — ACEs per ACL — 128 — ACL instances 6000 42,000 6 instances per port Net Flow policies 32,000 flows 64 monitor sessions 64 records 64 exporters — QoS policy maps — 128 — QoS class — 1024 —

This Deep-Dive series is focused on the advantages of Nexus 1000v Solution across spectrum of technologies and how it can be leveraged to enhance your Data Center Virtual Infrastructure to meet the next-generation goals.Cisco Nexus 1000V Series Switches provide a comprehensive and extensible architectural platform for virtual machine (VM) and cloud networking. The switches are designed to accelerate server virtualization and multitenant cloud deployments in a secure and operationally transparent manner.From single hypervisor to now a multi-hypervisor virtual networking solution, Cisco Nexus 1000v has come a long way since its launch few years back. Currently 1000v product-line provides complete solution ranging from Switching, Routing, Firewall, Load-balancing to Cloud-Infrastructure.Featured ExpertVishal Mehta is a Technical Marketing Engineer with Cisco's Data Center Competitive Insights Team based in San Jose, California. Previously he was working as the customer support engineer for Cisco’s Data Center Server Virtualization Technical Assistance Center (TAC) team for the past 3 years with a primary focus on data center technologies such as Cisco Nexus® 5000, Cisco UCS, Cisco Nexus 1000V, and virtualization. He presented at Cisco Live in Orlando 2013, Milan 2014, and San Francisco 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in Electrical and Computer Engineering and has CCIE® certification (# 37139) in Routing/Switching, Service Provider & Data CenterAsk your Questions in the Discussion forums from February 12 through March 4, 2015Part 1: Conquered Territory: Multi-Hypervisor – February 12, 2015 This session will discuss and compare about Nexus 1000v deployments on VMware, Hyper-V and Openstack-KVM hypervisors. Part 2: Meet the 1000v Family: The Secret of Unity – February 17, 2015This session will discuss vPath: The Secret behind uniting Virtual Network Services provided by ASA 1000v, VSG, vWAAS, Nexus 1000v, vNAM.

One or more VLANs.CautionDisruption of connectivity might result if you configure vPC-HM on the Cisco Nexus 1000V when vPC is also configured on the ports of upstream switches that connect to its VEMs.You must have already configured the Cisco Nexus 1000Vsoftware using the setup routine. For information, see the Cisco Nexus 1000V Installation and Upgrade Guide.The Cisco Nexus 1000V must be connected to the SCVMM. You are logged in to the CLI in EXEC mode.When you create a port channel, an associated channel group is automatically created.If Link Aggregation Control Protocol (LACP) support is required for the port channel, you must enable the LACP feature before you can configure it.Network State Tracking is only supported with HP Virtual Connect where one physical link from the Flex-10 fabric appears as four Flex-10 NICs (physical NICs) to the VMkernel.Default SettingsTable 3 Default Settings for Port ChannelsParametersDefaultPort profile typevEthernetPort profile administrative stateall ports disabledPort channelAdmin upLACPDisabledLoad balancing method for Layer 2 interfacesSource and destination MAC addressLoad balancing per moduleDisabledChannel modeonLACP offload(Offloading LACP management to VEMs)EnabledNetwork State Tracking: Broadcast interval5 secondsNetwork State Tracking: Split-network mode actionrepin Network State Tracking: Maximum threshold miss count5 secondsNetwork State Tracking: StateDisabledConfiguring Port ChannelsCreating a Port Profile for a Port ChannelSee the Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide for information about defining a port channel in a port profile, connecting to upstream networks, and pinning a vEthernet interface to a subgroup.Migrating a Channel Group to a Port Profile You can migrate a channel group to a port profile. Before You BeginYou are logged in to the CLI in EXEC mode.ProcedureStep 1 Place the host in maintenance mode.Step 2 Do one of the following: If Dynamic Optimization is enabled, make sure to wait until the virtual machines are migrated to other host(s).Otherwise, manually migrate the virtual machines.Step 3 When all the virtual machines are successfully migrated, from the Cisco Nexus 1000V CLI, create a new Ethernet type port profile for the uplink ports on this host with the needed parameters including the following. One of the following:channel-group auto mode active | passivechannel-group auto mode on mac-pinningCLI overrides on the existing port channels.Step 4 Remove the port channel configuration from the uplink switches. Note The new port channel has a new port channel ID.Step 5 When all the port(s) are moved from the old port profile, use the following command from the Cisco Nexus 1000V CLI to delete the port channels with zero members:no interface port-channel idStep 6 Bring the host out of maintenance mode.Step 7 Use the following command from the Cisco Nexus 1000V to save the running configuration persistently through reboots and restarts by copying it to the startup configuration. copy running-config startup-configStep 8

An upgrade, one of the port profiles with a duplicate name is deleted, which moves the corresponding ports in vCenter into quarantined state. For example, do not create bridge domains with the same name (one uppercase, one lowercase) that point to different segments. See the following examples: This is an example of an uppercase name: switch# show bridge-domain VXLAN14095 Bridge-domain VXLAN14095 (0 ports in all)Segment ID: 12333 (Manual/Active)Mode: Unicast-onlyMAC Distribution: DisableBGP control mode: EnableGroup IP: NULLEncap Mode: VXLAN*State: UP Mac learning: Enabled This is an example of a lowercase name: switch# show bridge-domain vxlan14095Bridge-domain vxlan14095 (0 ports in all)Segment ID: 14095 (Manual/Active)Mode: Unicast-onlyMAC Distribution: DisableBGP control mode: EnableGroup IP: 237.1.1.196Encap Mode: VXLAN*State: UP Mac learning: Enabled Single VMware Datacenter SupportThe Cisco Nexus 1000V for VMware can be connected to a single VMware vCenter Server datacenter object. Note that this virtual datacenter can span multiple physical datacenters. Each VMware vCenter can support multiple Cisco Nexus 1000V VSMs per vCenter datacenter. VDPImplementing VDP on the Cisco Nexus 1000V has the following limitations and restrictions: The Cisco Nexus 1000V supports the Cisco DFA-capable VDP based on the IEEE Standard 802.1 Qbg, Draft 2.2, and does not support the Link Layer Discovery Protocol (LLDP). Therefore, the EVB type, length, value are not originated or processed by the Cisco Nexus 1000V. The VDP implementation in the current release supports a matching LLDP-less implementation on the bridge side, which is delivered as part of the Cisco DFA solution. For more information on the Cisco DFA, see the Cisco DFA Solutions Guide. Timer-related parameters are individually configurable in the station and in the leaf. Connectivity to multiple unclustered bridges is not supported in this release. IPv6 addresses in filter format are not supported in this release. VDP is supported for only segmentation-based port profiles. VDP for VLAN-based port profiles is not supported in this release. The dynamic VLANs allocated by VDP are local to the VEM; they should not be configured on the Cisco Nexus 1000V VSM. VDP is supported on VMware ESX releases 5.0, 5.1, 5.5 and 6.0 in the current release. DFAFabric forwarding mode is not supported under the VLAN configuration. ERSPANIf the ERSPAN source and destination are in different subnets, and if the ERSPAN source is an L3 control VM kernel NIC attached to a Cisco Nexus 1000V VEM, you must enable proxy-ARP on the upstream switch. If you do not enable proxy-ARP on the upstream switch (or router, if there is no default gateway), ERSPAN packets are not sent to the destination. VMotion of VSMVMotion of VSM has the following limitations and restrictions: VMotion of 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