we are designing port connectivity on powerstore T series, example 500T or 1000T
from the network switch side - 2 switches S4128 with sfp+ for ToR - ready VLTi with QSFP
can we do the following options #option1 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS, iSCSI The question is, can we increase the throughput for the iSCSI connection, to 20Gb with this option?
#option2 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb): for iSCSI the question is, can port2 & port3 be bonded or LACP? thus yielding 20Gb for iSCSI
#option3 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb), not-bonding port : for iSCSI the question is, do port2 & port3 only support multi-path, or can it be bonded through a network switch configuration? so we can increase the throughput for the iSCSI connection, to 20Gb
For PowerStore T, only port 0 and port 1 of mezz card configure as system bond by default. Port 2 and port 3 does not support system bond, use multipath for load balancing.
You can refer to example of cabling from Dell EMC PowerStore Networking Guide for PowerStore T Models doc:
#option1 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS, iSCSI The question is, can we increase the throughput for the iSCSI connection, to 20Gb with this option? yes can, because this port already bonding, and this port can we set for iSCSI connection traffic
#option2 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb): for iSCSI the question is, can port2 & port3 be bonded or LACP? thus yielding 20Gb for iSCSI no, because port2 & port3 not support bonding
#option3 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb), not-bonding port : for iSCSI the question is, do port2 & port3 only support multi-path, or can it be bonded through a network switch configuration? so we can increase the throughput for the iSCSI connection, to 20Gb yes can, with multipath configuration, support failover and load balancing
please correct my assumption..
and can you explain about the port channel for iSCSI connection traffic ? can we configure port2 & port3 with port channel without configuring multipath to get 20gb connection ?
#option1 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS, iSCSI The question is, can we increase the throughput for the iSCSI connection, to 20Gb with this option? yes can, because this port already bonding, and this port can we set for iSCSI connection traffic and support for port channel
#option2 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb): for iSCSI the question is, can port2 & port3 be bonded or LACP? thus yielding 20Gb for iSCSI no, because port2 & port3 not support bonding and no support port channel
#option3 port0 (10Gb) & port1 (10Gb), (default bonding or LACP): for traffic cluster, NAS port2 (10Gb) & port3 (10Gb), not-bonding port : for iSCSI the question is, do port2 & port3 only support multi-path, or can it be bonded through a network switch configuration? so we can increase the throughput for the iSCSI connection, to 20Gb yes can, with multipath configuration, support failover and load balancing and no support port channel
Yes, your assumption is correct. Please take note that LACP port-channel provides high availability and potentially increased throughput, however the maximum throughput between any two devices will not exceed the link speed of the physical port. Meaning single flow max throughput is still 10Gb.
#option2 - port2 and port3 can be use for iSCSI but no configured as port-channel
I also believe this to be true that the 500T does not support LACP/LAG on port 0 and 1 like Dell says. WE are try to implement a 500T iSCSI with ESXi and Cisco switches. We cannot get LACP to come up on IO module ports 0 and 1. Dell says this is the proper config and I disagree. Does anyone have a sample config for iSCSI, ESXi and Cisco 3650 or 9300 switches? It seems to be rocket science to get Dell to help with this configuration. It would be great to know the Cisco configure, Storage config and the ESXi configure someone has in production.
PowerStore supports LACP bonding on the first two ports of the on-board mezzanine cards. Are you saying that the LACP bonds are not configurable on those first two ports? If so, I recommend working with Support to triage this further.
Note that PowerStore does not support LACP on the IO Module ports yet. This is a roadmap item.
Ports 0 and 1 on the ON Board 4 port I/O board (the one that ships) does not support LACP on the 500T. I had the exact same issue and was told it only supports LACP/LAG with the mezzanine card which is only fiber. I use Cisco C9300 switches. Only thing I could do was configure as MPIO. Yeah, not expecting that since Dell's literature makes you assume its supported. NOPE.
See the picture I have attached. The red arrows are the mezzanine slots. The on board I/O are the ones with Cat cables plugged in.
Dell-HooHongOoi
1 Rookie
•
54 Posts
4941
0
Posted October 1st, 2021 02:00
For PowerStore T, only port 0 and port 1 of mezz card configure as system bond by default. Port 2 and port 3 does not support system bond, use multipath for load balancing.
You can refer to example of cabling from Dell EMC PowerStore Networking Guide for PowerStore T Models doc:
https://www.dell.com/support/manuals/en-us/powerstore-1000t/pwrstrt-ntwkg/cable-the-base-enclosure-to-the-tor-switches?guid=guid-209dd57f-632e-4bc2-bf6d-a6f4e2608b4b&lang=en-us