Cisco Nexus 1000V Datasheet page 3

Both of these components are tightly integrated with the OpenStack environment to provide operational simplicity:
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.
Features
High Availability
The Cisco Nexus 1000V Switch is designed to be resilient with high availability built into the system at multiple
levels:
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.
VSM and VEM communication is built for reliability. In the event of loss of communication with the VSM, the VEMs
can use nonstop forwarding (NSF) to continue to switch traffic according to the last-known configuration.
Enhanced Visibility with Cisco NX-OS
The Cisco Nexus 1000V Switch provides advanced Cisco NX-OS features including:
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.
●
© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Cisco Nexus 1000V for KVM Integration with OpenStack
Page 3 of 8