Cisco Nexus 1000V Руководство по развертыванию - Страница 14

Просмотреть онлайн или скачать pdf Руководство по развертыванию для Сетевой маршрутизатор Cisco Nexus 1000V. Cisco Nexus 1000V 25 страниц. For microsoft hyper-v
Также для Cisco Nexus 1000V: Руководство по развертыванию (49 страниц), Информационный лист (8 страниц), Руководство (6 страниц), Руководство по установке (27 страниц)

Deployment Guide

The VSM maintains a heartbeat with its associated VEMs. This heartbeat is transmitted at 2-second intervals. If the

VSM does not receive a response within 8 seconds, the VSM considers the VEM removed from the virtual chassis. If

the VEM is not responding because of a connectivity problem, the VEM will continue to switch packets in its last

known good state. When communication is restored between a running VEM and the VSM, the VEM is

reprogrammed, causing a slight (1 to 15 second) pause in network traffic.

All communication between the VSM and VEM is encrypted using a 128-bit algorithm.

Domain ID

A physical Ethernet switch typically passes control information between the data plane and the control plane using an

internal network (Cisco switches use an internal network called the Ethernet out-of-band channel [EoBC]) that is not

exposed to the network administrator. This internal network is isolated by design. In the case of the Cisco Nexus

1000V Series, control packets between the VSM and VEM traverse the physical network. A potential although highly

unlikely scenario is the case in which a VEM receives control packets from a VSM that is managing a completely

different Cisco Nexus 1000V Series. If the VEM were to respond to such packets (for example, a request to

reconfigure an interface), the VEM would not forward packets as expected. To prevent this scenario, the Cisco Nexus

1000V Series implements a solution called domain IDs.

A domain ID is a parameter of the Cisco Nexus 1000V Series that is used to identify a VSM and VEM as relating to

one another. The domain ID of the Cisco Nexus 1000V Series is defined when the VSM is first installed and becomes

part of the opaque data that is transmitted to VMware vCenter Server.

Each command sent by the VSM to any associated VEMs is tagged with this domain ID. When a VSM and VEM

share the same domain ID, the VEM will accept and respond to requests and commands from the VSM. If the VEM

receives a command or configuration request that is not tagged with the proper domain ID, that request is ignored.

Similarly, if the VSM receives a packet from a VEM that is tagged with the wrong domain ID, it will be ignored.

The packet interface is used to send selected packets between the VEM and the VSM. This interface is used for only

two types of packets: Cisco Discovery Protocol and IGMP control packets.

The VSM presents a unified Cisco Discovery Protocol view to the network administrator through the Cisco NX-OS

CLI. When a VEM receives a Cisco Discovery Protocol packet, the VEM retransmits that packet to the VSM so that

the VSM can parse the packet and populate the Cisco Discovery Protocol entries in the CLI.

The packet interface is also used to coordinate IGMP across multiple VEMs. For example, when a VEM receives an

IGMP join request, that request is sent to the VSM, which coordinates the request across all VEMs in the switch.

Port profiles are the primary mechanism by which network policy is defined and applied to switch interfaces. A port

profile is a collection of interface-level configuration commands that are combined to create a complete network

policy.

Port profiles are created on the VSM and propagated to VMware vCenter Server as VMware port groups using the

VMware VIM API. After propagation, a port profile appears within VMware vSphere Client and is available to apply to

a virtual machines vNICs.

When the server administrator provisions a new virtual machine, a dialog box pertaining to network configuration

appears. This dialog box is consistent regardless of the presence of the Cisco Nexus 1000V Series: that is, the

workflow for provisioning a new virtual machine does not change when the Cisco Nexus 1000V Series is used. The

server administrator selects the port profiles to apply to each of the virtual machine's vNICs.

Page 14 of 25