Cisco Nexus 1000V Посібник з розгортання - Сторінка 32
Переглянути онлайн або завантажити pdf Посібник з розгортання для Мережевий маршрутизатор Cisco Nexus 1000V. Cisco Nexus 1000V 49 сторінок. For microsoft hyper-v
Також для Cisco Nexus 1000V: Технічний паспорт (8 сторінок), Посібник з розгортання (25 сторінок), Посібник (6 сторінок), Посібник з встановлення (27 сторінок)

Dynamic Port Profiles
The Cisco Nexus 1000V introduces the concept of the dynamic port profile for Microsoft Hyper-V to support policy
and network separation design in Microsoft SCVMM. When the Microsoft SCVMM administrator deploys a virtual
machine to a Cisco Nexus 1000V port classification and virtual machine network, a dynamic port profile is created
on the Cisco Nexus 1000V VSM and is applied to the virtual switch port on which the virtual machine is deployed.
These dynamic port profiles are shared by all virtual machines that have the same virtual machine network and
port classification. These port profiles are internal to the Cisco Nexus 1000V VSM and must not be edited or
deleted by the Cisco Nexus 1000 VSM administrator.
System Network Segments
System network segments can be used to put virtual switch ports on the Cisco Nexus 1000V VEM in perpetual
forwarding mode. When system network segments are not used, virtual switch ports on the VEM must be
programmed by the VSM before they will start forwarding traffic.
In certain deployments, the administrator may want to always allow traffic on certain switch ports. Figure 28 shows
an of such a deployment. In this topology, the management vNIC of the Microsoft Hyper-V host is attached to a
Cisco Nexus 1000V virtual switch port. When the Microsoft Hyper-V host restarts, all the switch ports are disabled
for forwarding. In this scenario, the Cisco Nexus 1000V VSM will attempt to reprogram all the switch ports on the
Microsoft Hyper-V host. However, the VSM will fail because the Microsoft Hyper-V host will not be reachable
because it is not in the forwarding state.
In such a scenario, the administrator should define the network segment that is used to manage the Microsoft
Hyper-V hosts as a system network segment. Because all ports in a system network segment are in perpetual
forwarding mode, the VSM will be able to reprogram the VEMs across reboot and VSM-to-VEM reconnections.
Figure 28.
To enable perpetual forwarding on switch ports, the network segment and the uplink network must be configured,
respectively, as "system network segment" and "system uplink network," as shown in the following example:
switch(config)# nsm logical network Internal
switch(config-logical-net)# description network for host/VMs behind the DMZ
switchM(config-logical-net)# exit
switch(config)# nsm network segment pool InternalSF
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Management Network Adapter Behind Cisco Nexus 1000V Switch
Page 32 of 48