http://blog.ioshints.info/2010/08/storage-networking-is-different.html
http://www.nanog.org/meetings/nanog55/presentations/Sunday/Hudson_Storage.pdf
其實就是loseless, 不過, 對我這種networking 老賊 , 就還是有笨問題
, 掉就掉, 重傳就好, HD Video這種real time, 都搞得定, IP萬歲!
FC到16Gbps到頂 (和SDH到40G一樣), L1/L2已被Ethernet大一統,
FC想藉FCOE延續生命, 還是被專家們唱衰(如冬瓜頭)
reminder to myself
data corruption will occur serious chain reaction
http://www.zdnet.com/blog/storage/data-corruption-is-worse-than-you-know/191
SAN needs redundant separate fabric( no connected) + multipath software + redundant HBA
SAN connection scheme is p2p
SAN connectivity is p2mp ( target-initiator)
SAN nodes divide into host(initiator) and storage( target)
SAN no broadcast (heavily rely on switch intelligence)
SAN forwarding is kinda routing (or TRILL)
http://www.nanog.org/meetings/nanog55/presentations/Sunday/Hudson_Storage.pdf
其實就是loseless, 不過, 對我這種networking 老賊 , 就還是有笨問題
, 掉就掉, 重傳就好, HD Video這種real time, 都搞得定, IP萬歲!
FC到16Gbps到頂 (和SDH到40G一樣), L1/L2已被Ethernet大一統,
FC想藉FCOE延續生命, 還是被專家們唱衰(如冬瓜頭)
reminder to myself
data corruption will occur serious chain reaction
http://www.zdnet.com/blog/storage/data-corruption-is-worse-than-you-know/191
SAN needs redundant separate fabric( no connected) + multipath software + redundant HBA
SAN connection scheme is p2p
SAN connectivity is p2mp ( target-initiator)
SAN nodes divide into host(initiator) and storage( target)
SAN no broadcast (heavily rely on switch intelligence)
SAN forwarding is kinda routing (or TRILL)
Comments