Hi J.

How could we guarantee that's SCSI flows from one intiator to a specified target won't take exactly the same Spine in emulated Fabric A and B?

And if this was the case, what would be the impact (in terms of reading/writing) of a reboot/failure of this spine? If we consider that we have approximately 100ms of reconvergence, is there any "chance" that the server completely lose connectivity to its remote disks/datastrores?

In any case, your article is great and gives a good perspective of a possible future for mutualized NextGen DC Architecture.

Best.
Pierre-Louis