Software & provisioning
The same containers, the same GitOps repositories. An additional node or stack is a commit, not a project.
BNGbox · Deployment scenarios
The same software at your scale
Three typical deployments. The same software and control plane with a varying number of server nodes, the sites and the connection to the aggregation network. We work out which scenario fits your network with your team.
Scenario 1
Single-node cluster
One node hosts both the control plane and the user plane. This is the entry point for lab work, pilots and small ISPs.
| Nodes | 1 |
| Sites | 1 |
| Ethernet segments | 1 |
| Control plane | on the node |
| Fits | Testing in the lab, pilots, networks with one PoP |
Scenario 2
Multi-node stack
Multiple nodes at one site form a cluster. The user planes are distributed across the nodes, while the control plane runs in the same stack. Two nodes are enough for redundant user planes. You can scale by adding more nodes.
| Nodes | 2 or more |
| Sites | 1 |
| Ethernet segments | 1 |
| Control plane | in the stack |
| Fits | Regional carriers and municipal utilities with one central PoP |
Scenario 3
Multiple stacks, one cluster
Stacks at several sites with their own Ethernet segments, connected over L3, under a common control plane. Session termination moves to the site where the subscribers connect; control and operations stay in one place. If a site loses its connection, its existing sessions stay up. New sessions can be established once the connection is restored.
| Nodes | 2 or more per stack |
| Sites | 1 to n |
| Ethernet segments | one per site, connected over L3 |
| Control plane | one, for all stacks, at one site or spread over three |
| Fits | Several PoPs or racks, wholesale providers with sites per partner |
What stays the same
Three set-ups for one product
The scenarios differ in hardware and network connectivity, rather than in software, control or operations. A deployment grows from the first scenario to the third without reinstalling anything.
Subscriber groups
The group is the unit you scale in every scenario. How CUPS and subscriber groups work together.
Operations
Software & Care, with operations run by your team or your integrator: the operating model is independent of the deployment scenario. Software & Care in detail.
How many subscribers and how much throughput a node supports in your deployment depends on packet sizes, traffic profile and hardware. We agree these figures with your team, based on reliable evidence rather than a calculator result.
Next step
Which scenario fits your network?
Bring your topology: sites, OLTs and aggregation. We draw the deployment with you and identify the hardware it needs.