The IRP platform has a few interconnected components (see Figure IRP Components), which work together to improve routing best path selection and eliminate various network issues.
To inject improvements into the network, the platform needs to ‘tell’ routers exactly what needs to be changed in the routing table.
A short description of each of the components is given below.
The IRP BGP daemon announces the improved prefix with an updated next hop so that traffic can start flowing via the new path.
Bmpserver receives BMP monitoring sessions to provide route data to IRP components.
Core is the most important part of the system. It runs all the logical operations and interconnects all the components. It handles the performance and cost improvements. It processes, stores and exports data.
Collector Irpflowd & Irpspand are receiving, analyzing and processing all traffic passing the network. They have two ways to gather data about the network: by mirroring network traffic or by using NetFlow/sFlow.
Explorer runs all the probes and checks the metrics specified by the platform policies, such as packet loss and latency. This information is sent back to the Core.
Globalcc communicates between different IRP instances to maintain commit levels globally.
Irpdetectd collects various statistics for DDOS detection and mitigation feature.
Irppushd is responsible for forwarding events to configured notification channels.
Irpapid is used to serve requests from GMI user interfaces and provides API to external tools.
Frontend represents a web interface with a comprehensive set of reports, graphs and diagnostic information that can reflect the current and historical state of the network, as well as the benefits of IRP network optimization.
