Cisco Nexus 1000V Uitrolhandleiding - Pagina 43
Blader online of download pdf Uitrolhandleiding voor {categorie_naam} Cisco Nexus 1000V. Cisco Nexus 1000V 49 pagina's. For microsoft hyper-v
Ook voor Cisco Nexus 1000V: Gegevensblad (8 pagina's), Uitrolhandleiding (25 pagina's), Handmatig (6 pagina's), Handleiding installeren (27 pagina's)
Pagina afdrukken
Beginning with Cisco NX-OS Release 5.2(1)SV1(5.1) for the Cisco Nexus 1000V Switch for Microsoft Hyper-V,
LACP processing can be moved from the control plane (VSM) to the data plane (VEM), as shown in Figure 35.
Figure 35.
The origination and processing of LACP PDUs is now completely offloaded to the VEM. Therefore, you should
enable this feature in any of the scenarios described in the preceding paragraphs, so that the VEM has no
dependence on VSM connectivity while negotiating an LACP PortChannel. This feature makes the overall
deployment of the Cisco Nexus 1000V solution more robust.
Special PortChannel
Most access-layer switches do not support clustering technology, yet most Cisco Nexus 1000V designs require
PortChannels to span multiple switches. The Cisco Nexus 1000V offers several ways to connect the Cisco Nexus
1000V Switch to upstream switches that cannot be clustered. To enable this spanning of switches, the Cisco
Nexus 1000V provides a PortChannel-like method that does not require configuration of a PortChannel upstream.
There are two main vPC-HM configurations:
vPC-HM MAC address pinning
●
vPC-HM subgroups
●
vPC-HM MAC Address Pinning
MAC address pinning defines all the uplinks coming from the server as standalone links and pins different MAC
addresses to those links in a round-robin fashion. This approach helps ensure that the MAC address of a virtual
machine is never seen on multiple interfaces on the upstream switches. Therefore, no upstream configuration is
required to connect the Cisco Nexus 1000V VEM to the upstream switches (Figure 36).
Furthermore, MAC address pinning does not rely on any protocol to distinguish the various upstream switches,
making the deployment independent of any hardware or design.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
LACP Offloaded to VEM in an FCoE Deployment
Page 43 of 48