Jump to...
redirecting...

Log for 電訊台

[photo](media:AgACAgUAAx0CT0ncdwABAud6YgoRLw2t5kTbepJldYwBcNGDS_EAAsevMRubY1FUg2FbmAPqjxABAAMCAANzAAMjBA@telegram)
邊個site
London, lol
咁啱bdx都出事,唔畀我入去
BDX 係Digital Realty 的嗎?
唔係
查咗,DBX係Telstra own
@licson 點解一個fat tree k-ary tree architecture個aggregation-edge layer唔整mesh network嘅
[photo](media:AgACAgUAAx0CT0ncdwABAueCYgodAvRZVO7k1XMfDrh_oZ4CW5oAAtqvMRubY1FUuww2xmoc-rMBAAMCAANzAAMjBA@telegram)
mesh = 好多條線
好似張圖 Spine and leaf 嘅話有 redundancy 之餘唔至於咁多條線
但係fault tolerance咪得k/2
咁係佢張圖駁法問題
如果每隻 leaf 都有 4 條嘅話其實四部死三部都得
同埋正常死一部都已經要去換
Distance同cost
用一個具體例子就明:你係紅磡poly,對上edge就係紅磡exchange,再上嘅aggregation就係佐敦exchange。如果mesh左嘅話,行bus line會collide,行p2p all mesh嘅結果係你個edge可能會走左去元朗exchange 或者係香港仔exchange,之後再route返去佐敦。對你就lag,對telco就分唔清faultpoint 同cost太大
有resilience 就可以唔洗咁急嘅🤐
呢個係考慮埋 MAN/WAN
但係如果純粹係 LAN 嘅話就無得咁講
oic
考慮Lan嘅話….要睇下size幾大,say polyu campus定係弊公司東區機樓
中間有幾多connection同埋幾大量
如果純粹係soho 嘅,mesh同layer type 就真係差別唔大
Network fabric card掛