Dell PS6000 Configuration Guide - Page 45

M1000e Blade Chassis Integration, 5.1 Guidelines for Stacking Switches in a Blade Chassis

Page 45 highlights

5 M1000e Blade Chassis Integration M1000e (or any 3rd party blade chassis implementation) requires additional SAN design considerations. In general, most blade integration solutions will require an external set of switches that will host the PS Series arrays that are then uplinked to the M1000e blade enclosure I/O modules. It is recommended that stackable blade I/O modules and external switches be utilized for all blade solutions when possible. Note: See the following Dell EqualLogic whitepaper for more information on integrating blade solutions into the EqualLogic SAN infrastructures:  Integrating Blade Solutions with the Dell EqualLogic PS Series, available at: http://www.equallogic.com/resourcecenter/assetview.aspx?id=7173 5.1 Guidelines for Stacking Switches in a Blade Chassis Use the following guidelines for blade server integration with EqualLogic SANs. Note: All configurations documented in this section assume that Fabric A is dedicated to client LAN traffic and Fabric B and/or C will be used for SAN infrastructure connectivity  Blade I/O modules and external switches should be from the same vendor if possible.  As a best practice, you should consider using Blade I/O modules as host aggregation switches only. The limited number of external ports on the blade I/O modules drastically reduces the scalability of a SAN if arrays are directly connected them.  Stack blade I/O modules into one of two stacking architectures as described in Section 5.2 and Section 5.3 when possible. Other configurations are possible and may be used if desired.  Stack any external switches into a single stack as described in Section 4.3.  Interconnect blade I/O stack(s) with external switch stacks via aggregated links as described in Section 4.3.1.  Use the switch vendor preferred method for link aggregation (if all switches from same vendor).  Use LACP for link aggregation when I/O modules and external switches are from different vendors  Using 10GbE port options where available (See Figure 18): If blade I/O modules are stacked: o Aggregate at least two 10GbE ports from each blade I/O module stack for redundancy o Distribute 10GbE links among multiple switches within each I/O module stack o Distribute 10GbE links evenly between all switches within the external switch stack If blade I/O modules are NOT stacked: o Aggregate at least two 10GbE ports from each switch to one external switch if external switches are not stacked. o Aggregate at least two 10GbE ports from each switch to two different external switches if external switches are stacked.  Using 1GbE port options only if 10GbE is not available for up-linking: If blade I/O modules are stacked: Dell EqualLogic Configuration Guide v11.3 40

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73

Dell EqualLogic Configuration Guide v11.3
40
5
M1000e Blade Chassis Integration
M1000e (or any 3
rd
party blade chassis implementation) requires additional SAN design considerations.
In general, most blade integration solutions will require an external set of switches that will host the
PS Series arrays that are then uplinked to the M1000e blade enclosure I/O modules.
It is recommended
that stackable blade I/O modules and external switches be utilized for all blade solutions when
possible.
5.1
Guidelines for Stacking Switches in a Blade Chassis
Use the following guidelines for blade server integration with EqualLogic SANs.
Blade I/O modules and external switches should be from the same vendor if possible.
As a best practice, you should consider using Blade I/O modules as host aggregation switches
only. The limited number of external ports on the blade I/O modules drastically reduces the
scalability of a SAN if arrays are directly connected them.
Stack blade I/O modules into one of two stacking architectures as described in Section 5.2 and
Section 5.3 when possible.
Other configurations are possible and may be used if desired.
Stack any external switches into a single stack as described in Section 4.3.
Interconnect blade I/O stack(s) with external switch stacks via aggregated links as described in
Section 4.3.1.
Use the switch vendor preferred method for link aggregation (if all switches from same
vendor).
Use LACP for link aggregation when I/O modules and external switches are from different
vendors
Using 10GbE port options where available (See Figure 18):
If blade I/O modules are stacked:
o
Aggregate at least two 10GbE ports from each blade I/O module stack for redundancy
o
Distribute 10GbE links among multiple switches within each I/O module stack
o
Distribute 10GbE links evenly between all switches within the external switch stack
If blade I/O modules are NOT stacked:
o
Aggregate at least two 10GbE ports from each switch to one external switch if external
switches are not stacked.
o
Aggregate at least two 10GbE ports from each switch to two different external switches if
external switches are stacked.
Using 1GbE port options only if 10GbE is not available for up-linking:
If blade I/O modules are stacked:
Note:
All configurations documented in this section assume that Fabric A is dedicated to client LAN
traffic and Fabric B and/or C will be used for SAN infrastructure connectivity
Note:
See the following Dell EqualLogic whitepaper for more information on integrating blade
solutions into the EqualLogic SAN infrastructures:
Integrating Blade Solutions with the Dell EqualLogic PS Series
,
available at: