Control Plane
The Control Plane defines a task's network control protocols: interfaces, LAG/MLAG, VxLAN on a CP interface, routing, MPLS/L2VPN, multicast, OAM, and BGP extensions. Use this section when the test requires not only user traffic but also a complete control plane around the device under test.
User-traffic encapsulation profiles (VLAN, VXLAN, GRE, IP-IP, and IPsec from the library) are described under Access Plane → Network Tunnels.
To configure the Control Plane, open the task, select the required agent, and click Edit Routing. The left panel displays a settings tree containing:
- General Settings — common parameters;
- Interface — the agent's network interface within the Control Plane;
- VxLAN — an overlay on the Control Plane interface (see also library VXLAN tunnels);
- Protocols: IS-IS, OSPFv2, OSPFv3, BGP, LDP, LLDP, BFD, RIP, PIM, IGMP/MLD Querier, EVPN, VPLS, VPWS, Pseudowire, MLDP, MPLS OAM, MPLS-TP, Link OAM, CFM (802.1ag on an interface), BGP-LS, BGP FlowSpec, and BGP L2VPN.
Control Plane protocols are configured as separate instances. Some protocols are then bound to the task's network interface, while others use an existing BGP or LDP session. If a task uses multiple agents or interfaces, make sure that the instance-id in the protocol settings matches the one in the interface binding. Peresvet ST uses this identifier to determine which protocol must operate on each side of the testbed.
For easier configuration, create the basic Control Plane elements first: the network interface and, when required, a BGP/LDP/IGP session. Then add the supplementary services. After the task starts, analyze protocol state on the Control Plane, Metrics, Events, and Logs tabs. These tabs show adjacencies, sessions, events, transmitted-message counters, and negotiation errors.
After making all changes, click + Save in the upper-right corner of the page.