Overview

Overview

This chapter contains the following sections:

Cisco Nexus 1000V for KVM and OpenStack

Cisco Nexus 1000V for KVM is a virtual distributed switch that works with the Linux Kernel-based virtual machine (KVM) open source hypervisor. The Linux KVM hypervisor is ideally suited for OpenStack environments. All major vendors of KVM have adopted OpenStack as their virtualization management tool.

The networking function of OpenStack is controlled and managed by a process called Quantum on the OpenStack controller. Quantum has been extended in such a way that the Cisco Nexus 1000V can now provide the networking capabilities to the compute nodes and the virtual machines (VMs). As Quantum 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 (subnets), such as VLANs, VLAN trunks, and VXLANs
  • IP address pools

Using the Cisco Nexus 1000V for KVM VSM, you create policy profiles (called port profiles on the VSM), which define port classification information, such as security settings (ACLs and so on).

When a VM is deployed, a port profile is dynamically created on the Cisco Nexus 1000V for KVM for each unique combination of policy 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 and subnet configuration. If you use both OpenStack and the VSM to configure VM networks and subnets, the OpenStack and the VSM configurations can become out-of-sync and result in faulty or inoperable network deployments. For information about OpenStack, see the Cisco Nexus 1000V for KVM Virtual Network Configuration Guide.


CDP

Cisco Discovery Protocol (CDP) runs over the data link layer and is used to advertise information to all attached Cisco devices, and to discover and view information about attached Cisco devices. CDP runs on all Cisco-manufactured equipment.

Domains

You must create a domain ID for Cisco Nexus 1000V. This process is part of the initial setup of the Cisco Nexus 1000V when installing the software. If you need to create a domain ID later, use the saves-domain command to configure.

You can establish Layer 3 Control in your VSM domain so that your VSM is Layer 3 accessible and able to control hosts that reside in a separate Layer 2 network.

Configuration Management

The Cisco Nexus 1000V provides you with the capability to change the switch name, configure messages of the day, and display, save, and erase configuration files.

File Management

Using a single interface, you can manage the file system including:

  • Flash memory file systems
  • Network file systems (TFTP and FTP)
  • Any other endpoint for reading or writing data (such as the running configuration).

User Management

You can identify the users currently connected to the device and send a message to either a single user or all users.

NTP

The Network Time Protocol (NTP) synchronizes timekeeping among a set of distributed time servers and clients. This synchronization allows you to correlate events when you receive system logs and other time-specific events from multiple network devices.

SNMP

The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of devices in a network.

NetFlow

NetFlow gives visibility into traffic transiting the virtual switch by characterizing IP traffic based on its source, destination, timing, and application information. This information is used to assess network availability and performance, assist in meeting regulatory requirements (compliance), and help with troubleshooting.

You can also use the Cisco Network Analysis Module (NAM) to monitor NetFlow data sources.

System Messages

You can use system message logging to control the destination and to filter the severity level of messages that system processes generate. You can configure logging to a terminal session, a log file, and syslog servers on remote systems. System message logging is based on RFC 3164.

For more information about the system message format and the messages that the device generates, see the Cisco Nexus 1000V Series NX-OS System Messages Reference.

Troubleshooting

Ping and trace route are among the available troubleshooting tools. For more information, see the Cisco Nexus 1000V for KVM Troubleshooting Guide.