bityard Blog

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

2017:10:23:experiences_with_dell_powerconnect_switches [2017/10/23 10:12] – created Frank Fegert2017:10:23:experiences_with_dell_powerconnect_switches [2017/10/23 10:16] (current) – Frank Fegert
Line 21: Line 21:
 There were multiple locations with roughly the same setup composed of the hardware components described above. Each location had two daisy-chained Dell PowerEdge M1000e blade chassis systems. The layer 2 LAN and SAN networks stretched over the two blade chassis. The setup at each location is shown in the following schematic: There were multiple locations with roughly the same setup composed of the hardware components described above. Each location had two daisy-chained Dell PowerEdge M1000e blade chassis systems. The layer 2 LAN and SAN networks stretched over the two blade chassis. The setup at each location is shown in the following schematic:
  
-{{:2017:10:23:dell_powerconnect_schematic.png|Schematic of the Dell PowerConnect LAN and SAN setup}}\\+{{:2017:10:23:dell_powerconnect_schematic.png?600x|Schematic of the Dell PowerConnect LAN and SAN setup}}\\
  
 All in all not an ideal setup. Instead, i would have preferred a pair of capable -- both functionality and performance-wise -- central top-of-rack switches to which the individual M1000e blade chassis would have been connected. Preferrably a seperate pair for LAN an SAN connectivity. But again, the mentioned components were already preselected and pre-purchased. All in all not an ideal setup. Instead, i would have preferred a pair of capable -- both functionality and performance-wise -- central top-of-rack switches to which the individual M1000e blade chassis would have been connected. Preferrably a seperate pair for LAN an SAN connectivity. But again, the mentioned components were already preselected and pre-purchased.
Line 72: Line 72:
   * Not per se an issue, but the baseline CPU utilization on Dell PowerConnect M8024-k switches running layer 3 instances is significantly higher compared to those running only as layer 2 devices. The following CPU utilization graphs show a direct comparison of a layer 3 (upper graph) and a layer 2 (lower graph) device:   * Not per se an issue, but the baseline CPU utilization on Dell PowerConnect M8024-k switches running layer 3 instances is significantly higher compared to those running only as layer 2 devices. The following CPU utilization graphs show a direct comparison of a layer 3 (upper graph) and a layer 2 (lower graph) device:
  
-{{:2017:10:23:dell_powerconnect_m8024-k_L3.png|CPU utilization on a Dell PowerConnect M8024-k switch as a Layer 3 device}}\\ +{{:2017:10:23:dell_powerconnect_m8024-k_L3.png?600x|CPU utilization on a Dell PowerConnect M8024-k switch as a Layer 3 device}}\\ 
-{{:2017:10:23:dell_powerconnect_m8024-k_L2.png|CPU utilization on a Dell PowerConnect M8024-k switch as a Layer 2 device}}\\+{{:2017:10:23:dell_powerconnect_m8024-k_L2.png?600x|CPU utilization on a Dell PowerConnect M8024-k switch as a Layer 2 device}}\\
  
 The CPU utilization is between 10 and 15% higher once the tasks of processing layer 3 traffic are involved. What kind of switch function or what type of traffic is causing this additional CPU utilization is completely intransparent. Documentation on such in-depth subjects or details on how the processing within the Dell PowerConnect switches works is very scarce. It would be very interesting to know what kind of traffic is sent to the switches CPU for processing instead of being handled by the hardware. < The CPU utilization is between 10 and 15% higher once the tasks of processing layer 3 traffic are involved. What kind of switch function or what type of traffic is causing this additional CPU utilization is completely intransparent. Documentation on such in-depth subjects or details on how the processing within the Dell PowerConnect switches works is very scarce. It would be very interesting to know what kind of traffic is sent to the switches CPU for processing instead of being handled by the hardware. <