Per-Tier POP Network Architecture
The physical blueprint underneath every Parinita POP — same image, same playbook, 101 sites.
Per-Tier POP Architecture is the standardized T1–T4 design that every Parinita POP follows. Same Cisco 8000 BGP edge, same Arista Fabric 2 east-west, same Palo Alto PA-5580/5560 firewalls, same ConnectX-7 NICs — so software above the network plane never has to care which tier it's running on.
What it does
-
Four standardized tiers
T1 (32 POPs, 129K seats, 400G), T2 (29 POPs, 79K seats, 300G), T3 (19 POPs, 55K seats, 200G), T4 (21 POPs, 54K seats, 100G). Four templates, one image, one playbook.
-
Cisco 8000 BGP edge
Every POP fronts the public internet through Cisco 8000 routers speaking standard BGP — the only place BGP runs inside Parinita's infrastructure.
-
Arista Fabric 2 east-west
Lossless RoCEv2/DCQCN across the entire POP fabric for GPU↔GPU and storage traffic. Same Arista CloudVision management at every site.
-
PA-5580/5560 firewalls
367 firewalls across 101 POPs. Active/Active PA-5580 in HA pair at every T1, Active/Passive PA-5560 at T2–T4. Panorama M-700 manages all 367 centrally.
-
ConnectX-7 universally
Same NIC at every node on every plane — line-rate hardware crypto offload, eBPF/XDP for Crucible enforcement, RoCEv2 for storage and GPU traffic.
How it works
The Per-Tier architecture is what makes Opera’s “same software stack everywhere” claim tractable. Instrument doesn’t need to know whether it’s running on a T1 or T4 POP; Maestro doesn’t need per-site cluster profiles for network gear; Crucible can rely on the same NIC capabilities at every node. Because the physical layer is standardized, the software stack can assume one set of capabilities.
A T1 POP has 32 sites supporting 129K seats with 400G uplinks and HA PA-5580 firewalls. T4 POPs are leaner — 21 sites, 54K seats, 100G, Active/Passive PA-5560 — but the same management plane (Panorama M-700), the same fabric controller (Arista CloudVision / Cisco Crosswork), the same NICs. The only thing that changes between tiers is scale.
When to use it
This isn’t really a product you “use” — it’s the substrate every other Parinita product is designed against. It matters because it’s what makes the rest of the stack deterministic: if you’re building on Parinita, the network beneath you is the same in Atlanta as in Anchorage.
What it isn’t
A consumable product. It’s a published reference architecture for the 101-POP build-out — useful for understanding why the software stack behaves consistently across sites, not something you provision separately.
Related products
Part of the Parinita AI Edge
Bring Per-Tier POP Network Architecture into your stack.
Every Parinita product runs on the same 9-plane fabric across 101 edge POPs. Talk to us about a pilot, or see how the pieces fit together.