Overview
CPE’s created using the Flock Internet Routing Engine (FIRE) require very little resources to run. FIRE based CPE’s have been deployed in production for many years on various low end hardware platforms (i.e. Lanner® 5530, Dell® XR5610), in KVM virtual machines and in containers hosted in the public cloud.
- Low end deployment: FIRE can be compiled to run on various light weight targets including ARMv6, ARMv7, ARMv8, RISC-V, Virtual Machines, Containers and Linux Network Namespaces.
- Low CPU utilization: A FIRE based CPE will only use CPU cores assigned by the customer. With access to only a couple of CPU cores FIRE will automatically disable its internal thread pool. In a converged network a FIRE based CPE will use less than 0.1% of a single cpu core.
- Low Memory footprint. A FIRE based CPE with a few hundred routes, running eBGP to a couple of PE’s and OSPF to the customers network will use less than 5MB of RAM. RAM usage will grow slowly and linearly as more routes are learnt.
Other products built using FIRE
All products →RS→
BGP Route Server
Create BGP Route Servers with fast convergence and unmatched security
RR→
BGP Route Reflector
Create BGP RR's with unparalleled scalability and stability
HOST→
Host Application Routing
Allow each host to select a network path per application
MON→
Network Monitoring Node
Monitor in real time by installing a passive network node
P→
P Router
Create uniform core provider routers
PCE→
Path Computation Element
Create PCE controllers with five-nines uptime
PE→
PE Router
Create feature rich core provider edge routers
Build your CPE Router using FIRE.
The source code is available to license. Run it on Linux or SONiC.