Sign in or 

|
Jeff_Sullivan |
Latest page update: made by Jeff_Sullivan
, Aug 17 2009, 4:16 PM EDT
(about this update
About This Update
1 word added 1 word deleted view changes - complete history) |
|
Keyword tags:
5424
5448
iSCSI
POWERCONNECT
More Info: links to this page
|
| Started By | Thread Subject | Replies | Last Post | ||
|---|---|---|---|---|---|
| aseniuk | Setting up 2 VLANs | 0 | Jan 25 2010, 9:47 AM EST by aseniuk | ||
|
Thread started: Jan 25 2010, 9:47 AM EST
Watch
I really like to say that write up is quite good for us new to the iSCSI game.
I have 1x 5448 swtich that we would like to setup as the iSCSI (VLAN'd) and the rest of the switch to be used for network traffic for the servers we have. Is there any thing special I would need to change to get that going?
Do you find this valuable?
Keyword tags:
iSCSI VLAN
|
|||||
| steve_o2 | iSCSI configuration | 2 | Nov 10 2009, 4:13 AM EST by DylanGoh | ||
|
Thread started: Aug 27 2009, 10:14 PM EDT
Watch
Great write-up. My performance over two dedicated Intel NICs went from 22mb/sec to 73mb/sec after these changes.
I also will now setup a 4 port LAG between 2 5424 switches for redundant paths to my Equallogic PS5000. What performance is everyone else seeing over iSCSI? |
|||||
| holografique | need more details | 3 | Oct 29 2009, 8:30 PM EDT by nebdude | ||
|
Thread started: Sep 9 2009, 2:54 PM EDT
Watch
this is a good start. but we need more details around:
- best practice for configuration 2x 5424 to act as a primary and secondary switch and the use of LAG or LACP groups (either via copper or fiber ports) - how to configure VLAN routing for when it comes time to have your iSCSI array replicate it's data to another site (subnet). - how to configure STP to ensure management uplinks from each switch back to a single core switch My typical configuration invovles creating the dedicated iSCSI VLAN on the core switch, then setting up an access port uplink on the primary and secondary 5424 on that iSCSI VLAN. I then use the other 3 fiber ports as the LAG/LACP group for the ISL trunk (per Equallogic Guidelines). This essentially gives me a dedicated iSCSI VLAN on the core and the iSCSI switches, and it's routable through the core to be able to route out to external sites for array replication. I can also access the array and other iSCSI devices management from your user networks for day-to-day management, email alerting, etc. etc. the problem I have is that if the uplink on the primary switch goes doen (or it fails) I lose complete management access to the secondary switch, even though it has it's own dedicated fiber uplink to the core on the iSCSI VLAN. |
|||||