When working with iSCSI on W2K3 server or any Microsoft OS, the key is the networking component. If it is at all possible, I enable Jumbo Frames and create a separate VLAN for the storage traffic, very similar to a FC SAN. You also want to make sure that you Bind the Volumes and make the target Persistent. I also use a VIF (multi or single) as well as etherchannels and NIC Teaming to try to aggregate bandwidth.
If you are able to use SnapDrive, it'll make connecting and managing the LUNs much easier, especially if you will need to increase their size.
I've only used HP Proliant servers. I've used the MS iSCSI Initiator (all versions) and the QLOGIC 4010.
If you are going to cluster and iSCSI environment, I recommend reading MS Article 883397. I would follow the steps even if it not a pure iSCSI environment.
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Rob Winters Sent: Wednesday, March 30, 2005 5:39 PM To: toasters@mathworks.com Subject: experience with iSCSI from W2K3 servers?
Does anyone have feedback or gotchas about W2K3 accessing large iSCSI space on NetApp filers? With what hardware? HBA and/or software initiator?
How about clustering W2K3 servers to a NetApp iSCSI target, or similar HA configurations?
Thanks!
/// Rob
P.S. Yes, *this* is how well the MacOS X research is going... :-|
-- Rob Winters SAIC, NASA Headquarters ISEM Contract rwinters@hq.nasa.gov ***************************************************************************************************** If you have received this email in error please notify the the system manager or the sender immediately and do not disclosed the to anyone or make copies.
** eSafe scanned this email for viruses, vandals or malicious content ** ** To find out eSafe(TM) and other Aladdin Security Products, contact AMC Corporation at (212) 736-0111 *****************************************************************************************************