Over recent years, ‘cloud-native’ service providers have developed ways to build and run massive data centers with a high degree of automation, to reduce operational overheads and deliver levels of service agility beyond traditional carrier infrastructure. RtBrick’s disaggregated BNG brings these same benefits to carrier access networks, by using agile methodologies and the same battle-hardened DevOps cloud automation tools that have been adopted by the world’s biggest cloud providers.
The RtBrick BNG is delivered as a software container, packaged out-of-the-box with the Open Network Linux (ONL) provided by the hardware SKU manufacturers, which handles peripherals such as LEDs, temperature sensors, and so on. There are no dependencies on either the kernel or the hardware platform components, so RtBrick’s containers can be run on the Linux version of your choice.
The RtBrick BNG software can run on either an x86 server as a vBNG, or for most carrier-scale deployments, on low-cost but powerful bare-metal switches.
RtBrick’s disaggregated BNG delivers some significant benefits compared to traditional monolithic systems:
· Greater agility – you can add new services in weeks rather than years
· Reduced risk – no more vendor lock-in and a simpler automated operating environment
· Cloud cost-levels – leverage low-cost merchant silicon and automate your operations like a ‘cloud-native’
ZTP (Zero-Touch-Provisioning) ensures that each switch is booted, provisioned and operational without requiring manual intervention. This means that you can add capacity, or roll-out new service features, in a matter of minutes instead of days or weeks. The software itself is developed using Agile methodologies so that features are rapidly prototyped and implemented, reducing the time-to-market for new services.
RtBrick’s BNG software is compiled for your specific use-case, using only the features you need. With an order of magnitude fewer lines of code, and a single state database rather than hundreds, the whole system is less complex, less prone to bugs and has much faster restart times. It also allows you to pick and mix between the latest silicon and the best available software.
Now you can take advantage of the low cost-points of merchant silicon on your choice of bare-metal switches, significantly reducing your capex bill. And opex costs can be reduced by automating your operations, using ZTP and the same Web2.0 operational tools that the ‘cloud-natives’ use to run their infrastructure.
The BNG’s subscriber management capacity is provided in a scale-out architecture called the Point-Of-Deployment (PoD). A large-scale PoD consists of Access Leaf Routers and Border Leaf Routers aggregated by a layer of Spine Leaf Routers in an auto-provisioned CLOS topology. The Access Leaves deliver subscriber management functionality and the Border Leaves provide connectivity to the core of the provider network.
The leaves can be scaled out horizontally to increase the number of subscribers supported on the PoD, providing a pay-as-you-grow architecture. For smaller PoDs, Spine and Border Leaf functionality can be collapsed onto a single hardware platform, depending upon the hardware platform used. PPPoE Subscribers can be terminated on the Access Leaf Routers or tunneled to an LNS over L2TPv2. L2 Cross Connect (L2X) allows subscriber traffic to be tunneled out of the PoD at Layer 2, providing wholesale connectivity.
The RtBrick BNG software can also run on an x86 server to create a vBNG (Virtual Broadband Network Gateway).
You can re-use your existing infrastructure to continue to provide lower volume legacy services, and optimize the rest of the network for the bulk of your traffic - providing large volumes of high bandwidth services at a lower cost-point with a web-scale operating environment. So your RtBrick BNG can also act as a service cross-connect, routing each subscriber to the appropriate network infrastructure and extending the life of your high-cost legacy BRAS or BNG systems, for example.
Along with the traditional CLI and SNMP, more ‘cloud-native’ means of interactions are also supported, such as gNMI and Netconf. RtBrick’s Management System, RBMS, takes this a step further, by providing network level workflows such as Image Lifecycle Management, Network Upgrades and Event and Log Management. RBMS actions are available through REST APIs making them easy to integrate into existing OSS systems. RBMS provides a single point of interaction for operations staff – from provisioning and management to monitoring and debugging.
The result is a BNG that can be managed using the latest Web2.0 tools through a ‘single pane of glass’, with Zero-Touch-Provisioning.
The features supported by RtBrick FullStack are expanding all the time, because it's much faster for us to add and test new features than it is using a traditional monolithic code base. Currently supported features include:
|ACLs (IPv4/6, L2)||✔|
|QoS (policing, scheduling, queuing, hierarchical)||✔|
|Accounting (Time/Volume based)||✔|
|ResmondD (RtBrick resource monitoring application)||✔|
|RBMS (RtBrick Management System)|
|Topology Discovery & Inventory||✔|
|Dynamic Service Selection||✔|
* may include some road-map features
RtBrick's Full Stack routing software can operate on many bare metal switches, depending on your performance and port count requirements. You can find details of compatible hardware here.