![]() ![]() In the lab (and production) network we have above, OcNOS is deployed as the MPLS core at each data center and MikroTik routers are being used as MPLS PE routers. This is especially true for startup ISPs that may be limited in the amount of capital that can be spent in a service area to keep ROI numbers relatively sane for investors. Unlike enterprise networks, cost is more consistently a significant driver when selecting network equipment for ISPs. This in turn creates a significant competitive advantage as ISPs can take the same budget (or less) and roll out 100 gig instead of 10 gig – as an example The cost difference is so large that often ISPs are able to buy switches with a higher overall port speeds than they could from a major vendor. ![]() This is where IPI really shines as they have feature sets like MPLS FRR, TE and the newer Segment Routing for OSPF and IS-IS that can be used in a platform that is significantly cheaper than incumbent network vendors. Use case – Building an MPLS core to deliver L2 overlay servicesĪlthough certainly not a new use case or implementation, MPLS and VPLS are very expensive to deploy using major vendors and are still a fundamental requirement for most ISPs. Here is an overview of the EVE-NG lab we built based on an actual implementation. What does a production OcNOS based MPLS network look like? There is a great overview of OcNOS from Networking Field Day 15 here: IP Infusion has been making network operating systems (NOS) for more than 20 years under the banner of its whitelabel NOS – ZebOS.Īs disaggregated networking started to become popular, IPI created OcNOS which is an ONIE compatible NOS using elements and experience from 20 years of software development with ZebOS. It’s especially exciting for me as I work on implementing IPI on a regular basis and integrating OcNOS into client networks. This will be the second time IPI has presented at Networking Field Day but the first time that I’ve had a chance to see them present firsthand. Things are really starting to heat up in the disaggregagted network space after the announcement by Amazon a few days ago that it intends to build and sell whitebox switches.Īs I write this, I’m headed to Networking Field Day 18 where IP Infusion will be presenting and I expect whitebox will again be a hot topic. Whitebox often faces the perception problem of being more difficult to implement than traditional vendors – which is exactly why I wanted to highlight some of the work we’ve been doing at integrating whitebox into production ISP networks using IP Infusion’s OcNOS. ISPs are working to figure out how to integrate and move to production on disaggregated models to lower the cost of investing in higher speeds and feeds. Whitebox, also called disaggregated networking, has started changing the rules of the game. This can be an especially daunting task when routers with the feature sets ISPs need cost an absolute fortune – especially as new port speeds are released. One of the challenges service providers have faced in the last decade is lowering the cost per port or per MB while maintaining the same level of availability and service level.Īnd then add to that the constant pressure from subscribers to increase capacity and meet the rising demand for realtime content. Moving away from incumbent network vendors ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |