iSCSI - Best practices....

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: iSCSI - Best practices....

Re:iSCSI - Best practices....

by Guest » Wed Aug 02, 2006 1:46 am


just what I was looking for... Thanks!

Re:iSCSI - Best practices....

by Guest » Wed Aug 02, 2006 12:11 am


We route our iSCSI for two reasons:1. SAN-SAN replication to remote site2. Management - no dedicated management interface in our arrays without sacrificing one of the iSCSI data transfer portWe do put an ACL on the iSCSI VLAN to restrict traffic to just the needed management ports, and the iSCSI port between the local & remote arrays. That also prevents initiators in servers or wherever from accidentally making a connection over a routed path vs. a dedicated NIC directly on the iSCSI VLAN.I'd say if you have no replication need, and if your system has dedicated management interfaces, then don't route iSCSI.

Re:iSCSI - Best practices....

by Guest » Tue Aug 01, 2006 11:57 pm


we do have jumbo frames enabled.We are just trying to figure out the advantages and disadvantages of routing iscsi.  Any security concerns?

Re:iSCSI - Best practices....

by Guest » Tue Aug 01, 2006 10:19 pm


An isolated VLAN for iSCSI is not a bad idea, but not a requirement.  If the situation permits it, I would use an isolated VLAN for the iSCSI hosts and if needed a separate one for the iSCSI targets. The iSCSI traffic is 100% routable. Best practice would be also to use jumbo frames if the network devices support it.   Hope this helps, Mike

iSCSI - Best practices....

by Guest » Tue Aug 01, 2006 9:30 pm


routable or non-routable iSCSI VLAN??

Top