Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
Design Guide
Figure 11.
4+ Ports vPCs and 2 Ports vPCs
In the case of Unified Fabric (Fibre Channel over Ethernet [FCoE]) deployments, it is important to distinguish 4+ ports
Host vPCs from 2-Ports Host vPCs as depicted in Figure 12. In order for FCoE to work, the server adapter needs to
see two separate Fibre Channel fabrics. This is only possible when the Converged Network Adapter card has only 1
link per Cisco Nexus 5000 as in the case of server 2 in Figure 12.
Host vPCs from 2-Ports Host vPCs as depicted in Figure 12. In order for FCoE to work, the server adapter needs to
see two separate Fibre Channel fabrics. This is only possible when the Converged Network Adapter card has only 1
link per Cisco Nexus 5000 as in the case of server 2 in Figure 12.
Figure 12.
4+ Ports vPCs and 2 Ports vPCs and FCoE
In-Service Software Upgrade and vPC
In presence of vPC, it is possible to upgrade a device such as the Cisco Nexus 7000 Series using an In-Service
Software Upgrade (ISSU) with no disruption to the traffic. However, if someone modifies the vPC configuration during
the upgrade, it will cause an inconsistency between the vPC peer devices (the one being upgraded and the other
device).
Software Upgrade (ISSU) with no disruption to the traffic. However, if someone modifies the vPC configuration during
the upgrade, it will cause an inconsistency between the vPC peer devices (the one being upgraded and the other
device).
To avoid this undesirable situation, vPC is capable of locking the configuration on the device that is not undergoing
the upgrade and releasing it when the upgrade is complete.
the upgrade and releasing it when the upgrade is complete.
vPC Failure Scenarios
This section describes the expected behavior of a vPC design for various link failures.
© 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 15 of 28