Cisco Nexus 1000V - Page 2

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 2 of 8
●
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.
In addition to the virtual form factor, a physical form factor to host all virtual appliances relevant to the Cisco Nexus
1000V Switch is available: the Cisco Nexus 1100-S Virtual Services Appliance.
Hypervisor-Independent Architecture
The Cisco Nexus 1000V Switch for KVM employs the same hypervisor-independent architecture used across
other hypervisors (such as VMware vSphere and Microsoft Hyper-V), and has two components (Figure 1):
●
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