Table of Contents

n1000v_rel_notes_521_SM_311a

Cisco Nexus 1000V for Microsoft Hyper-V Release Notes, Release 5.2(1)SM3(1.1a)

First Published: June 8, 2015

This document describes the features, limitations, and bugs for Cisco Nexus 1000V for Microsoft Hyper-V Release 5.2(1)SM3(1.1a). It also explains how to find information about open and closed bugs.

Contents

This document includes the following sections:

- Introduction

- Software Compatibility with Microsoft Servers

- Software Compatibility with Cisco Nexus 1000V

- Upgrading Cisco Network Service Provider (Cisco VSEM) to the Current Release

- Configuration Limits

- Open Bugs

- Resolved Bugs

- Using the Bug Search Tool

- MIB Support

- Documentation Feedback

- Related Documentation

- Obtaining Documentation and Submitting a Service Request

Introduction

Cisco Nexus 1000V provides a distributed, Layer 2 virtual switch that extends across many virtualized hosts. Cisco Nexus 1000V manages a data center. 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.

When server virtualization is implemented, the edge of the network is pushed from the traditional network access layer, which is implemented in physical switches, to the virtual network access layer that is implemented through the software in the server hypervisor. Cisco Nexus 1000V is an intelligent virtual network access layer switch that runs Cisco NX-OS, which is Cisco’s data center operating system common to all of Cisco’s data center products.

Operating inside the Microsoft Hyper-V Hypervisor, Cisco Nexus 1000V supports the Cisco Virtual Network-Link (VN-Link) server virtualization technology to provide the following:

- Policy-based virtual machine (VM) connectivity

- Mobile VM security and network policy

- Nondisruptive operational model for your server virtualization and networking teams

Data center virtualization servers and VMs are not managed the same way as physical servers. Server virtualization is treated as a special deployment, leading to longer deployment time, with a greater degree of coordination among server, network, storage, and security administrators. With the Cisco Nexus 1000V, you have a consistent networking feature set and a configuration and provisioning model for both physical and the virtual networks.

VM networks can use the same network configuration, security policy, diagnostic tools, and operational models as physical server deployments that are connected to physical switches. This unified approach to quicker deployment and troubleshooting makes virtualization environments no different from nonvirtualized deployments.

Developed with Microsoft, Cisco Nexus 1000V is Microsoft certified and integrates with the Windows Server and Systems Center Virtual Machine Manager (SCVMM).

Cisco Nexus 1000V consists of two basic components:

- Virtual Supervisor Module (VSM), also known as the Control Plane (CP). The VSM acts as the supervisor and contains the Cisco CLI, configuration, and high-level features.

- Virtual Ethernet Module (VEM), also known as the Data Plane (DP). The VEM acts as a line card and runs in each Hyper-V virtual switch to handle packet forwarding and other localized functions.

Hyper-V Webinar

Cisco offers a Cisco Nexus 1000V for Microsoft Hyper-V webinar as either a video demonstration or a PDF download. In the webinar, you can learn how the Cisco Nexus 1000V virtual access/distributed switch can simplify your Hyper-V virtual environment through a nondisruptive operational model, policy-based provisioning, and a strong services ecosystem. You can also learn about the Cisco Nexus 1000V architecture, how it integrates with Microsoft SCVMM, and the networking capabilities it brings to Hyper-V environments.

Administrative Model

Cisco Nexus 1000V for Microsoft Hyper-V consists of two distinct administrative entities that manage the environment on the same set of hardware. Each entity has its own separate goals, abilities, and responsibilities.

Server and VM policies can be set only by the server administrator through SCVMM or its management tools. Network policies can be set only by the network administrator through the VSM or its management tools.

Network and server administrators cannot make administrative changes to the system at the same time. Operations such as deployment, upgrade, configuration, and troubleshooting can be carried out in an asynchronous fashion by administrators.

If the network administrator has set up appropriate policies, the server administrator can add, remove, and move both physical hosts and VMs, as well as install physical interfaces in hosts and add virtual interfaces to VMs.

Software Compatibility with Microsoft Servers

Ensure that the servers that run the Cisco Nexus 1000 VSM and VEM are in the Hardware Compatibility list. This release of Cisco Nexus 1000V supports the following server:

- Microsoft Windows Server 2012 R2

For additional compatibility information, see the Cisco Nexus 1000V and Microsoft Hyper-V Compatibility Information, Release 5.2(1)SM3(1.1a)

Software Compatibility with Cisco Nexus 1000V

This release supports upgrades from Release 5.2(1)SM1(5.1) and later.

This section describes how to upgrade Cisco Network Service Provider to the current release. The upgrade procedure for all other components is described in the Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1).

Upgrading Cisco Network Service Provider (Cisco VSEM) to the Current Release

Note Starting with Release 5.2(1)SM3(1.1), Cisco VSEM is referred to as Cisco Network Service Provider.

Upgrading Cisco Network Service Provider from Release 5.2(1)SM3(1.1) to the Current Release

To upgrade Cisco Network Service Provider, perform the following steps:

Step 1 Install the Nexus1000V-NetworkServiceProvider-5.2.1.SM3.1.1a.0.msi from the Cisco Nexus 1000V zip location on the SCVMM server.

Note The installation restarts the SCVMM service, uninstalls the existing Cisco Network Service Provider MSI, and installs the new Cisco Network Service Provider MSI.

After a successful installation, the powershell scripts needed to upgrade VEM are placed in the %ProgramFiles%\Cisco\Nexus1000V\V2\Scripts\VEMUpgrade directory on the SCVMM server (for example, C:\Program Files\Cisco\Nexus1000V\V2\Scripts\VEMUpgrade).

Step 2 Verify that Cisco Network Service Provider is installed correctly by completing the following steps:

a. Click the Start button and choose Control Panel > Programs > Programs and Features .

b. Verify that the current version of the Cisco Nexus 1000V Network Service Provider program is 1.01.100 .

Step 3 Refresh the Cisco Nexus 1000V Extension Manager by completing the following steps:

a. Open the SCVMM console.

b. Navigate to the Fabric workspace.

c. On the Fabric pane, expand Networking , and click Network Service .

d. In the Results pane, right-click Cisco Systems Nexus 1000V extension, and choose Refresh.

Upgrading Cisco Network Service Provider from Release 5.2(1)SM1(5.x) to the Current Release

To upgrade Cisco Network Service Provider, referred to as Cisco VSEM in Release 5.2(1)SM1(5.x), perform the following steps:

Step 1 Install the Nexus1000V-NetworkServiceProvider-5.2.1.SM3.1.1a.0.msi from the Cisco Nexus 1000V zip location on the SCVMM server.

Note The installation restarts the SCVMM service.

After a successful installation, the powershell scripts needed to upgrade VEM are placed in the %ProgramFiles%\Cisco\Nexus1000V\V2\Scripts\VEMUpgrade directory on the SCVMM server. For example, C:\Program Files\Cisco\Nexus1000V\V2\Scripts\VEMUpgrade.

Step 2 Verify that Cisco Network Service Provider is installed correctly by completing the following steps:

a. Click the Start button and choose Control Panel > Programs > Programs and Features .

b. Verify that the current version of the Cisco Nexus 1000V Network Service Provider program is 1.01.100 .

Step 3 Execute the Upgrade-Nexus1000V-Provider.ps1 script to upgrade the Cisco Network Service Provider. On the SCVMM server, the script is located in the %ProgramFiles%\Cisco\Nexus1000V\V2\Scripts\ProviderUpgrade directory (for example, C:\Program Files\Cisco\Nexus1000V\V2\Scripts\ProviderUpgrade). It requires the following inputs as parameters:

– IP address for the Cisco Nexus 1000V VSM

– Username for the Cisco Nexus 1000V VSM

– Password for the Cisco Nexus 1000V VSM

The following is a sample snapshot of the upgrade script:

PS C:\Program Files\Cisco\Nexus1000V\V2\Scripts\ProviderUpgrade>.\Upgrade-Nexus1000V-Provider.ps1

Enter IP Address for the Nexus1000V VSM: 10.105.225.123

Enter Username for the Nexus1000V VSM: admin

Enter Password for the Nexus1000V VSM:

Found the NetworkService vsem connected to the VSM 10.105.225.123

The NetworkService model: Nexus 1000V Chassis

The NetworkService is linked to the old provider. Start upgrading...

Upgrade the provider for the NetworkService: vsem

Upgrade completed

Performing VSEM Refresh with extension ip ==> '10.105.225.123'

---------------------------------------------------------

Retrieve Cisco Extension with IP = 10.105.225.123

---------------------------------------------------------

Cisco Switch Extension Manager with ip '10.105.225.123' is detected on this VMM server.

Reading Cisco Switch Extension Manager now...

This may take a while depending on VSM configuration Size...

Saving the configs of VSM ==> '10.105.225.123'

Upgrade Script Execution Complete

Step 4 Verify that Cisco Network Service Provider is upgraded correctly by completing the following steps:

a. Open the SCVMM console.

b. Navigate to the Fabric workspace.

c. On the Fabric pane, expand Networking , and then click Network Service .

d. In the Results pane, click the corresponding Cisco Systems Nexus 1000V extension and verify that Cisco Systems Nexus 1000V – Version 2 is displayed in the Provider column.

Step 5 Refresh the Cisco Nexus 1000V Extension Manager:

a. Open the SCVMM console.

b. Navigate to the Fabric workspace.

c. On the Fabric pane, expand Networking , and click Network Services .

d. In the Results pane, right-click Cisco Systems Nexus 1000V extension , and choose Refresh .

Configuration Limits

Table 1 shows the Cisco Nexus 1000V configuration limits.

Table 1 Cisco Nexus 1000V Configuration Limits

Component

Per VSM

Per VEM

Access control lists (ACLs)

128

—

ACL instances

2048

216

Active VLANs

2048

—

Application Control Engines (ACEs) per ACL

128

—

Hosts

64

MAC addresses per VLAN

4096

32000

MAC addresses per DVS

32000

—

Multicast groups

512

64

NetFlow interfaces

2048

216

NetFlow policies

64

64

Physical trunks

512

—

PNICs/hosts

32

—

Port channels

256

8

Port profiles

1000 dynamic port profiles (vEthernet)

64 uplink dynamic port profiles

—

Port security

2048

216

Private VLANs (PVLANs)

512

—

Quality of service (QoS) class maps

128

128

QoS instances

2048

216

QoS policy maps

128

16

Network segment

2048

—

Switched Port Analyzer (SPAN)/Encapsulated Remote SPAN (ERSPAN) sessions

64

4

System network segments

32

—

System profiles

32

—

Virtual Ethernet (vEthernet) trunks

Not supported

—

vEthernet interfaces per port profile

1024

—

vEthernet interfaces

2048

216

Reserved-ip per ip pool template

128

—

Netbios-name-server per ip pool template

16

—

DNS-server per ip pool template

16

—

DNS-suffix per ip pool template

16

—

Open Bugs

The following are descriptions of the open bugs in Cisco Nexus 1000V Release 5.2(1)SM3(1.1a). The IDs are linked to the Cisco Bug Search tool.

Table 2 Open Bugs in Cisco Nexus 1000V for Hyper-V Release 5.2(1)SM3(1.1a)

Category/Bug ID

Description

Cisco

Management

CSCur66138

The module from a VSM can go offline if you try to change an active VSM to VEM directly.

Platform

CSCup54800

When you perform a network migration of vNIC after the SCVMM is upgraded to R2, the VEM is not migrated to a new network, although the SCVMM shows that the operation has been completed.

VSG and VEM Interaction

CSCup34712

Jumbo packets of size greater than 4014 get dropped for a Linux VM.

HNV

CSCuo33922

When using HNV with Cisco Nexus 1000V, if a virtual network adapter with a dynamic MAC is attached to Cisco Nexus 1000V, SCVMM tries to change the MAC address to a static address.

Microsoft

Virtual Machine Manager

CSCup54800

VM-network migration of vNIC does not work after an SCVMM upgrade.

Windows Server

CSCuj33348

WS 2012 R2 enters a crash loop when a logical switch is created on the management NIC with VMQ.

See http://support.microsoft.com/kb/2913659 .

CSCuq98489

Switch deletion gets stuck when a scaled host has 200/205 vEths, including VMs and host vNIC.

CSCur77715

The host crashes with Broadcom BCM5709C NetXtreme II GigE NICs and VSG-protected vEths.

CSCuf09114

Bulk vEthernet flaps fail with a Sequence Timeout error for DHCP.

Resolved Bugs

The following are descriptions of the resolved bugs in Cisco Nexus 1000V Release 5.2(1)SM3(1.1a). The IDs are linked to the Cisco Bug Search tool.

Table 3 Resolved Bugs in Cisco Nexus 1000V for Hyper-V Release 5.2(1)SM3(1.1a)

Bug ID

Description

CSCus08112

TOS value is not copied from the L2 LISP inner header to the outer header.

CSCus15610

MAC age-out time configuration causes VEM to go offline.

Using the Bug Search Tool

Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.

Step 1 Go to http://tools.cisco.com/bugsearch .

Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In . The Bug Search page opens.

Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.

Step 3 To search for a specific bug, enter the bug ID in the Search For field and press Return .

Step 4 To search for bugs in the current release:

a. In the Search For field, enter Cisco Nexus 1000V and press Return . (Leave the other fields empty.)

b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.

Tip To export the results to a spreadsheet, click the Export Results to Excel link.

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.

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

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

Documentation Feedback

To provide technical feedback on this document or report an error or omission, please send your comments to nexus1k-docfeedback@cisco.com.

We appreciate your feedback.

Related Documentation

Cisco Nexus 1000V for Microsoft Hyper-V

Cisco Nexus 1000V for Microsoft Hyper-V Documentation

Cisco Nexus 1000V for VMware

Cisco Nexus 1000V for VMware vSphere Documentation

Cisco Virtual Security Gateway

Cisco Virtual Security Gateway Documentation

Cisco Prime Network Services Controller

Cisco Prime Network Services Controller Documentation

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the 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.

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)

© 2015 Cisco Systems, Inc. All rights reserved.