topic Re: P4000 Switch Setup Issue in StoreVirtual Storage

P4000 Switch Setup Issue

HMUSER — Mon, 14 Nov 2011 14:47:25 GMT

We have currently got 2x 2910al-24G switches which i have setup.

At current i can only get the SAN to work on 1 switch without having the failover switch working. The software cant find the SAN if i move a connection from each shelf to the other switch. Below is the config i have for 1 of my switches. The other switch config is identical but has a different IP address for the VLAN. What am i missing out? The SAN are set to use ALB and are bonded on IP 192.168.0.10 and 192.168.0.20

Running configuration:

J9145A Configuration Editor; Created on release #W.14.49

hostname "ProCurve 2910al SAN Switch 1"
module 1 type J9145A
no stack
interface 1
   name "HM-SAN1"
   flow-control
exit
interface 2
   name "HM-SAN2"
   flow-control
exit
interface 13
   name "Data Server"
   flow-control
exit
interface 14
   name "Data Server"
   flow-control
exit
interface 20
   name "Management Port"
exit

vlan 1
   name "DEFAULT_VLAN"
   untagged 5-12,15-24
   ip address 10.0.0.35 255.255.255.0
   no untagged 1-4,13-14
   exit
vlan 10
   name "SAN_VLAN"
   untagged 1-4,13-14
   ip address 192.168.0.30 255.255.255.0
   jumbo
   exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
snmp-server contact "IT" location "Server Rack 1 - Comms Room 2"
spanning-tree
no autorun
password manager
password operator

Re: P4000 Switch Setup Issue

Jay Cardin — Mon, 14 Nov 2011 16:47:41 GMT

How are the two switches connected together?

Re: P4000 Switch Setup Issue

HMUSER — Tue, 15 Nov 2011 13:34:27 GMT

See my SAN setup diagram

Re: P4000 Switch Setup Issue

Jay Cardin — Tue, 15 Nov 2011 14:22:58 GMT

I am pretty sure you need have the switches connected if you are going to use ALB. I think there is a heartbeat frame that ALB uses to determine a valid path.

Re: P4000 Switch Setup Issue

HMUSER — Tue, 15 Nov 2011 15:00:41 GMT

I will look to get a trunk the 2 switches together.

Is it best to run LACP Dynamic rather than a static trunk?

Re: P4000 Switch Setup Issue

Jay Cardin — Tue, 15 Nov 2011 15:44:42 GMT

You can use Dynamic LACP but only if you configure your volumes for Network RAID 10. You would need to connect both links from a single P4500 to the one switch while the other P4500 has both links connected to the other switch. You still need to have a trunk between the switches.

There is some discussion about Dynamic LACP and is it really worth it; so you might be better off using Adaptive Load Balancing for now.

Re: P4000 Switch Setup Issue

HMUSER — Tue, 15 Nov 2011 16:08:24 GMT

I am running ALB on the SAN boxes and MPIO/DSM on the server with a pair of NICs Teamed as below

LAN
Nic 1 and Nic 2

SAN Switch 1
Nic 3 and Nic 4

SAN Switch 2
Nic 5 and Nic 6

What i meant was for the trunk would it be better off as LACP or Static?

Just to confirm what you are saying is having both nics of one P4300 going to SAN switch 1 and the other P4300 going to SAN Switch 2

Sorry this all new to me

Re: P4000 Switch Setup Issue

Jay Cardin — Tue, 15 Nov 2011 16:57:03 GMT

For ALB, your design will be fine once you add a trunk (I would use no less than 3 links and go static) between the two switches.

Re: P4000 Switch Setup Issue

Dan Nichols — Tue, 15 Nov 2011 18:03:28 GMT

As Jay says create a static trunk. You should have one NIC from each P4300 into each switch (as per your diagram) to create the most resilient architecture (think switch failure when using some network RAID0).

Re: P4000 Switch Setup Issue

HMUSER — Wed, 23 Nov 2011 15:55:09 GMT

I am still having trouble getting this up and running. I must be missing something out.

I have got 2 Trunks between the switches now as static trunks.

From my server I can ping both switches and both SAN shelves but not the virtual IP address of the SAN cluster.

I also cannot logon to the SAN

Is there something that im missing. Each switch has RSTP enabled