• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 813
  • Last Modified:

Separate network for iSCSI

Hi Experts,

Have a question regarding setting up a iSCSI connection to a SAN from a Windows 2003/2008 server using MS iSCSI. We currently have it setup so that from the server one NIC connects to the main VLAN - 192.168.2.X and the other NIC connects to a SAN VLAN - 192.168.12.X

The SAN is connected to the same switch to which these NICs terminate. Is this the right way to set up the iSCSI connection or is there a better way? We don't notice too many issues on the network but if there were a better way to do it then we can try. We do have spare Cisco Catalyst 3560 lying around but we can't purchase a dedicated iSCSI HBA. Do we need to connect the SAN on a completely different switch with only NICs from the servers attached to it? If so how would routing work? We are not looking into redundancy currently but to see if speeds can be increased on the SAN. TIA
0
abhijitm00
Asked:
abhijitm00
  • 2
  • 2
3 Solutions
 
jimmyray7Commented:
The SAN should be on it's own segment.  Ideally a separate switch, at minimum, a separate VLAN.  With a dedicated switch you can do some iSCSI optimizations like jumbo frames, etc.  Speed increase would depend on the current switch's load, but it should be better.  A separate switch also makes troubleshooting easier, as you immediately know which network the problem stems from.
0
 
abhijitm00Author Commented:
Thanks for getting back Jimmy but how would you physically connect the cables. I would assume you would have a cable from the SAN (192.168.12.5) going to the Cisco switch. Another cable from the server's second NIC (192.168.12.6) going into it as well. How would they talk though. What would you put under the gateway for the server NIC? Also what configuration would need to go onto the switch? Please correct me if my assumptions are wrong. We are using Cisco Catalyst 3560G switches
0
 
jimmyray7Commented:
NIC1 - data network- would plug into the existing switch.
NIC2 - SAN - would plug into the second switch (SAN only).

The two switches should be completely separate.  The SAN switch should be isolated without any connections anywhere else.

The data network config wouldn't change.  The SAN NIC shouldn't need a gateway, as there is no outside access.  Just an IP and subnet mask.

Let me see what I can dig up regarding the cisco iscsi config.
0
 
abhijitm00Author Commented:
Thanks Jimmy. So I would disconnect my SAN NIC from my server and plug into the new switch put in the IP and subnet and then another NIC from the SAN with IP and subnet connecting to this new switch. How would the new switch need to be configured in terms of IP and VLAN? Would I set it up with an IP address and subnet as well, would I need to add VLAN info or anything else you can think of? Again the servers would be using the MS iSCSI software initiator

I appreciate you looking up the cisco iscsi config.
0
 
johnemyersCommented:
On the Iscsi Switch
1. enable PORT FAST on the switch ports. (Brings ports online quick and turns off STP)
2. Lable the ports with descriptions ( Server a, b , SAN A ,B )
3.  Optional   Setup a Management IP for inband management  ( If you have Vlans on network the management Vlan is allowed to all devices)
If no Management VLAN the console or direct cable to switch is the only way to manage the switch.


0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now