background image

 
 
 

5  

Optimizing Performance When Designing Highly Scalable SAN Solutions:  

Guidelines for SAN Architects

 

 

 
 
 
 
 
SPG-WP06004 SN0130924-00 

Rev 

 

 

Examples of Rule B: Remote/ISL Traffic  

Per Rule B, the total amount of remote traffic must be less than or equal to the capacity of 
the ISLs/trunks to avoid oversubscription. Therefore, network traffic must be balanced 
across the SAN to ensure maximum performance using the ISLs. 

Maximum ISL Traffic Load for 4Gb Stackable Switch 

In the example shown below, using a SANbox 5602 stackable 4Gb switch, the 10Gb trunks 
(actual bandwidth capability is 12Gb/sec) can support about 

75%

 of the theoretical traffic 

load to/from the attached server and storage devices. Due to the high capacity of these 
ISLs/trunks, 

stackable solutions allow for scaling up to large port counts while 

maintaining high performance

 

 

ISLs support 75% of total 

theoretical data traffic 

(from attached server and 

storage devices) 

• 

Max theoretical bandwidth from devices is: 
16 ports x 4Gb/sec speed x 2 (full duplex) = 128 Gb/sec 

• 

Max theoretical bandwidth of ISLs/trunks is: 
4 ports x 12Gb/sec x 2 (full duplex) = 96 Gb/sec 

• 

ISL capacity (96 Gb/sec) is 75% of theoretical device bandwidth (128 Gb/sec).  

Traffic Calculation 

Traffic To “Remote” 

Devices over ISLs 

Server and Storage 

Devices 

Traffic To “Local” 

Devices 

Summary of Contents for SANbox 5200 Series

Page 1: ...ghly scalable SAN solutions allow your network traffic engineer to maximize overall performance and to minimize cost Key Findings By following simple network engineering guidelines SAN switch solution...

Page 2: ...further ISL connections between the switches to support more data bandwidth but this reduces the number of ports available to attach servers and storage This is the classic scalability versus perform...

Page 3: ...ust be considered Local and remote traffic are defined as follows Local traffic I O operations between servers and storage located on the same switch Remote traffic I O operations between servers and...

Page 4: ...for localized traffic and Rule B for remote ISL traffic for stackable switch and traditional fixed port solutions Example of Rule A Localized Traffic for Critical High Bandwidth I O Operations Followi...

Page 5: ...actual bandwidth capability is 12Gb sec can support about 75 of the theoretical traffic load to from the attached server and storage devices Due to the high capacity of these ISLs trunks stackable so...

Page 6: ...s can support only about 14 of the theoretical traffic load of each switch Max theoretical data traffic from devices is 14 ports x 4Gb sec x 2 full duplex 112 Gb sec Max theoretical capacity of ISLs t...

Page 7: ...ance as they scale due to the minimal number of ISL trunks available As discussed earlier the obvious solution of adding more ISL links reduces the number of ports available for server and storage dev...

Page 8: ...n choosing a topology design In general ideal best practices when connecting switches via inter switch links or trunks include the following A minimum of one link between every pair of switches to max...

Page 9: ...Guidelines for SAN Architects SPG WP06004 SN0130924 00 Rev A Baseline Configurations The following table shows the topology summary of three baseline configurations Total Switches Total 2Gb 4Gb Device...

Page 10: ...G WP06004 SN0130924 00 Rev A Maximum Performance Configurations By adding additional ISL trunks higher remote traffic bandwidth can be supported between switches as indicated in the following table To...

Page 11: ...s also preserve 2Gb 4Gb ports for connections to server and storage devices Switch Architecture Choice Architecture choice is a key factor in the network engineering equation Per the guidelines in the...

Reviews: