Release Notes for Cisco Nexus 1000V for KVM, Release 5.2(1)SK3(1.1)

Release Notes for Cisco Nexus 1000V for KVM Release 5.2(1)SK3(1.1)

---

First Published: August 1, 2014

Last Updated: May 10, 2016

This document describes the features and limitations for Cisco Nexus 1000V for KVM. It also provides information about how to find information about open and closed bugs.

Contents

This document includes the following sections:

• Introduction
• Cisco Nexus 1000V for KVM Features
• OpenStack Features
• Limitations and Restrictions
• Software Compatibility
• Server and NIC Requirements
• Canonical MAAS and Juju Installation
• Using the Bug Search Tool
• MIB Support

Introduction

Cisco Nexus 1000V for KVM is a virtual distributed switch that works with the Linux Kernel-based virtual machine (KVM) open source hypervisor.

The Cisco Nexus 1000V for KVM, Release 5.2(1)SK3(1.1) is based on the OpenStack Icehouse release.

The networking function of OpenStack is controlled and managed by the OpenStack Neutron Service. Neutron has been extended in a such a way that Cisco Nexus 1000V can now provide the networking capabilities to the compute nodes and the virtual machines (VMs). As Neutron creates and configures its networks for its environment, this configuration is passed to the Cisco Nexus 1000V switch.

Using OpenStack, you create VM networks and subnets on the Cisco Nexus 1000V for KVM by defining components such as the following:

• Tenants
• Network segments, such as VLANs, VLAN trunks, and Virtual Extensible Local Area Networks (VXLANs)
• IP subnets

On the Virtual Supervisor Module (VSM), you create port profiles, which define feature policies for different types or classes of VMs and security policies for the VM’s traffic.

When a VM is deployed, a port profile is dynamically created on the Cisco Nexus 1000V for KVM for each unique combination of policy (or feature) port profile and network segment. All other VMs deployed with the same policy to this network reuse this dynamic port profile.

Note You must consistently use OpenStack for all VM network, subnet, and port configurations. If you create VM networks, subnets, and ports directly on the VSM, the configuration is lost when the OpenStack synchronization occurs. For information about OpenStack, see the Cisco Nexus 1000V for KVM Virtual Network Configuration Guide.

Cisco Nexus 1000V for KVM Features

The Cisco Nexus 1000V for KVM Release 5.2(1)SK3(1.1) supports the following features:

Layer 2 Features

• Layer 2 switch ports and VLAN trunks
• IEEE 802.1Q VLAN encapsulation
• Link Aggregation Control Protocol (LACP): IEEE 802.3ad
• Advanced PortChannel hashing based on Layer 2, 3, and 4 information
• Virtual port channel Host Mode (static, MAC pinning, MAC pinning relative, manual and subgroup CDP)
• Internet Group Management Protocol (IGMP) snooping Versions 1, 2, and 3
• Jumbo-frame support; up to 9216 bytes
• Integrated loop prevention with the Bridge Protocol Data Unit (BPDU) filter without running Spanning Tree Protocol

Multi-Hypervisor Licensing

Cisco Nexus 1000V uses a multi-hypervisor licensing approach, which allows you to migrate a license from one Cisco Nexus 1000V switch platform type to another. For example, you can migrate the license from a Cisco Nexus 1000V for VMware switch to a Cisco Nexus 1000V for KVM. The Cisco Nexus 1000V supports Essential and Advanced license editions. You can swap editions at any time as long as you have the appropriate licenses available for the Advanced edition. Beginning with Cisco Nexus 1000V Release 5.2(1)SV3(1.1), the Advanced license supports license versioning.

Security

• Ingress and egress ACLs on Ethernet and virtual Ethernet ports
• Standard and extended Layer 2 ACLs:

– MAC address and IPv4

– Source MAC address

– Destination MAC address

– EtherType

– VLAN

– Class of service (CoS)

• Standard and extended Layer 3 and 4 ACLs:

– Source IP

– Destination IP

– DSCP

– Precedence

– Protocol (TCP, UDP, Internet Control Message Protocol [ICMP], and IGMP)

– Source port

– Destination port

– TCP flags

– ICMP and IGMP types

– ICMP code

• Port-based ACLs (PACLs)
• Named ACLs
• ACL statistics

VXLANs

• Scalable network isolation
• Port statistics
• ACL
• Netflow
• Multicast mode
• Unicast Flood and Learn mode
• Multicast traffics

High Availability

• Stateful supervisor failover—Synchronized redundant supervisors are always ready for a failover while maintaining a consistent and reliable state.
• Nonstop forwarding—Forwarding continues despite loss of communication between the VSM and Virtual Ethernet Module (VEM).
• Process survivability—Critical processes run independently for ease of isolation, fault containment, and upgrading. Processes can restart independently in milliseconds without losing state information, affecting data forwarding, or affecting adjacent devices or services.
• Branch-office VEM support—This feature extends the datacenter to the branch office with support for hosts in branch offices and VSMs in the central datacenter.

System Management

• Management through OpenStack Representational State Transfer (REST) APIs, CLI, and Horizon dashboard
• Layer 3 connectivity between VSM and VEM, recommended through the VSM management interface
• Cisco NX-OS CLI console
• In-service software upgrade (ISSU)
• Cisco Discovery Protocol Versions 1 and 2
• SNMP (read) v1, v2, and v3
• SNMP ACL
• Enhanced SNMP MIB support
• SSH v2
• Telnet
• Authentication, authorization, and accounting (AAA)
• TACACS+
• RADIUS
• Syslog
• Ingress and egress packet counters per interface
• Network Time Protocol (NTP) RFC 1305
• Domain Name Services (DNS) for management interfaces
• Distributed NetFlow

OpenStack Features

Limitations and Restrictions

Software Compatibility

Table 1 lists the minimum supported software versions required for a Cisco Nexus 1000V for KVM Release 5.2(1)SK3(1.1) deployment.

Note Depending on your specific Cisco Nexus 1000V for KVM release, it is your responsibility to monitor and install all relevant Linux patches on Linux hosts.

Server and NIC Requirements

You can deploy Cisco Nexus 1000V for KVM on the following Cisco UCS servers:

• Standalone rack-mount servers that are managed by Cisco Integrated Management Controller (IMC)
• Integrated rack-mount servers that are managed by Cisco UCS Manager
• Blade servers that are managed by Cisco UCS Manager

Additionally, you can use other servers supported by Canonical. For information, see the following URL:

http://www.ubuntu.com/certification/server/

The following NIC types have been tested and verified:

• Emulex OCe11102-FX 2 port 10 GbE CAN
• Intel X520 DA2 10Gbps 2 port NIC
• Intel I350 1 Gbps
• Intel 82599EB 10 Gbps
• Broadcom 5709 1 Gbps 4 port NIC

See the Cisco Nexus 1000V for KVM Software Installation Guide for additional information about the requirements for the Cisco UCS servers that you use for the nodes in your Cisco Nexus 1000V for KVM deployment.

Canonical MAAS and Juju Installation

Cisco Nexus 1000V for KVM uses the Ubuntu Metal as a Service (MAAS) and Juju tools to facilitate the installation of OpenStack and Cisco Nexus 1000V for KVM. A description of each is as follows:

• Metal as a Service (MAAS)—Tool that sets up and manages the physical infrastructure on which services are deployed.
• Juju—Tool that deploys services, such as OpenStack and the Cisco Nexus 1000V for KVM services to your physical or virtual environment. Juju provides the installation logic (Juju charm) and software packages (Debian packages) to deploy the Cisco Nexus 1000V for KVM.
• OpenStack—Scalable cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter.
• Cisco Nexus 1000V for KVM— Distributed virtual switch (DVS) that works with several different hypervisors. This DVS version is integrated with the Ubuntu Linux Kernel-based virtual machine (KVM) open source hypervisor.

You need to deploy MAAS and Juju before you can deploy OpenStack with the Cisco Nexus 1000V for KVM.

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 for KVM 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.

For a list of MIBs that the Cisco Nexus 1000V for KVM supports, see the Cisco Nexus 1000V for KVM System Management Configuration Guide.

Related Documentation

This section lists the documents used with the Cisco Nexus 1000V for KVM.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the  What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.