Unified Computing System (UCS) Quality of Service (QoS) and Security. Session ID BRKCOM 2004

Size: px

Start display at page:

Download "Unified Computing System (UCS) Quality of Service (QoS) and Security. Session ID BRKCOM 2004"

Tyrone Chandler
5 years ago
Views:

1 Unified omputing System (US) Quality of Service (QoS) and Security Session ID BRKOM 2004

2 US QoS Agenda System omponents QoS hilosophy User onfigurable arameters QoS Tools ongestion Management acket Flow Details resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 2

System omponents SAN LAN MMT SAN A S S A Interconnect (40 or 20 10E ports) + (2 or 1 Expansion Slots) ompute hassis Extender R I I R Extender Blade hassis Upto 8 half width blades or 4 full width

3 System omponents SAN LAN MMT SAN A S S A Interconnect (40 or 20 10E ports) + (2 or 1 Expansion Slots) ompute hassis Extender R I I R Extender Blade hassis Upto 8 half width blades or 4 full width blades M B B Extender Host to uplink traffic engineering Up to 8:1 Flexible oversubscription possible X X 6 omputer X X X 6 omputer X Virtualized adapter for single OS and hypervisor systems ompute Blade (Half slot) ompute Blade (Full slot) ompute Blade resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 3

4 System omponents - Details ASI SAN LAN MMT SAN ompute hassis ompute hassis ompute hassis L I Extender F X X 6 omputer S S V I X X X L F 6 omputer X Extender V ort ASI 10E/F/1E Media Access ontrollers Forwarding - Ethernet, Fibre hannel, Multipath olicy Engine acket Buffering FEXLink ASI Host to uplink traffic engineering onnectivity detection & management portal Virtual Interface ard ASI Virtualized adapter for both single OS and hypervisor systems Ethernet and F vnis ompute Blade (Half slot) ompute Blade (Full slot) NA FOE couples Industry standard NIs and HBAs resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 4

QoS Architecture SAN LAN MMT SAN A S S A No packet drops within the array Largest buffers are on switch and host memory, so congestion pushed to edges ompute hassis Extender R I I R Extender riority

5 QoS Architecture SAN LAN MMT SAN A S S A No packet drops within the array Largest buffers are on switch and host memory, so congestion pushed to edges ompute hassis Extender R I I R Extender riority Flow ontrol (F) used to ensure packet drops are at vni or All traffic in a A system belongs to 1 of 6 System lasses M X X B B X X X X Four are user configurable while the other two are for FoE and standard Ethernet 6 omputer ompute Blade (Half slot) 6 omputer ompute Blade (Full slot) QoS parameters can be configured at a per system class level, or a per vni level. resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 5

6 User onfiguration Users configure QoS parameters at two levels lobally for each System lass OS value for packets in this class Example lass Name F Bronze OSValue 3 0 Drop/No-drop behavior Drop/No-Drop No-Drop Drop Strict riority No No Bandwidth/Weight 20% 30% Strict riority Bandwidth/Weight resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 6

5000 Burst 300 400 100 System lass for traffic from this vni Rate limit (Mbps) Burst

7 User onfiguration Users configure QoS parameters at two levels For each vni (Egress properties) Example: Logical Server A vni1 vni2 vni3 lass F F Bronze Rate Burst System lass for traffic from this vni Rate limit (Mbps) Burst Size (Kbytes) resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 7

User onfiguration Example lobal System lass Definitions lass Name F old Ethernet BE OS Value 3 1 0 Drop/No-Drop No-Drop Drop Drop Strict riority No No No Bandwidth/Weight 1 (20%) 3 (60%) 1 (20%) F

8 User onfiguration Example lobal System lass Definitions lass Name F old Ethernet BE OS Value Drop/No-Drop No-Drop Drop Drop Strict riority No No No Bandwidth/Weight 1 (20%) 3 (60%) 1 (20%) F Traffic High riority Ethernet Best Effort Ethernet Logical Server A vni1 vni2 vni3 Logical Server B vni1 vni2 lass F F Eth. BE Rate Burst lass old Eth. BE Rate Burst resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 8

QoS Tools riority Flow ontrol Transmit Queues Receive Buffers Ethernet Link OS based Bandwidth Management Offered Traffic 10 E Link Realized Traffic Utilization One Two One Two 3/s 3/s 2/s 3/s H

t3 Enables lossless s for each class of service AUSE sent per virtual lane when buffers limit exceeded Enables Intelligent sharing of bandwidth between traffic classes control of bandwidth 802.

9 QoS Tools riority Flow ontrol Transmit Queues Receive Buffers Ethernet Link OS based Bandwidth Management Offered Traffic 10 E Link Realized Traffic Utilization One Two One Two 3/s 3/s 2/s 3/s H Traffic 3/s 2/s Three Four Five Six Seven STO AUSE Three Four Five Six Seven Eight Virtual Lanes 3/s 3/s 3/s 3/s 4/s 6/s 3/s 3/s Storage Traffic 3/s LAN Traffic 4/s 3/s 5/s Eight Eight t1 t2 t3 t1 t2 t3 Enables lossless s for each class of service AUSE sent per virtual lane when buffers limit exceeded Enables Intelligent sharing of bandwidth between traffic classes control of bandwidth 802.1Qaz Enhanced Transmission Among the tools used are aggregate shapers at the vnis (VI ), ETS, olicers at the switch for each vni. resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 9

10 Traffic Engineering vnis can be pinned to specific switches when created (with configurable failover to other switch) Depending on requirements, vnis could be pinned to one switch or distributed evenly vni-1 vni-2 FEX-1 2 Extenders in chassis, each with 1 link to the switch. vni-3 FI-1 Blade-1, VI-1 VI with 3 vnis vnis in System lass pinned to one interconnect vni-1 Blade-2, VI-1 vni-2 2 FI, both with 1 connection to each FEX vni-3 FEX-2 lass-a lass-b lass- FI-2 resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 10

Traffic Engineering vnis can be pinned to specific switches when created (with configurable failover to other switch) Depending on requirements, vnis could be pinned to one interconnect or

11 Traffic Engineering vnis can be pinned to specific switches when created (with configurable failover to other switch) Depending on requirements, vnis could be pinned to one interconnect or distributed evenly vni-1 FEX-1 vni-2 vni-3 FI-1 Blade-1, VI-1 vnis in System lass distributed across interconnects vni-1 Blade-2, VI-1 vni-2 vni-3 FEX-2 lass-a lass-b lass- FI-2 resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 11

12 vni-1 ongestion Spread vni1in class generating large amount of traffic vnis 1 and 2 in lass- backup in host memory FEX-1 2 Extenders in chassis, each with 1 link to the FI. 2 FI, both with 1 connection to each FEX lass- congestion, going into switch on this port FI-1 vni-2 vni-3 ause packet sent out for lass- VIwith 3 vnis Blade-1, VI-1 vni-1 vni-2 Blade-2, VI-1 FI-2 vni-3 FEX-2 lass-a lass-b lass- resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 12

13 QoS Tools riority Flow ontrol (aka er riority ause) Ability to assert pause per IEEE 802.1p lane All internal US links support F Shaping and WRR s can shape traffic generated by hosts. Available in VI WRR in, FEX and s resentation_id 2010 isco and/or its affiliates. All rights reserved. isco ublic 13

Traffic Monitoring and Engineering for UCS

Traffic Monitoring and Engineering for UCS Steve McQuerry, CCIE# 6108 Technical Marketing Engineer Agenda UCS Networking Overview Network Statistics in UCSM Understanding Collection Policies Hotspot Detection