Cisco Nexus 1000V Manuel de déploiement - Page 6

Parcourez en ligne ou téléchargez le pdf Manuel de déploiement pour {nom_de_la_catégorie} Cisco Nexus 1000V. Cisco Nexus 1000V 25 pages. For microsoft hyper-v
Également pour Cisco Nexus 1000V : Manuel de déploiement (49 pages), Fiche technique (8 pages), Manuel (6 pages), Manuel d'installation (27 pages)

Imprimer la page

Deployment Guide

System Overview

The Cisco Nexus 1000V Series is a software-based switch that extends across multiple hosts running VMware ESX

or ESXi 4.0. It consists of two components: the virtual supervisor module, or VSM, and the virtual Ethernet module, or

VEM. The VSMs are deployed in pairs that act as the switch's supervisors. One or more VEMs are deployed; these

act like line cards within the switch.

The VSM is a virtual appliance that can be installed independent of the VEM: that is, the VSM can run on an VMware

ESX server that does not have the VEM installed. The VEM is installed on each VMware ESX server to provide the

packet-forwarding capability. The VSM pair and VEMs make up a single Cisco Nexus 1000V Series Switch, which

appears as a single modular switch to the network administrator.

Each instance of the Cisco Nexus 1000V Series Switch is represented in VMware vCenter Server as a vNetwork

Distributed Switch, or vDS. A vDS is a VMware concept that enables a single virtual switch to span multiple VMware

ESX hosts. The Cisco Nexus 1000V Series is created in VMware vCenter Server by establishing a link between the

VSM and VMware vCenter Server using the VMware VIM API.

VMware's management hierarchy is divided into two main elements: a data center and a cluster. A data center

contains all components of a VMware deployment, including hosts, virtual machines, and network switches, including

the Cisco Nexus 1000V Series.

Note:

A VMware ESX host can have only a single VEM installed.

Within a VMware data center, the user can create one or more clusters. A cluster is a group of hosts and virtual

machines that form a pool of CPU and memory resources. A virtual machine within a cluster can be run on or

migrated to any host in the cluster. Hosts and virtual machines do not need to be part of a cluster; they can exist on

their own within the data center as well.

Virtual Chassis

The Cisco Nexus 1000V Series uses a virtual chassis model to represent a pair of VSMs and their associated VEMs.

Like any Cisco chassis base platform, the Cisco Nexus 1000V Series virtual chassis has slots and modules, or line

cards, associated with it. The VSMs are always associated with slot numbers 1 and 2 in the virtual chassis. The

VEMs are sequentially assigned to slots 3 through 66 based on the order in which their respective hosts were added

to the Cisco Nexus 1000V Series Switch.

Network Policy Management

Software-based virtual switching presents new data center management challenges. The traditional management

model calls for server administrators to manage the OS and applications while the network administrator manages

the switches and their associated policies. The link between the server and switch, usually a Category 5 cable, is a

clear boundary between administrative roles. The Cisco Nexus 1000V Series management model calls for

collaboration between server and network administrators who are maintaining the configuration of the same piece of

hardware: a VMware ESX host.

Server and network administrators are separate entities with separate responsibilities. The Cisco Nexus 1000V

Series maintains this separation, with distinct roles for each administrator. Collaboration between the administrators

is required, but the Cisco Nexus 1000V Series is designed to provide server and network administrators with a high

level of autonomy.

The Cisco Nexus 1000V Series provides a feature called port profiles to simplify network provisioning with VMware.

Port profiles create a virtual boundary between server and network administrators. Port profiles are network policies

that are defined by the network administrator and exported to VMware vCenter Server. Within VMware vCenter

Server, port profiles appear as VMware port groups in the same locations as a traditional VMware port group would.

The server administrator is free to use the port profile in the same manner as a port group defined by VMware.

Page 6 of 25