How do I do this?
Here are some best practices to follow when configuring your network. Also remember if using stacked switches, to map your ports, and fully understand what happens on a firmware upgrade to your network stack. Most stacked switches don't allow for rolling updates, and will require the entire stack to be rebooted. If this is longer than your timeouts allow you will need to plan accordingly.
iSCSI Switching best practices
Some high level best practices:
1)separate mgmt from data traffic (have dedicated VLAN for each type of traffic)
2)configure flow control for the network ports
3)if jumbo frame were to be used, ensure it is enabled end-to-end (from host NIC to access switch ports to nimble data interface ports)
4)K.I.S.S (keep it simple st*pid): stay with default settings in ESX and/or physical hosts (unless told by tech support explicitly)
A few more recommendations (current as of 188.8.131.52)
Got the following set of tips from Eddie Tang (thanks Eddie):
another point from Adam Herbert on ISL vs. stacking switches, on this very same subject - here's my opinion, most enterprise class switches can be stackable - and yes, it is best to stack the switches. If customer is using Cisco Nexus switches, then recommend customers to configure vPC (virtual port channeling)
Be cautious about just simply adding a couple of ISL links between switches that also uplink into a core. Spanning tree will elect the ports that are closest to the root node for uplinks. The ISL links will have a higher cost and will be disabled unless configuration is done to override this. In this scenario iSCSI traffic will traverse the core rather than the ISL links. This cannot be fixed by simply disabling spanning tree on the uplinks due to a risk of a layer 2 loop. This is why a stacked switch design is better because the stack will share a MAC bridging table.
Retrieving data ...