Such chassis are based on a fixed set of resources of different types:
- Compute resources: x86 CPU executed instructions
- Storage resources: RAM, storage etc.
- Bandwidth resources: traffic forwarding in and out of and within the chassis (AKA data plane)
- TCAM (Ternary Content-addressable memory) resources: include high-speed memory resources, used to store Forwarding Information Bases (FIB), Access Control Lists (ACL), counters etc.
- Quality of Service (QoS) resources: include buffers, queues, policers etc. used for SLA (Service Level Agreement) mechanisms implementation.
Monolithic architectures: The resource utilization wall
With the monolithic chassis designed to accommodate various networking scenarios, they are implemented for one specific networking scenario. The set of resources is built as a superset to accommodate any scenario and is fixed, for any given platform.
When using the platform in a specific network scenario, the inherent inefficiency of the monolithic architecture means that the chassis goes under-utilized, for at least one of the resources mentioned previously.
This is because most networking functions require a different set of resources, which is usually a mixture of 1 or 2 intensely used resources and other, lesser used resources.
For instance, a core function (e.g., P router) requires intense bandwidth resources as it predominantly deals with packet forwarding and label switching (no requirements for routing, access lists and QoS). For this function, x86, TCAM and QoS resources will hardly be used.
On the other hand, an edge router, in the same network, will require more x86 and TCAM resources but not that many bandwidth resources, as it addresses lower capacity streams that only need specific forwarding, access lists etc.
Typical networking functions and services
The drawing below illustrates the resource requirements for a few typical networking functions and services, highlighting the difference in the mix of requirements that lead to under-utilization of resources for any networking scenario. This means that there are wasted resources in almost any monolithic router deployment in any specific network scenario. Those resources are a major part of the router cost-structure. The outcome is that operators pay for hardware resources they do not use, regardless of network growth trajectory.
n practice, this inefficiency starts from day one of launching the network, peaking upon the exhaustion of intensely used resources in a monolithic chassis. At that point, the chassis is blocked, even though there is still an abundance of unused resources (the lesser used resources in that specific networking scenario).
Inherent inefficiency drains ongoing network investments
As the network grows, the consumption of these favored resources also grows, further intensifying the abuse of unused resources. With more networking scenarios being addressed, this inefficiency eventually expands to all hardware resource types, significantly draining operator investments, while not yielding any benefit. In other words, wasted money.