iSCSI VLAN & LAG between two PC6224

In order for the management VLAN to traverse over your port channel you will need to set the switchport mode to general instead of trunk.  On the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID.  If you use Trunk mode, you will not have the default VLAN on those ports.  The ports will only allow tagged traffic.

console(config)# interface port=channel 1

console(config-if)# switchport mode general

console(config-if)# switchport general allowed vlan add 2 tagged

console(config-if)# switchport general pvid 1

As far as any up to date information on the MPIO functionality with your storage you may direct that to the storage group or we could move the Post to the storage forum.  Let us know if this something that you desire.

One more thing I forgot, the connections between PS4000 and servers are working, if I disable the NIC that has currently active connections to PS4000 then the other adapter takes over and it's seen on the PS4000 management that now connections come from different IP.

I did all this, but it seems that this did not solve my problem, MPIO is still not working.

I know that the servers are not the problem, because they worked with MPIO with older PC6224's, where I did not use VLAN to separate iSCSI traffic. The old PC6224's had also a LAG set up and all ports where then available for iSCSI. Now that we neede new switches to expand our network I decided to swap 6224's from the SAN to put newer ones there and by the stuff I have learned since my first SAN setup I decided to speratae the iSCSI traffic.

Also one curious thing about the commands You posted, if I look at the running config then there is no console(config-if)# switchport general pvid 1 in there, but when I check thru the web console it show's that ch1 has PVID 1

Some notes about your config:

- if a port is made part of a port-channel, no other settings should be applied to that port (e.g. MTU)

- you set up a LAG without LACP (static), but then use LACP settings on the ports

- you have management set to vlan 1, but the trunk (on the LAG) only allows VLAN 2.

I'd suggest to

- change from "channel-group 1 mode on" to "channel-group 1 mode auto"

- remove the MTU settings from the individual LAG ports

- add the MTU to the port-channel (this is most likely why MPIO isn't working if your servers are set to use jumbo frames.

- add vlan 1 to the trunk on the LAG (switchport trunk allowed vlan add 1,2)

Look at your mac address table on both switches, you should see ALL the array interfaces (eth0, 1,2, etc. and your host iSCS interfaces i.e., whatever you have wired to both switches) listed. 

Telnet into a switch, and try pinging/traceroute from one switch to a iSCSI interface connected to the other switch.

Telnet/SSH into each of your array member(s), use one of the eth IP address, not the group IP

ping "-I "

(that is a –I as in Capital letter “eye”, ensure you use the quotes after the command and at the end of the destIP).  Use CTRL-C to quit.  

The “source_ETH_IP” is one of the eth interfaces of the member you connected to (eth0, eth1, etc.)

The “dest_IP” is each of the eth interfaces of the other member(s)

Test all combinations, to other members, to host iSCSI interfaces.

To Traceroute:

Telnet/SSH in to the member use one of the ETH interface ip’s not the group IP), then traceroute out of each specific ETH port,

GrpName>support

GrpName(support)>traceroute “-s [ETH port source IP] [destinationIP]”

Also note the quotes after the command and at the end of the destinationIP.

“ETH port Soruce IP” is the member you connected to

The “destinationIP” is the other member test each eth combination (all members eth interfaces, and host iSCSI interfaces).  

If you don’t see all the mac address, or any of pings fail, you may need to enable spanning tree on the lag ports so that they can learn the mac address from the other switch.  This would be enabled on both sides of the lags, for each interface you configured (19-24)

-joe

Now my switch config looks like this:

!Current Configuration:

!System Description "PowerConnect 6224, 3.3.4.1, VxWorks 6.5"

!System Software Version 3.3.4.1

!Cut-through mode is configured as disabled

!

configure

vlan database

vlan 2

vlan routing 2 1

exit

hostname "punane"

stack

member 1 1

exit

ip address 192.168.1.233 255.255.255.0

ip default-gateway 192.168.1.1

lacp system-priority 120

interface vlan 2

name "iSCSI"

routing

ip address 192.168.234.230 255.255.255.0

exit

!

interface ethernet 1/g2

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g3

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g4

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g5

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g6

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g7

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g8

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g9

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g10

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g11

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g12

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g13

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g14

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g15

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g16

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g17

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g18

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

!

interface ethernet 1/g19

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface ethernet 1/g20

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface ethernet 1/g21

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface ethernet 1/g22

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface ethernet 1/g23

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface ethernet 1/g24

channel-group 1 mode auto

lacp port-priority 247

exit

!

interface port-channel 1

switchport mode general

switchport general allowed vlan add 2

mtu 9216

exit

Tried also swichpoer general allowed vlan add 2 tagged, no joy.

Pinging from the array member just confirms what we already know, that EHT0 doesn't see the traffic from ETH1 because the LAG is not configured correctly.

Post the following:

show vlan (shortcut is "sh vlan")

show interfaces switchport (shortcut is "sh int port")

show spanning-tree (shortcut is "sh span")

show spanning-tree mst-configuration

show bridge address

Could be that the spanning tree mst isn't setup correctly for the vlans:

-joe

punane#show vlan

VLAN       Name                         Ports          Type      Authorization

-----  ---------------                  -------------  -----     -------------

1      Default                          ch1-48,1/g1,   Default   Required

                                       1/xg1-1/xg4

2      iSCSI                            ch1,1/g2-1/g18 Static    Required

show interfaces switchport (shortcut is "sh int port") is not recognized command, did You mean the port-channel 1 instead?

punane#show interfaces switchport port-channel 1

Port: ch1

VLAN Membership mode:General Mode

Operating parameters:

PVID: 1

Ingress Filtering: Enabled

Acceptable Frame Type: Admit All

Default Priority: 0

GVRP status:Disabled

Port ch1 is member in:

VLAN    Name                              Egress rule   Type

----    --------------------------------- -----------   --------

1       Default                           Untagged      Default

2       iSCSI                             Untagged      Static

Static configuration:

PVID: 1

Ingress Filtering: Enabled

Acceptable Frame Type: Admit All

Port ch1 is statically configured to:

VLAN    Name                              Egress rule

----    --------------------------------- -----------

2       iSCSI                             Untagged

Forbidden VLANS:

VLAN    Name

----    ---------------------------------

punane#show spanning-tree

Spanning tree :Enabled - BPDU Flooding :Disabled - Portfast BPDU filtering :Disabled - mode :rstp

CST Regional Root:        80:00:D0:67:E5:8F:CB:C1

Regional Root Path Cost:  0

ROOT ID

             Address         00:0D:56:3D:F9:22

             Path Cost       30000

             Root Port      1/g1

             Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec TxHoldCount 6 sec

Bridge ID

             Priority        32768

             Address         D0:67:E5:8F:CB:C1

             Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec

Interfaces

Name    State   Prio.Nbr    Cost       Sts  Role PortFast  Restricted

------  -------- --------- ----------  ---- ----- --------  -------

1/g1    Enabled  128.1         20000   FWD  Root      No      No

1/g2    Enabled  128.2         20000   FWD  Desg     Yes      No

1/g3    Enabled  128.3         20000   FWD  Desg     Yes      No

1/g4    Enabled  128.4         20000   FWD  Desg     Yes      No

1/g5    Enabled  128.5         20000   FWD  Desg     Yes      No

1/g6    Enabled  128.6         20000   FWD  Desg     Yes      No

1/g7    Enabled  128.7         20000   FWD  Desg     Yes      No

1/g8    Enabled  128.8             0   DIS  Disb     Yes      No

1/g9    Enabled  128.9         20000   FWD  Desg     Yes      No

1/g10   Enabled  128.10            0   DIS  Disb     Yes      No

1/g11   Enabled  128.11            0   DIS  Disb     Yes      No

1/g12   Enabled  128.12            0   DIS  Disb     Yes      No

1/g13   Enabled  128.13            0   DIS  Disb     Yes      No

1/g14   Enabled  128.14            0   DIS  Disb     Yes      No

1/g15   Enabled  128.15            0   DIS  Disb     Yes      No

1/g16   Enabled  128.16            0   DIS  Disb     Yes      No

1/g17   Enabled  128.17            0   DIS  Disb     Yes      No

1/g18   Enabled  128.18            0   DIS  Disb     Yes      No

1/g19   Enabled  128.19            0   FWD  Disb      No      No

1/g20   Enabled  128.20            0   FWD  Disb      No      No

1/g21   Enabled  128.21            0   FWD  Disb      No      No

1/g22   Enabled  128.22            0   FWD  Disb      No      No

1/g23   Enabled  128.23            0   FWD  Disb      No      No

1/g24   Enabled  128.24            0   FWD  Disb      No      No

1/xg1   Enabled  128.25            0   DIS  Disb      No      No

1/xg2   Enabled  128.26            0   DIS  Disb      No      No

1/xg3   Enabled  128.27            0   DIS  Disb      No      No

1/xg4   Enabled  128.28            0   DIS  Disb      No      No

ch1     Enabled   96.626        3333   DSC  Altn      No      No

ch2     Enabled   96.627           0   DIS  Disb      No      No

ch3     Enabled   96.628           0   DIS  Disb      No      No

ch4     Enabled   96.629           0   DIS  Disb      No      No

ch5     Enabled   96.630           0   DIS  Disb      No      No

ch6     Enabled   96.631           0   DIS  Disb      No      No

ch7     Enabled   96.632           0   DIS  Disb      No      No

ch8     Enabled   96.633           0   DIS  Disb      No      No

ch9     Enabled   96.634           0   DIS  Disb      No      No

ch10    Enabled   96.635           0   DIS  Disb      No      No

ch11    Enabled   96.636           0   DIS  Disb      No      No

ch12    Enabled   96.637           0   DIS  Disb      No      No

ch13    Enabled   96.638           0   DIS  Disb      No      No

ch14    Enabled   96.639           0   DIS  Disb      No      No

ch15    Enabled   96.640           0   DIS  Disb      No      No

ch16    Enabled   96.641           0   DIS  Disb      No      No

ch17    Enabled   96.642           0   DIS  Disb      No      No

ch18    Enabled   96.643           0   DIS  Disb      No      No

ch19    Enabled   96.644           0   DIS  Disb      No      No

ch20    Enabled   96.645           0   DIS  Disb      No      No

ch21    Enabled   96.646           0   DIS  Disb      No      No

ch22    Enabled   96.647           0   DIS  Disb      No      No

ch23    Enabled   96.648           0   DIS  Disb      No      No

ch24    Enabled   96.649           0   DIS  Disb      No      No

ch25    Enabled   96.650           0   DIS  Disb      No      No

ch26    Enabled   96.651           0   DIS  Disb      No      No

ch27    Enabled   96.652           0   DIS  Disb      No      No

ch28    Enabled   96.653           0   DIS  Disb      No      No

ch29    Enabled   96.654           0   DIS  Disb      No      No

ch30    Enabled   96.655           0   DIS  Disb      No      No

ch31    Enabled   96.656           0   DIS  Disb      No      No

ch32    Enabled   96.657           0   DIS  Disb      No      No

ch33    Enabled   96.658           0   DIS  Disb      No      No

ch34    Enabled   96.659           0   DIS  Disb      No      No

ch35    Enabled   96.660           0   DIS  Disb      No      No

ch36    Enabled   96.661           0   DIS  Disb      No      No

ch37    Enabled   96.662           0   DIS  Disb      No      No

ch38    Enabled   96.663           0   DIS  Disb      No      No

ch39    Enabled   96.664           0   DIS  Disb      No      No

ch40    Enabled   96.665           0   DIS  Disb      No      No

ch41    Enabled   96.666           0   DIS  Disb      No      No

ch42    Enabled   96.667           0   DIS  Disb      No      No

ch43    Enabled   96.668           0   DIS  Disb      No      No

ch44    Enabled   96.669           0   DIS  Disb      No      No

ch45    Enabled   96.670           0   DIS  Disb      No      No

ch46    Enabled   96.671           0   DIS  Disb      No      No

ch47    Enabled   96.672           0   DIS  Disb      No      No

ch48    Enabled   96.673           0   DIS  Disb      No      No

punane#show spanning-tree mst-configuration

Name: D0-67-E5-8F-CB-C1

Revision: 0

Instance    Vlan Mapped

----------  -----------------------------------------------

0          1-2

punane#show bridge address

Aging time is 300 Sec

 Vlan        Mac Address       Port          Type

-------- --------------------- ---------- --------------------

1        0000.0000.FE00        1/g1       Dynamic

1        0000.0000.FE01        1/g1       Dynamic

1        000D.563D.F94A        1/g1       Dynamic

1        0015.5D01.1E2F        1/g1       Dynamic

1        0015.5D01.1E38        1/g1       Dynamic

1        0015.5D01.1E3C        1/g1       Dynamic

1        0015.5D01.1E3D        1/g1       Dynamic

1        0015.5D01.1E40        1/g1       Dynamic

1        0015.5D01.1F3F        1/g1       Dynamic

1        0015.5D01.1F40        1/g1       Dynamic

1        0015.5D01.1F41        1/g1       Dynamic

1        0015.5D01.1F44        1/g1       Dynamic

1        0016.EC99.BB90        1/g1       Dynamic

1        0018.8B7F.7E52        1/g1       Dynamic

1        001B.218F.6ED9        1/g1       Dynamic

1        001B.218F.7759        1/g1       Dynamic

1        001B.219D.D56D        1/g1       Dynamic

1        001B.219D.D725        1/g1       Dynamic

1        001C.23E2.9D80        1/g1       Dynamic

1        001D.0983.09A2        1/g1       Dynamic

1        001E.4F0E.5B5E        1/g1       Dynamic

1        0020.6B6B.A840        1/g1       Dynamic

1        0021.706D.7161        1/g1       Dynamic

1        0021.706D.CCAB        1/g1       Dynamic

1        0022.1987.89EF        1/g1       Dynamic

1        0022.1987.89F0        1/g1       Dynamic

1        0025.64C9.AB0F        1/g1       Dynamic

1        0026.B95C.4F21        1/g1       Dynamic

1        0026.B95C.4F22        1/g1       Dynamic

1        0026.B9B9.6D34        1/g1       Dynamic

1        0026.B9CF.9BEF        1/g1       Dynamic

1        0080.7781.CD38        1/g1       Dynamic

1        0090.FB2A.DF86        1/g1       Dynamic

1        00C0.B753.0EB4        1/g1       Dynamic

1        00C0.B753.0ECA        1/g1       Dynamic

1        30E4.DB2A.9693        1/g1       Dynamic

1        7845.C405.0AFA        1/g1       Dynamic

1        842B.2B5D.76AA        1/g1       Dynamic

1        842B.2B75.F84B        1/g1       Dynamic

1        842B.2B75.F84C        1/g1       Dynamic

1        842B.2B75.F84F        1/g1       Dynamic

1        B8AC.6F19.DEB4        1/g1       Dynamic

1        B8AC.6FCA.34FA        1/g1       Dynamic

1        D067.E58F.CB85        1/g1       Dynamic

1        D067.E58F.CB87        1/g1       Dynamic

1        D067.E58F.CBC1        cpu        Management

2        0009.8A06.6949        1/g3       Dynamic

2        0010.1861.E3D8        1/g7       Dynamic

2        0010.1861.E3D9        1/g7       Dynamic

2        0015.5D01.1E31        1/g5       Dynamic

2        0015.5D01.1E3F        1/g5       Dynamic

2        0015.5D01.1E42        1/g5       Dynamic

2        0015.5D01.1F43        1/g5       Dynamic

2        0015.5D01.1F46        1/g5       Dynamic

2        001B.218F.6EDD        1/g9       Dynamic

2        001B.218F.775D        1/g6       Dynamic

2        D067.E58F.CBC3        vlan 2     Management

Regarding the orginal MPIO issue, just to confirm, that you tested (the switches in question), by connecting the hosts and array iSCSI interfaces on only one switch to verify the server connects to a target volume on the array with the number of interfaces you specified with MPIO on the host?  Do this for the second switch as well.

Also, are you using the IP address or the .iqn name of the host iSCSI initiator for the Access Control List on the Array?  The iqn name of the iSCSI initiator is preferred for MPIO.

With that said, the next step would be to reconfigure the LACP/LAG from scratch again:

Note: it is recommended that you physically disconnect the ports to be aggregated at one of the switches during configuration, until both are configured.  It is suggested to do this during a maintenance period if the arrays are in production.

So the standard configuration is as follows:

(config)# interface range ethernet 1/g19-1/g24

(config-if)# channel-group 1 mode auto

For a more detailed configuration try this:

Enter configuration mode

Select all port-channel interfaces

console#interface range port-channel all

To Protect from bringing down a switch or subnet, make sure the LAG is off before configuring

console(config-if)# shutdown

Select the ports that you are going to use in the LAG

console(config-if)# interface range ethernet 1/g19-1/g24

Add those ports to LAG 1, and use the LACP protocol to configure the LAG

console(config-if)# channel-group 1 mode auto

(adds those ports to LAG 1, and use the LACP protocol to configure the LAG)

Select the port-channel interface you just created

console(config-if)# int range port-channel 1

Enable spanning-tree

console(config-if)# no spanning-tree disable

Enable Flow Control, which is required for iSCSI

console(config-if)# flowcontrol on

Keep this config open on the first switch, then open a new telnet and repeat the above on the partner switch and the LAG ports

Then go back to the first switch and with port-channel 1 interface as the active interface, to bring up the LAG.

console(config-if)# no shutdown

Do the same command with port-channel 1 interface as the active interface, on the second switch to bring up the LAG

console(config-if)# no shutdown

console(config-if)#exit

I would keep the swtichport mode trunk as you had in the original config:

console# interface port-channel 1

console(config-if)#switchport mode trunk

console(config-if)#switchport trunk allowed vlan add 2

console(config-if)#exit

to verify:

show interfaces port-channel

show interfaces port-channel [port-channel number]

Alternetelly you can try to set the hashing mode to the default (3) to see if the behavior is the same

console(config)#interface port-channel l

console(config-if-ch1)#no hashing-mode

Beyond this, if you are still having issues (and you confirmed both switches work independently for MPIO), I would suggest that you contact the PowerConnect support team to ensure that the LACP/LAG is configured properly.

-joe

Tried today all these and no joy :(

Servers are connecting to EQL using IQN

If I disable currently active NIC the system fails over to 2nd NIC and communication with EQL restores quickly, but it won't connect to EQL using MPIO (seeing only one of the NICs on the EQL and on the HIT)

So the current configs look like these:

!Current Configuration:
!System Description "PowerConnect 6224, 3.3.4.1, VxWorks 6.5"
!System Software Version 3.3.4.1
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 2
vlan routing 2 1
exit
hostname "punane"
stack
member 1 1
exit
ip address 192.168.1.233 255.255.255.0
ip default-gateway 192.168.1.1
lacp system-priority 120
interface vlan 2
name "iSCSI"
routing
ip address 192.168.234.230 255.255.255.0
exit
!
interface ethernet 1/g2
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g3
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g4
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g5
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g6
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g7
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g8
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g9
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g10
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g11
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g12
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g13
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g14
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g15
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g16
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g17
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g18
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
switchport access vlan 2
exit
!
interface ethernet 1/g19
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface ethernet 1/g20
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface ethernet 1/g21
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface ethernet 1/g22
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface ethernet 1/g23
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface ethernet 1/g24
channel-group 1 mode auto
lacp port-priority 247
exit
!
interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 2
mtu 9216
exit

punane#show interfaces port-channel 1

Channel   Ports                         Hash Algorithm Type
-------   ----------------------------- -------------------
ch1       Active: 1/g19, 1/g20,         3
          1/g21, 1/g22, 1/g23, 1/g24

I have not tested this way that servers have have NIC's connected to only one switch. But before I installed these new PC6224 switches I had 2 year old PC6224 where I did not use VLAN's to separate traffic (they still had LAG). That configuration was working fine and the servers were able to use MPIO.

Array is Equallogic PS4000 firmware V6.0.1

HIT is 4.0.0

Windows is Windows Server 2008R2 (6.1.7601)

MPIO Policy is Least Queue Depth

The configuration has not been changed on servers.

There is one option, I could revert back to that configuration where I do not use VLANs, then the management will be a bit more complicated but at least it solves the MPIO problem.

Is MPIO working if the Host AND EqualLogic interfaces are connected to only ONE switch?

When testing did you see the mac address of both host interfaces (all all array eth interfaces) on both switches?

Also, post the following:

Array FW version

HIT Version

Windows Version

MPIO Policy

Also, to ensure you didn't miss any steps in configuring the host, please review the configuration portal (if using Win2008 servers - both sections 2 and 5).  http://en.community.dell.com/techcenter/storage/w/wiki/3615.rapid-equallogic-configuration-portal-by-sis.aspx

-joe

If/when the switches are disconnected from your LAN/Management network, serial/telnet/ssh into one of them, and try to ping the other switch (on the 192.168.234 subnet) to see if that works.

Other than that, I'd suggest to start from scratch and build from the basics up.

A config like this comes to mind:

======================

configure

vlan database

vlan 2

exit

hostname "punane"

exit

ip address 192.168.1.233 255.255.255.0

ip default-gateway 192.168.1.1

interface vlan 2

name "iSCSI"

exit

interface range ethernet 1/g2-1/g18

storm-control broadcast

storm-control multicast

spanning-tree portfast

mtu 9216

switchport access vlan 2

exit

interface range ethernet 1/g19-1/g24

channel-group 1 mode auto

exit

interface port-channel 1

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 1,2

exit

flowcontrol

======================

This takes routing and your LACP priority settings out of the picture (only do routing if you plan on doing replication on the Equallogic array), but if this works, build up from there till you see what breaks your setup.

So finaly had the time to redo both switches with the offered configuration.

No luck, still servers connect to only one ethernet port on PS4000. :(

I went back to my original configuration, where I don't have VLANs, derfor eliminating the possibility to manage switches from my desktop. But now MPIO is working again, so it's a small price to pay.