Cisco Cisco UCS B200 M2 Blade Server Libro blanco
© 2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 21 of 95
Figure 9. Uplink Interfaces and PortChannel Status
On the Cisco Nexus 5548UP Switch, a separate vPC is created to access NetApp shared iSCSI storage. The vPC
is created with the vPC name and corresponding vPC ID and required VLAN IDs, as shown in Table 3.
is created with the vPC name and corresponding vPC ID and required VLAN IDs, as shown in Table 3.
Table 3.
NetApp Storage
vPC Name
iSCSI Ports
(Controllers A and B)
(Controllers A and B)
vPC ID
VLAN ID
vPC- iSCSI Storage 1
e1b and e1c (Controller A)
103
192
vPC- iSCSI Storage 2
e1b and e1c (Controller B)
104
192
On NetApp Storage Controller A, Ethernet 10-Gbps port e1b is connected to Cisco Nexus 5548UP Application 1
(port 19), and Ethernet port e1c is connected to Cisco Nexus 5548UP Application 2 (port 19), which are part of
vPC-iSCSI Storage 1 with vPC ID 103 that allows traffic from VLAN ID 192. On NetApp Storage Controller B,
Ethernet 10-Gbps port e1b is connected to Cisco Nexus 5548UP Application 1 (port 20), and Ethernet port e1c is
connected to Cisco Nexus 5548UP Application 2 (port 20), which are part of vPC-iSCSI Storage 2 with vPC ID 104
that allows traffic from VLAN ID 192.
(port 19), and Ethernet port e1c is connected to Cisco Nexus 5548UP Application 2 (port 19), which are part of
vPC-iSCSI Storage 1 with vPC ID 103 that allows traffic from VLAN ID 192. On NetApp Storage Controller B,
Ethernet 10-Gbps port e1b is connected to Cisco Nexus 5548UP Application 1 (port 20), and Ethernet port e1c is
connected to Cisco Nexus 5548UP Application 2 (port 20), which are part of vPC-iSCSI Storage 2 with vPC ID 104
that allows traffic from VLAN ID 192.
Cisco UCS Quality-of-Service System and Policy
Cisco UCS uses IEEE Data Center Bridging (DCB) to handle all traffic within Cisco UCS. This industry-standard
enhancement to Ethernet divides the bandwidth of the Ethernet pipe into eight virtual lanes. System classes
determine how the DCB bandwidth in these virtual lanes is allocated across the entire Cisco UCS platform.
enhancement to Ethernet divides the bandwidth of the Ethernet pipe into eight virtual lanes. System classes
determine how the DCB bandwidth in these virtual lanes is allocated across the entire Cisco UCS platform.
Each system class reserves a specific segment of the bandwidth for a specific type of traffic, providing an assured
level of traffic management even in an oversubscribed system. For example, you can configure the Fibre Channel
Priority system class to determine the percentage of DCB bandwidth allocated to FCoE traffic.
level of traffic management even in an oversubscribed system. For example, you can configure the Fibre Channel
Priority system class to determine the percentage of DCB bandwidth allocated to FCoE traffic.
Table 4 describes the system classes.