Hot answers tagged


No - iSCSI runs over IP, the switch doesn't need to know how to specifically handle it for iSCSI to run.


Very interesting question. The more I think of an answer to this problem them more road blocks I am hitting. Here is a few possible solutions that I can think of: Two NICs in Each Machine + Two Switches This is obviously what you suggested but you might run into problems with each computer on your network taking 2 IP address's. What I would suggest for ...


You will need the multiple NICs in each box and the two switches, with each box plugged into both switches. Then setup NIC Teaming/NIC Bonding. For most modern operating systems it is a pretty simple setup, and in most basic environments it will just work. In Windows Server 2012 you have to use Switch Independent mode and the OS will take care of ...


Dell's iSCSI mode just tracks targets and initiators, all you should really be doing is follow the specific best practices for that switch/SAN, usually this is MTU 9k+ (Force10 use 12k) Flow control rx on tx off Never do port channels, each interface should have a single ip, use multipath to aggregate links. Avoid vlan tagging


This image represents an entry level amount of redundancy that can be achieved network wide. Switch 1 and Switch 2 represent a collapsed Core/Distribution network and Switch 3, 4, and 5 represent an access network. Switches 1 and 2 should usually be aggregated by combining them into some kind of stack when possible, however you can configure them as 2 ...


In addition to Ondra Sniper Flidr and the comment by Michael Hampton, I wanted to provide the official statement by Citrix. Quoting this pdf (didn't found this in HTML), chapter "XenMotion", page sixteen: But in this example setup, the external real switch device is expecting the MAC address of the VM to be on one port, while it‟s actually just ...

Only top voted, non community-wiki answers of a minimum length are eligible