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

Скачать
Страница из 38
 
 
Design Guide 
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 
Page 21 of 38 
 
Figure 14.    Worst Case of Dual-Active Failure 
 
vPC and Object Tracking 
The object tracking feature available in NXOS can be used to associate the vPC status of a vPC device with the 
status of the interfaces that are tracked. The following explample clarifies. At the time of this writing Object Tracking is 
only available on the Cisco Nexus 7000 Series. 
You can use a single 10 Gigabit Ethernet card on the Cisco Nexus 7000 Series for both core connectivity and the 
peer link, but this is not the best option. If you lose the 10 Gigabit Ethernet card on the vPC primary device, you lose 
not only core connectivity, but also the peer link. As a result, ports will be shut down on the peer vPC device, isolating 
the servers completely. 
You can address this specific configuration requirement with a tracking configuration. The objects being tracked are 
the uplinks to the core and the peer link. If these links are lost, vPCs local to the switch are shut down so that traffic 
can continue on the vPC peer. 
To configure this feature, use the following command syntax: 
! Track the vpc peer link 
track 1 interface port-channel110 line-protocol 
 
! Track the uplinks to the core 
track 2 interface Ethernet7/9 line-protocol 
track 3 interface Ethernet7/10 line-protocol 
 
! Combine all tracked objects into one. 
! “OR” means if ALL object are down, this object will go down 
! --> we have lost all connectivity to the core and the peer link