When I set up my iSCSI LAN, I put a whole separate LAN in place. I then put a second NIC (or used the already existing NIC) in the servers that communicated with the iSCSI machines. My thought was to avoid the load of the iSCSI traffic off of my backbone.
In a small home setup like what you have, a separate VLAN is probably just fine. However, if you *do* use a VLAN, you'll want a second NIC in which ever machine(s) use the iSCSI network, and put them in a different address space. You don't need a router for this, which is good. For instance, assume that you have your production LAN (the one with the workstations talking to servers) on 192.168.10.0/24. I'd then make a separate VLAN, put your iSCSI box and the second NIC for your file server on that VLAN, and use, for instance, 192.168.11.0/24 for that VLAN. However, you might not even need to do that, if you want. Just put everything on the same LAN (or VLAN), if you're not worried about traffic. Kurt On Tue, Oct 27, 2009 at 17:49, Webster <[email protected]> wrote: > Goal is to setup a VLAN for the iSCSI traffic from my Windows Storage Server > 2008 box I built. > > I can barely spell VLAN so I have my work cut out for me. :) I know I will > make a lot of ID10T errors but this is my personal lab so I am not going to > hurt anything. If I screw something up, I can just reset the switch back to > factory defaults and start all over. > > > Webster > >> -----Original Message----- >> From: Ben Scott [mailto:[email protected]] >> Subject: Re: HP ProCurve 2810 CLI ref guide >> >> On Tue, Oct 27, 2009 at 8:38 PM, Webster <[email protected]> wrote: >> > I must be doing something wrong on my switch as I was told to >> > enter "ip routing" but I get "Invalid command: routing". >> >> The 2810 doesn't do routing. It's a layer two switch. It's not a >> router (or a "layer three switch", as routers are sometimes called). >> >> > I am at the (config)# prompt but can't figure >> > out what I am doing wrong. >> >> What are you trying to accomplish? What's the end goal? > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
