Unsolved
This post is more than 5 years old
6 Posts
0
142362
July 30th, 2013 13:00
Perfect iSCSI Config for PowerConnect 6224 ?!?
Hi there :)
i'm setting up two new PowerConnect 6224 for iSCSI network. But i'm not sure if the config is completly perfect. Because our HP ProCurve 2848 give me a better IOPS performance, but without JumboFrames !!!
The switch config on both devices is the same. I've connected the two switches via LAG on port 21-24. But i get the same performance by using one or two switches. Port 1 is configured for management.
Anybody have an idea how to tune up this config? :)
Config:
console#show running-config
!Current Configuration:
!System Description "PowerConnect 6224, 3.3.5.5, VxWorks 6.5"
!System Software Version 3.3.5.5
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 10
exit
stack
member 1 1
exit
ip address X.X.X.X
ip address vlan 10
!
interface ethernet 1/g1
storm-control broadcast
storm-control multicast
spanning-tree portfast
switchport access vlan 10
exit
!
interface ethernet 1/g2
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g3
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g4
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g5
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g6
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g7
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g8
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g9
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g10
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g11
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g12
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g13
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g14
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g15
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g16
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g17
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g18
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g19
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g20
storm-control broadcast
storm-control multicast
spanning-tree portfast
mtu 9216
exit
!
interface ethernet 1/g21
channel-group 1 mode on
mtu 9216
exit
!
interface ethernet 1/g22
channel-group 1 mode on
mtu 9216
exit
!
interface ethernet 1/g23
channel-group 1 mode on
mtu 9216
exit
!
interface ethernet 1/g24
channel-group 1 mode on
mtu 9216
exit
!
interface port-channel 1
mtu 9216
exit
exit
sketchy00
203 Posts
0
July 30th, 2013 17:00
At the risk of being self serving, I will say that my posts on rebuilding the 6200 series switches for EqualLogic has not only been extremely popular, but I've used the same arrangement to deploy in a number of environments beyond just my own. It's bomb proof. But aside from that, yes, make sure you are running the latest firmware.
vmpete.com/.../reworking-my-powerconnect-6200-switches-for-my-iscsi-san
alexxxxxx
6 Posts
0
July 31st, 2013 03:00
I've installed the FW Version 3.3.5.5 - the config i've posted is identicaly on both switches. I've only changed the ip! But after connecting my ESXi's the communication between Ports on different switches don't work anymore. I think it must be the LAG-Config.
alexxxxxx
6 Posts
0
July 31st, 2013 06:00
Yes Port-Channel 1 is the connection between the two switches (g21-g24). I've created VLAN 10 only to seperate the iSCSI Traffic from Mgmt-Network. In my config only Port g1 has access to VLAN 10. I would use the default VLAN for ISCSI-Traffic (g2-g20).
Actually i can't ping between the two switches. I'm using a HP MSA P2000 G3 in this environment. But next week i'll connect a PS4100XS too. If it works :D