Cisco Nexus 1000V Switch for KVM

Product Overview

• Advanced switching features such as access control lists (ACLs) and port-based access control lists (PACLS).

• Support for highly scalable, multitenant virtual networking through Virtual Extensible LAN (VXLAN).

• Manageability features such as Simple Network Management Protocol (SNMP), NETCONF, syslog, and advanced troubleshooting command-line interface (CLI) features.

• Strong north-bound management interfaces including OpenStack Neutron plug-in support and REST APIs.

Benefits

• Easily deploy your Infrastructure-as-a-service (IaaS) networks

– As the industry's leading networking platform, the Cisco Nexus 1000V delivers performance, scalability, and stability with familiar manageability and control.

• Preserve your existing investment in operation processes and management tools

– You can manage network policies across both physical and virtual environments using the same familiar interfaces with no additional overhead in retraining costs. You can also use your existing network monitoring, management, and troubleshooting tools to manage both environments.

• Simplify virtual networking operations

– With greater visibility into traffic between virtual machines, these switches simplify your network troubleshooting and your network policy management.

– REST APIs facilitate orchestration and management by providing access to numerous server configuration management tools.

• Strengthen security

– By extending network policies and network visibility to the virtual machine level, virtualization-aware networking increases security.

Hypervisor-Independent Architecture

• The virtual Ethernet module (VEM) is deployed on each physical host managed by the Cisco Nexus 1000V as part of the KVM hypervisor.

• The virtual supervisor module (VSM) can be deployed as a virtual appliance on any KVM host or on the Cisco^® Cloud Services appliance.

Figure 1. Cisco Nexus 1000V Architecture

• The VEM is a hypervisor-resident component and is tightly integrated with the KVM architecture.

• The VSM is integrated with OpenStack using the Neutron plug-in (Figure 2).

Figure 2. Cisco Nexus 1000V for KVM Integration with OpenStack

Features

High Availability

• Cisco NX-OS Software, the OS run by the VSM, is specifically designed for high availability at the network, system, and process levels. Critical processes run independently for ease of isolation, fault containment, and upgrades. Processes can restart independently in milliseconds without losing state information, affecting data forwarding, or affecting adjacent devices or services.

• VSMs are typically deployed in active-standby pairs for high availability. The state and configuration remain constantly synchronized between the two VSMs to provide stateful switchover if the active VSM fails.

Enhanced Visibility with Cisco NX-OS

• Enhanced visibility and troubleshooting of virtual machine traffic through features such as Cisco NetFlow and packet statistics.

• Simplified virtual networking operations and manageability through a strong partner ecosystem and features including SNMP, NETCONF, and syslog.

• Advanced switching and security through features such as VXLANs and ACLs.

• Manage network policies across Cisco Nexus 5000, 6000, and 7000 Series Switches as well as the Cisco Nexus 1000V.

• Use REST APIs to deliver better orchestration by creating your own scripts.

• Use existing networking monitoring tools to manage and troubleshoot both environments.

Product Specifications

Maximum Supported Configurations

• 64 hosts per VSM

• 4096 virtual Ethernet ports per vswitch, with 300 virtual Ethernet ports per physical host

• 2048 active VLANs

• 2048 active VXLANs

• 4000 port profiles

• 6 physical NICs per physical host

• 256 PortChannels per vswitch, with 4 PortChannels per physical host

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

– Source MAC address (default)

– Virtual port ID

– Destination IP address and Layer 4 port

– Destination IP address, Layer 4 port, and VLAN

– Destination IP address and VLAN

– Destination MAC address

– Destination Layer 4 port

– Source and destination IP addresses and Layer 4 port

– Source and destination IP addresses, Layer 4 port, and VLAN

– Source and destination IP addresses and VLAN

– Source and destination MAC addresses

– Source and destination Layer 4 ports

– Source IP address and Layer 4 port

– Source IP address, Layer 4 port, and VLAN

– Source IP address and VLAN

– Source MAC address

– Source Layer 4 port

– VLAN only

• Virtual PortChannel Host Mode (Static, MAC address pinning, MAC address pinning relative, manual and subgroup Cisco Discovery Protocol)

• Internet Group Management Protocol (IGMP) Snooping Versions 1, 2, and 3

• Jumbo-frame support; up to 9216 bytes

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

• 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

VXLAN

• Scalable network isolation

• Port statistics

• ACL (ingress only)

• NetFlow (ingress only)

• Multicast mode

• Unicast flooding and learn mode

• Multicast traffic

Management

• Management through Cisco NX-OS CLI, OpenStack's Horizon dashboard, and other configuration management tools

• Layer 3 connectivity between VSM and VEM, recommended through the management interface of the VSM

• Cisco NX-OS CLI console

• 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

• REST API's (Create/Read/Update/Delete)

SNMP MIBs

• Generic MIBs

– CISCO-TC

– SNMPv2-MIB

– SNMP-COMMUNITY-MIB

– SNMP-FRAMEWORK-MIB

– SNMP-NOTIFICATION-MIB

– SNMP-TARGET-MIB

• Configuration MIBs

– ENTITY-MIB

– IF-MIB

– CISCO-ENTITY-EXT-MIB

– CISCO-ENTITY-FRU-CONTROL-MIB

– CISCO-FLASH-MIB

– CISCO-IMAGE-MIB

– CISCO-CONFIG-COPY-MIB

– CISCO-ENTITY-VENDORTYPE-OID-MIB

– ETHERLIKE-MIB

– CISCO-LAG-MIB

– MIB-II

• Monitoring MIBs

– NOTIFICATION-LOG-MIB

– CISCO-PROCESS-MIB

– CISCO-VIRTUAL-NIC-MIB

• Security MIBs

– CISCO-AAA-SERVER-MIB

– CISCO-COMMON-MGMT-MIB

• Miscellaneous MIBs

– CISCO-CDP-MIB

– CISCO-LICENSE-MGR-MIB

– CISCO-ENTITY-ASSET-MIB

Supported Standards

Table 1. IEEE Compliance

Table 2. RFC Compliance

System Requirements

• Ubuntu 12.04 LTS

• Cisco Nexus 1000V VSM

– VSM can be deployed as a virtual machine on Ubuntu 12.04

– Hard disk: 3 GB

– RAM: 4 GB

– 2 virtual CPUs at 1.5 GHz

• Cisco Nexus 1000V VEM

– Hard disk space: 6.5 MB

– RAM: 150 MB

• Compatible with any upstream physical switches, including all Cisco Nexus and Cisco Catalyst^® switches and Ethernet switches from other vendors

• VXLAN requires physical switches that support multicast (RFC 2236) for multicast mode

For More Information

• For more information about the Cisco Virtual Networking portfolio, visit http://www.cisco.com/go/1000v.

• For more information about the Cisco Nexus 1000V Switch for KVM, visit http://www.cisco.com/go/1000v/kvm.

• For more information about Cisco Nexus 1100 Series Cloud Services Platforms, visit http://www.cisco.com/go/1100.

• For more information about the Cisco Nexus 1000V community, visit http://communities.cisco.com/community/technology/datacenter/nexus1000v.

• For more information about Cisco NX-OS Software, visit http://www.cisco.com/go/nxos.