Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

41558

July 6th, 2012 12:00

Powerconnect 6224 Config help with Equallogic PS4100

Hello,

first post and a lot to ask :) To cut a long story short I recently received 2 Dell 6224 along with an Equallogic PS4200 storage to implement vmware with it. Managed to set everything up and got 3 R610 connected on it. I can vmotion, thanks to all the posts and comments that I have found around that help me configure everything.

My remaining problem are the switches. As I am not at all a networking guru and this is new to me, I am sure that I haven't configured the 6224 correctly. As we haven't purchased the stacking module I decided to create a LAG with ports 21 -> 24. First question that might be stupid but just to be sure, for the LAG you have to connect port 21 from switch1 with port 21 of switch 2 with a straight cable right and so on the three others right ?

Goal is to have those 2 switches connected together for redundancy. Port 1 will be used for management, Port 2 -> 16 for iscsi traffic (vlan 2), Port 17 -> 20 for vmotion traffic (vlan 3).

Vmotion works with vlan 3 tagged in vmware however iscsi network doesn't work with vlan 2 tagged. I haven't figured out how to tag the PS4100 traffic with the vlan 2 and I think that's where the issue is. I read about DCB that had to be activated but haven't managed to find how to activate this at switch level. Found the DCB thing in the PS4100 group admin. Any advice for the PS4100 vlan tagging would be really appreciated.

Attached is the config of the switch (same for both except the management IP of course). I am pretty sure I have missed something even if I have been following famous post like "you have received your equallogic box, now you what" and went also through all the config guides and a lot of post & forums.

As I am stuck with this I would really appreciate any help or advice.

Regards

One more thing, what does the vlan routing 2 3 & vlan routing 3 2 stands for in the switch config ? In some of the config I have seen it is not here but I never managed to get rid of it :)

Eelm

 

!Current Configuration:
!System Description "PowerConnect 6224, 3.3.1.10, VxWorks 6.5"
!System Software Version 3.3.1.10
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 2-3
vlan routing 2 1
vlan routing 3 2
exit
stack
member 1 1
exit
ip address 192.168.90.251 255.255.255.0
ip default-gateway 192.168.90.2
lacp system-priority 120

interface vlan 2
name "iscsi"
routing
ip address 10.10.10.2 255.255.255.0

interface vlan 3
name "vmotion"
routing
ip address 10.10.11.2 255.255.255.0

username "admin" password xxxxxxxxxxxxxxxxxx level 15 encrypted

interface ethernet 1/g1
spanning-tree disable
mtu 9216

interface ethernet 1/g2
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g3
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g4
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g5
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g6
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g7
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g8
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g9
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g10
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g11
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g12
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g13
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g14
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g15
spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g16
Spanning-tree disable
mtu 9216
switchport mode general
switchport general pvid 2
switchport general allowed vlan add 2

interface ethernet 1/g17
spanning-tree disable
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 3

interface ethernet 1/g18
spanning-tree disable
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 3

interface ethernet 1/g19
spanning-tree disable
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 3

interface ethernet 1/g20
spanning-tree disable
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 3

interface ethernet 1/g21
channel-group 1 mode auto
lacp port-priority 247
spanning-tree disable
mtu 9216

interface ethernet 1/g22
channel-group 1 mode auto
lacp port-priority 247
spanning-tree disable
mtu 9216

interface ethernet 1/g23
channel-group 1 mode auto
lacp port-priority 247
spanning-tree disable
mtu 9216

interface ethernet 1/g24
channel-group 1 mode auto
lacp port-priority 247
spanning-tree disable
mtu 9216

interface ethernet 1/xg1
spanning-tree disable
mtu 9216

interface ethernet 1/xg2
spanning-tree disable
mtu 9216

interface ethernet 1/xg3
spanning-tree disable
mtu 9216

interface ethernet 1/xg4
spanning-tree disable
mtu 9216

interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 2-3
mtu 9216

7 Technologist

 • 

729 Posts

July 6th, 2012 14:00

The LAG doesn’t have to match 1:1 (from switch-A port # to the switch-B port #, although it’s easier to manager if done in this way).  Note that depending on the ASIC of the switch you typically don’t flood a single ASIC with all your LAGs, they would be spaced out across all ASIC’s.  In this case the 6224 only has one ASIC. (Note, the same holds true for ports in a VLAN, typically you don’t put them all in the same ASIC).

At quick glance, you need to enable spanning-tree on the LAG ports (on both sides of the LAG, so that each switch can learn the MAC address from each other).  You also need to add the following to the LAG ports (both sides):

no storm-control unicast

channel-group 1 mode on (instead of auto)

For the iSCSI interfaces, you also should enable the following:

no storm-control unicast

spanning-tree portfast

-joe

Moderator

 • 

6.2K Posts

July 6th, 2012 15:00

Hello eelm

First question that might be stupid but just to be sure, for the LAG you have to connect port 21 from switch1 with port 21 of switch 2 with a straight cable right and so on the three others right ?

Ideally you would want to use a crossover cable when connecting two switches. Our switches are capable of auto-negotiating the cable type and correcting for it. Because of this you can use straight through or crossover and the switch will act the same with either.

Any advice for the PS4100 vlan tagging would be really appreciated.

Change ports 2-16 to access mode(switchport mode access). The way you have them configured they are currently acting as access ports. If you have them connected to a virtual switch then that could be the problem. They are not currently tagging packets.

One more thing, what does the vlan routing 2 3 & vlan routing 3 2 stands for in the switch config ?

Whenever you assign an IP address to a VLAN it creates that entry. There is no way to get rid of it without removing the IP addresses from the VLAN's. It is listing the index number assigned to the VLAN.

Thanks

7 Technologist

 • 

729 Posts

July 9th, 2012 08:00

I didn’t see the unicast or flow control settings.

Ensure flow control is enabled on the iSCSI interfaces (per the configuration guide recommendations listed here: en.community.dell.com/.../2639.equallogic-configuration-guide.aspx). This is a global command.

To check the status you can use: console#show interfaces status

Also, it’s recommended for this switch to have the “no storm-control unicast” on all the switch ports, but especially on the iSCSI ones.  Use the “show storm-control all” to view the current settings.

-joe

9 Posts

July 6th, 2012 15:00

Thanks Joe for your reply. I ll test that Monday and post back the full configuration. Can help someone else maybe someday. Cheers Eelm

9 Posts

July 9th, 2012 02:00

Thanks to both of you.

Based on what you wrote I have updated both switches config. I have also upgraded to the last firmware.

Here is the updated config. Please let me know if there is anything you think I should change ;)

Current Configuration:

System Description "PowerConnect 6224, 3.3.3.3, VxWorks 6.5"

System Software Version 3.3.3.3

Cut-through mode is configured as disabled

configure

vlan database

vlan 2-3

stack

member 1 1

ip address 192.168.90.251 255.255.255.0

ip default-gateway 192.168.90.2

lacp system-priority 120

interface vlan 2

name "iscsi"

interface vlan 3

name "vmotion"

username "admin" password xxxxxxxxxxxxxxxxxxxxxxxxxx level 15 encrypted

interface ethernet 1/g1

mtu 9216

interface ethernet 1/g2

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g3

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g4

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g5

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g6

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g7

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g8

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g9

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g10

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g11

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g12

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g13

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g14

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g15

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g16

spanning-tree portfast

mtu 9216

switchport access vlan 2

interface ethernet 1/g17

spanning-tree disable

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 3

interface ethernet 1/g18

spanning-tree disable

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 3

interface ethernet 1/g19

spanning-tree disable

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 3

interface ethernet 1/g20

spanning-tree disable

mtu 9216

switchport mode trunk

switchport trunk allowed vlan add 3

interface ethernet 1/g21

channel-group 1 mode on

lacp port-priority 247

mtu 9216

interface ethernet 1/g22

channel-group 1 mode on

lacp port-priority 247

mtu 9216

interface ethernet 1/g23

channel-group 1 mode on

lacp port-priority 247

mtu 9216

interface ethernet 1/g24

channel-group 1 mode on

lacp port-priority 247

mtu 9216

interface ethernet 1/xg1

mtu 9216

interface ethernet 1/xg2

mtu 9216

interface ethernet 1/xg3

mtu 9216

interface ethernet 1/xg4

mtu 9216

interface port-channel 1

switchport mode trunk

switchport trunk allowed vlan add 2-3

mtu 9216

9 Posts

July 10th, 2012 00:00

Hi Joe,

Flow control is enabled (active) on all interfaces and storm-control is shown as disabled in all mode.

At first sight this final config that you both help me to fine tune seems just fine and everything is working great so far :)

Thanks a lot to both of you for your quick & clear replies.

Cheers

Eelm

No Events found!

Top