Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch

Скачать
Страница из 28
 
Design Guide 
Figure 4 illustrates another vPC topology consisting of Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 
Series Fabric Extenders (in straight-through mode—that is, each fabric extender is single-attached to a Cisco Nexus 
5000 Series Switch). 
Figure 4 shows devices that are connected to the vPC peer (5k01 and 5k02) with a PortChannel (a vPC): like server 
2 (configured for NIC teaming with the 802.3ad option). 
Server 1 and server 3 connect to orphan ports. 
Figure 4.   
vPC Components with the Fabric Extender 
  
To summarize, a vPC system consists of the following components: 
● 
Two peer devices: the vPC peers of which one is primary and one is secondary and are part of a vPC domain. 
● 
A Layer 3 Gigabit Ethernet link called peer-keepalive link to resolve dual-active scenarios 
● 
A redundant 10 Gigabit Ethernet PortChannel called a peer link to carry traffic from one system to the other 
when needed 
● 
vPC member ports forming the PortChannel 
Traffic Flows 
vPC configurations are optimized to ensure that traffic through a vPC-capable system is symmetric. In Figure 5, for 
example, the leftmost flow (in blue) reaching a Cisco Nexus switch (Agg1 in the figure) from the core is forwarded 
toward the access (Acc1 in the figure) without traversing the peer Cisco Nexus switch device (Agg2). Similarly, traffic 
from the server directed to the core reaches a Cisco Nexus 7000 Series Switch (Agg1) and the receiving Cisco 
Nexus 7000 Series Switch routes it directly to the core without unnecessarily passing it to the peer Cisco Nexus 7000 
Series Device. This happens regardless of which Cisco Nexus 7000 Series device is the primary Hot Standby Router 
Protocol (HSRP) device for a given VLAN. 
 
© 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. 
Page 6 of 28