HP ProCurve 2910al, VLANs 1

[pinkpanther56]

Me again.

I have two servers and a SAN plugged into the same switch, i've been told to seperate the iSCSI traffic into a seperate VLAN. I've setup a VLAN and moved the appropriate ports into it and selected tagged. Should that seperate the traffic even though it all operates in the same IP range, my PC is not in the VLAN I created yet I can still ping the SANs network card.

 

[cajuntank]

Create a VLAN just for SAN on your switch, put the SAN and the NIC or NIC(s) if your doing what's called "multipath", enable jumbo frames on the VLAN, SAN, and NIC(s).

You mention the word "tagged"... I use HP Procurve equipment and the word "tagged" denotes a port passing multiple VLAN(s) through it (Cisco uses the work "trunk"). HP's "untagged" is where that port or ports are only in that particular VLAN so for example:

VLAN 1
ip address 192.168.1.1 255.255.255.0
untagged 1-15
no untagged 16-24
exit
VLAN 2
name SAN
ip address 192.168.2.1 255.255.255.0
untagged 16-24
jumbo
exit

Ports 1-15 are on the 192.168.1.0/24 subnet and ports 16-24 are on the 192.168.2.0/24 subnet. You enable jumbo frames on that particular VLAN only (assuming your switch, SAN, and NIC(s) support jumbo frames).

So based on your question, you do not have something setup correctly since the two separate VLAN(s) will be on different subnets. If this is a layer 3 switch, then adding the command "ip routing" will turn on routing between the VLAN(s).

Hope that helps.

 

[pinkpanther56]

I'm using HP 2910al switches is IP routing not on by default on these?

I created a vlan and setup the SAN and NIC's on 192.168.0.* range. Am I correct that if I have my laptop in that range but not in the VLAN then I shouldn't be able to ping them? I started off being able to ping the SAN but expected that when I moved those ports into the vlan that I then shouldn't be able to ping the SAN from my laptop if i've set it up correctly.

Thanks.

 

[cajuntank]

IP routing is not turned on by default until you issue the
"ip routing" in the config.

Without seeing your config, I'm making assumptions, but you are correct. If you have one vlan defined in the 192.168.0.0 range and have another defined in another range, then the two do not talk to each other unless they have a route to each other (thus the "ip routing" statement so directly connected vlan interfaces automatically route to each other).

If you are having issues still, post your config and we'll see what's up.

 

[pinkpanther56]

I'll have another look when I get chance thanks.

 

[pinkpanther56]

Yep ok I hadn't got the ports set to untagged it seems to be working fine now.

How do I make sure that jumbo frames are enabled on those ports? The I think i'm all set.

 

[cajuntank]

Look at my config example I posted earlier. It will show the "jumbo" command under that particular vlan interface.
You can also do a "show vlan". This will show you in the last column listing of Jumbo either yes or no.

 

[pinkpanther56]

Excellent I think i'm all set, I really must get around to digesting the beast of a manual

Thanks for your help.