Your over subscription ratio ? (Usually 3:1 is good for most part) You gonna need single or multi stage CLOS ? How you gonna connect to external world ? (Border Spine Vs. How you gonna introduce security & Services such as Load Balancer ? How you gonna manage and monitor such large network ? Your network is going to multi vendor now/In future ? Where to define Layer2-Layer 3 boundary ? How you can minimize the state of the Core (Spine) to minimum ? Your DC traffic is mostly east-west or north-south ? What are technical and business requirements ? What is the scale that you got to deal with ? Here are some questions/Things you figure out about CLOS if you decide to go for it : Now in theory Layer 3 Fabrics scale much better than Layer 2 Fabric. So you are pretty much dependent upon what works best for you from vendor implementation perspective while keeping your overall goal in mind. While scalability is a matter of context, it's not necessary that everyone needs or to be precise going too far about it.Īlso CLOS fabric also doesn't define your Layer2 - Layer 3 boundaries itself. The major problem that CLOS fabric solves is about solving scalability issues. Well you should start by asking why CLOS in first place ? Most of companies in these segments present their products like real Other stuff well and standardize them across vendors Lack of new networking models to define and shape th ese protocols and There are very limited books and texts around these topics and some are These things which really makes the situation tough Most traditional network certifications, classes & courses don't cover Well there are couple of moving pieces which you need to consider: On the other hand important question is " Should I be afraid ? " Now to me these are old ideas which are wrapped in nice package (Remember RFC 1925 Rule 11) but certainly needed to meet business demands and scale in current scenario and near future depending upon what all business problems you are trying to solve with technology. New requirements in terms of scales and get rid of some old challenges Enhancements into existing protocols considering their proven historyĪnd robustness ( BGP LS, BGP EVPN, Segment Routing etc.) to meet Some old fundamentals re-discovered (Cap theorem, Game theory, Clos Support with CLI in past or missing shell access etc.) Fixes applied to some traditional techniques (e.g. Some better protocols/techniques to support workload mobility (e.g. Network virtualization techniques (e.g. Good Orchestrator that really works well for most part (Numerous failed Overlay Networks (Host Based, Network Based or Hybrid - e.g.: VxLAN etc.) Now if you take a closer look, most of these products are good mix of: What are the new models, frameworks and protocols that works in the background (Check under the hood) Well it depends upon what's your personal take on SDN to begin with in terms of : So coming back to idea of there is fundamentally something new. Now let's not try to define SDN here and keep it for next post since I would wan't to clarify on some of misconceptions. Protocols like Open Flow will take over the world soon and re-define the networking completely SDN is the only thing that the next generation networks would be build around or run (Mostly these are people claiming themselves as SDN/NFV experts or evangelist) Some people seems to be afraid of loosing there jobs thinking they will be irrelevant in near future, well lots of posts are there on web where people are throwing opinions about whats the value of CCIE now and if CCIE is relevant any longer. Let's first review some of interesting facts: For quite some time I have been sort of irritated (for lack of better word) by hearing and discussing about buzz word in the market called SDN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |