Cisco Cisco UCS B200 M3 Blade Server Libro blanco
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 19 of 95
Figure 7. Cisco UCS Component in iSCSI Network Design
As shown in Figure 7, a pair of Cisco UCS 6248UP fabric interconnects carries both storage and network traffic
from the blades with the help Cisco Nexus 5548UP. Both the fabric interconnect and the Cisco Nexus 5548UP are
clustered with the peer link between them to provide high availability. Two virtual PortChannels (vPCs) are
configured to provide network and storage access paths for the blades to northbound switches. Each vPC has
VLANs created for application network data, iSCSI storage data, and management data paths. There is also a
dedicated VLAN for VMware vMotion data traffic for VMware ESX Server.
from the blades with the help Cisco Nexus 5548UP. Both the fabric interconnect and the Cisco Nexus 5548UP are
clustered with the peer link between them to provide high availability. Two virtual PortChannels (vPCs) are
configured to provide network and storage access paths for the blades to northbound switches. Each vPC has
VLANs created for application network data, iSCSI storage data, and management data paths. There is also a
dedicated VLAN for VMware vMotion data traffic for VMware ESX Server.
For more information about vPC configuration on the Cisco Nexus 5548UP Switch, see
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html
.
Microsoft SQL Data Network and Storage Network vPC Mapping
Table 1 shows the Cisco Nexus 5548UP vPC configurations with the vPC domains and corresponding vPC names
and IDs for Microsoft SQL Servers. To provide Layer 2 and 3 switching, a pair of Cisco Nexus 5548UP Switches
with upstream switching are deployed, providing high availability in the event of failure to Cisco UCS to handle
management, application, and iSCSI storage data traffic. In the Cisco Nexus 5548UP topology, a single vPC
feature is enabled to provide high availability, faster convergence in the event of a failure, and greater throughput.
and IDs for Microsoft SQL Servers. To provide Layer 2 and 3 switching, a pair of Cisco Nexus 5548UP Switches
with upstream switching are deployed, providing high availability in the event of failure to Cisco UCS to handle
management, application, and iSCSI storage data traffic. In the Cisco Nexus 5548UP topology, a single vPC
feature is enabled to provide high availability, faster convergence in the event of a failure, and greater throughput.
Table 1.
vPC Mapping
vPC Domain
vPC Name
vPC ID
100
vPC-MS SQL 1
101
100
vPC-MS SQL 2
102
100
vPC-iSCSI Storage 1
103
100
vPC-iSCSI Storage 2
104
In the vPC design table, a single vPC domain, Domain 100, is created across Cisco Nexus 5548UP member
switches to define vPCs to carry specific network traffic. This topology defines four vPCs with IDs 101 through 104.
switches to define vPCs to carry specific network traffic. This topology defines four vPCs with IDs 101 through 104.