Cisco Nexus 1000V Manual de implantação - Página 19
Procurar online ou descarregar pdf Manual de implantação para Router de rede Cisco Nexus 1000V. Cisco Nexus 1000V 49 páginas. For microsoft hyper-v
Também para Cisco Nexus 1000V: Ficha de dados (8 páginas), Manual de implantação (25 páginas), Manual (6 páginas), Manual de instalação (27 páginas)
Imprimir página
Figure 17.
VEM Representation
Unlike with the VSM, the VEM's resources are unmanaged and dynamic. Although the storage footprint of the
VEM is fixed (approximately 6.4 MB of disk space), RAM use on the Microsoft Hyper-V host is variable, based on
the configuration and scale of the Cisco Nexus 1000V deployment. In a typical configuration, each VEM can be
expected to require 10 to 50 MB of RAM, with an upper limit of 150 MB for a fully scaled solution with all features
turned on and used to their design limits.
Each instance of the Cisco Nexus 1000V is typically composed of two VSMs (in a high-availability pair) and one or
more VEMs. The maximum number of VEMs supported by a VSM is 64.
VSM-to-VEM Communication
The Cisco Nexus 1000V VSM needs to communicate with the VEM to program and monitor virtual switch ports on
the Logical Switch instances (VEMs). The Cisco Nexus 1000V Switch for Microsoft Hyper-V supports only Layer 3
communication between the VSM and the VEMs. In Layer 3 mode, the control information is exchanged as Layer
3 IP packets between the VSM and VEM. Because the VSM and VEM exchange IP traffic, the VSM and VEMs can
be on different subnets as long as routing between the subnets is configured correctly. Layer 3 mode deployment
leads to greater deployment flexibility.
Note:
Unlike the Cisco Nexus 1000V Switch for VMware ESX, which supported both Layer 3 and Layer 2
modes, the Cisco Nexus 1000V Switch for Microsoft Hyper-V supports only Layer 3 mode.
By default the management interface on the VSM (mgmt0 interface) is used for VSM-to-VEM communication. In
Figure 18, the dotted lines show the path taken by VSM-to-VEM communication.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 19 of 48