SourceX SDN/NFV Controller components:
Database – a database for storing inventory information on client equipment, as well as information on the configuration of services.
Cfg Store – a repository for periodically collecting configuration from devices, as well as maintaining information on changing the configuration of devices.
Web UI – web interface for administrators and network engineers, allowing you to perform the following functions:
- register new CPEs in the system;
- configure the WAN configuration of the CPE interface;
- configure the configuration of the client network.
REST API – the program interface (northbound interface) for interaction with information systems of the Customer.
BPM Engine – A module that is required when configuring complex services that require reconfiguration of multiple devices.
Message Queuing – is a component used to communicate between controller modules.
SSH Adapter – Used to send commands to the CPE and to obtain the current CPE configuration.
TR-069 Engine – the configuration module of the WAN interface CPE to specification TR-069.
HTTPS Server – is a module that allows the CPE to interact with the controller to run scripts that are run on the CPE and receive data (for example, certificates, configurations, etc.).
- Maintaining domains, with reference to clients and types of services.
- Maintain a list of devices installed at the clients in the context of the domain.
- Maintain the WAN interface configuration of each device (for example, DHCP, Static, L2TP, PPTP, etc.).
- Maintaining the service settings for each device (tuning the tunnel, Encryption, etc.).
- Setting up the general hardware configuration (access parameters, certificates, updating scripts, etc.).
- Activating the configuration of services (tunnels, routing) on client Devices.
- Storage of equipment configuration and provision of information on Change the configuration.
- Display information about the availability of the final equipment.
- Display information about the actual configuration of the client
- Rapid deployment of corporate WAN networks using Existing network infrastructure.
- Lack of expensive or “hidden” licenses.
- Minimum costs both at the initial stage, and on the subsequent.
- Use of inexpensive client equipment for small offices
(For example, Mikrotik RB750Gr3), as well as the possibility of using more Productive equipment for large offices (For example, Mikrotik Cloud Core Router CCR1009).
- There is no binding of the System to the equipment manufacturer, i.e. The system can in the future be integrated with other models of equipment.
- Clients of the company can build corporate WAN networks between offices, Connected to different Internet providers.
- It is possible to use the connection of remote offices using NAT broadcast.