Contents
Managing controllers
To display the table of controllers, go to the Infrastructure menu section, click the created data center, and select the Network resources tab. Information about controllers is displayed in the following columns of the table:
- Name is the name of the controller.
- Transport/service strategy is the being used.
- Controller nodes are IP addresses of controller nodes.
- Connection type is the type of connection of CPE devices to the controller:
- Unicast
- Multicast
- Cluster status is the status of the cluster of controller nodes:
- Up means the cluster is operating normally.
- DEGRADED means an error occurred during the operation of the cluster.
- Down means the cluster is not operational.
- Node statuses is the status of controller nodes:
- Connected (primary) means the node is connected to the controller and is the primary node in the cluster.
- Connected (single) means the node is connected to the controller and is the only node in the cluster.
- Connected (secondary) means the node is connected to the controller and is a secondary node in the cluster.
- Disconnected means the node is not connected to the controller.
- Not in cluster means the node is not added to a cluster.
- Unavailable means the node is not available.
- Unknown means the status of the node is unknown.
The actions you can perform with the table are described in the Managing solution component tables instructions.
Editing a controller
To edit a controller:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Edit next to the controller that you want to edit.
- This opens a window; in that window, in the Name field, enter the name of the controller. Range of values: 1 to 128 characters.
- If necessary, in the Description field, enter a brief description of the controller.
- In the Controller installation on <1>/<3>/<5> servers field, select the number of controller nodes.
- In the Connection type drop-down list, select the type of connection of CPE devices to the controller:
- Unicast
- Multicast
- Configure the controller node:
- In the Address (IP or hostname) field, enter the IP address or hostname of the controller node.
- In the gRPC port field, enter the gRPC port number of the controller node.
- In the JGroups port field, enter the jGroups port number of the controller node.
- If you want to make the controller node the primary node, select the Primary option.
You can configure multiple controller nodes.
- Click Save.
The controller is modified and updated in the table.
Page topReprovisioning a controller
During reprovisioning, controller properties are reset to their default values. This may help resolve errors.
To reprovision the controller:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Reprovision next to the controller that you want to reprovision.
- In the confirmation window, click Reprovision.
The controller is reprovisioned.
Page topRestoring a controller
You can download a file with controller settings and later use the file to restore the controller if necessary.
To restore a controller:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Download backup file next to the controller whose settings file you want to download.
A file with controller settings in YAML format is saved to your local device.
- Click Management → Restore next to the controller that you want to restore.
- This opens a window; in that window, specify the path to the downloaded file with controller settings.
- Click Restore.
The controller is restored with settings from the controller settings file.
Page topEnabling or disabling the maintenance mode on a controller
You can enable maintenance mode on the controller when performing maintenance work related to the SD-WAN network to minimize the impact of the controller on parts of the SD-WAN network that are not affected by the maintenance work. In maintenance mode, the controller monitors the status of the SD-WAN network, but does not take any action when the parameters of the SD-WAN network change. For example, in maintenance mode the controller does not rebuild links and paths, does not rewrite MAC addresses of service interfaces, or change transport services.
When you disable maintenance mode, the controller performs actions corresponding to the changes you made to the parameters of the SD-WAN network.
To enable or disable maintenance mode on the controller:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Do one of the following:
- If you want to enable maintenance mode on the controller, click Management → Enable maintenance next to it.
- If you want to disable maintenance mode on the controller, click Management → Disable maintenance next to it.
Maintenance mode is enabled or disabled on the controller.
Page topDeleting a controller
Deleted controllers cannot be restored.
To delete a controller:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Delete next to the controller that you want to delete.
- In the confirmation window, click Delete.
The controller is deleted and is no longer displayed in the table.
Page topManaging controller properties
Properties regulate the operation of the controller. Each property has a change method that determines whether the property value can be changed and when the change takes effect. The following change methods are available:
- Read-only means the property cannot be changed.
- Reload means that when a property is changed, the orchestrator commits the new value to the database of the controller. The new value takes effect after the controller is restarted.
A property value that is in the database, but has not yet taken effect is called a planning value. You can delete a planning value before restarting the controller to keep the current value.
- Runtime means the new value takes effect immediately when the property is modified.
Modifying properties may lead to unstable operation of the controller, so we recommend contacting Kaspersky Technical Support before managing properties.
You can view the table of all controller properties or only changeable controller properties:
- To display the table of all controller properties, navigate to the Infrastructure section, click the added data center, select the Network resources tab, and click Management → Properties next to the controller.
- To display the table of changeable properties of the controller, navigate to the Infrastructure section, click the added data center, select the Network resources tab, click Management → Properties next to the controller and select the Changeable properties tab.
Information about controller properties is displayed in the following columns of the table:
- Change method is the change method of the property.
- Property is the name of the property.
- Current value is the current value of the property.
- Planned value is the planning value of the property. This column is displayed only on the Changeable properties tab.
The actions you can perform with the table are described in the Managing solution component tables instructions.
Description of editable controller properties
Modifying properties may lead to unstable operation of the controller, so we recommend contacting Kaspersky Technical Support before managing properties.
Property |
Description |
|
Buffer size, in bytes, for messages coming in from switches on the controller. |
|
Buffer size, in bytes, for messages going out to switches on the controller. |
|
The starting port number in the range of switch ports. Ports with the next three consecutive numbers are added to the range. For example, if you enter |
|
Whether the TCP_NODELAY parameter is used for management sessions between switches and the controller. Possible values:
|
|
Whether the epoll system is used by the controller when managing switches. Possible values:
|
|
Time in milliseconds after which management sessions between the switches and the controller go idle in absence of read or write operations. The countdown starts anew whenever a read or write operation is performed. |
|
Time in milliseconds after which management sessions between the switches and the controller go idle in absence of read operations. The countdown starts anew whenever a read operation is performed. |
|
Time in milliseconds after which management sessions between the switches and the controller go idle in absence of write operations. The countdown starts anew whenever a write operation is performed. |
|
Netty threads preferentially run on separate CPU cores for separate switches. Possible values:
|
|
Number of Netty threads for handling new switch connections. |
|
Path to the PEM file of the root certificate that was used to sign the OpenFlow certificate. |
|
Path to the PEM file of the encryption certificate for OpenFlow traffic between the controller and switches. |
|
Path to the PEM file with the private key of the OpenFlow certificate. |
|
When the Netty buffer of the management session between switches and the controller contains this number of bytes, the queue is used to write to the session. |
|
When the Netty buffer of the management session between switches and the controller contains this number of bytes, the queue is no longer used to write to the session. This property is used when the number of bytes reaches the |
|
The throughput of the policer on the switches when sending traffic packets through the management session between the switches and the controller. Traffic packets are copied by interception flow rules. |
|
Time, in seconds, after which flow rules automatically created by the controller when processing the first intercepted traffic packet are deleted on the switches to block subsequent packets. The countdown starts anew every time the flow rule is applied. |
|
Bonding of parallel links between two switches. Possible values:
|
|
Whether the equal cost algorithm is used when bonding links. Possible values:
If you specify |
|
Maximum number of links in a bonded link. |
|
Type of the bonded link group. Possible values:
|
|
Whether the controller periodically sends LLDP packets only to enabled ports to detect links between switches. Possible values:
|
|
Whether the switches relay LLDP packets to the controller only from enabled ports when the controller attempts to discover links between the switches. Possible values:
|
|
Interval in milliseconds for the controller sending LLDP packets through the switch links. |
|
Interval in milliseconds for the receiving side of switch links to receive LLDP packets and forward the LLDP packets to the controller. If no LLDP packets arrive through the link within the specified time, the controller considers the link unavailable. |
|
Whether switches send notifications to the controller whenever flow rules that send traffic packets to the controller are deleted. Possible values:
|
|
Interval in milliseconds for checking the connection of switches to the controller. |
|
Time in milliseconds within which disconnected switches must reconnect to the controller. |
|
Number of the last virtual network interface (VNI) in the range of switch interfaces. |
|
Number of the first virtual network interface in the range of switch interfaces. |
|
Whether link Dampening is used. Possible values:
|
|
Maximum time in milliseconds for which access to the link can be restricted. When the specified time elapses, all Dampening counters are reset. |
|
The number by which Penalty is incremented when the link changes state. |
|
The Penalty value at which access to the link is restricted. |
|
Time in milliseconds within which the Penalty must reach the |
|
The IEEE 802.1Q TPID value that is specified as the inner tag for traffic packets with Q-in-Q traffic classification. |
|
The IEEE 802.1Q TPID value that is specified as the outer tag for traffic packets with Q-in-Q traffic classification. |
|
Getting statistics on switches. Statistics contain information about network devices to which the switch is connected, as well as the ports being used. Possible values:
|
|
Value of the 'cookie' field in the message for requesting statistics from the switches. Possible values:
This property must be specified if for |
|
ID of the LLDP packet queue on the switches. |
|
Maximum size of the push notification queue on the switches. If this size is exceeded, the first push notification in the queue is deleted. |
|
Duration in seconds for which IP addresses and ports of switches are blocked after an attempt to connect to the controller with an invalid TLS certificate. |
|
Whether IP addresses and ports of switches are blocked after an attempt to connect to the controller with an invalid TLS certificate. Possible values:
|
|
Time in seconds within which the switches must make the number of attempts (specified in the |
|
The number of attempts of switches to connect to the controller with an invalid TLS certificate, after which the IP addresses and ports of the switches are blocked. |
|
This property is no longer used. |
|
This property is no longer used. |
|
Whether flow rules send traffic packets to the controller. Possible values:
|
|
This property is no longer used. |
|
Interval in milliseconds for checking the latency between the controller and the switches. |
|
Whether latency is checked between the controller and switches. Possible values:
|
|
Number of leading traffic packets on the switches, which is not counted towards statistics. |
|
Number of trailing traffic packets on the switches, which is not counted towards statistics. |
|
Size, in bytes, of chunks of serialized OpenFlow messages that the controller sends to the switches. |
|
Maximum number of blocks of serialized OpenFlow messages in the controller queue. |
|
This property is no longer used. |
|
This property is no longer used. |
|
This property is no longer used. |
|
This property is no longer used. |
|
Maximum number of paths in a segment. |
|
Maximum number of SPF paths for automatic balancing. |
|
Action that switches perform with traffic packets that are not in any of the OpenFlow tables. Possible values:
|
|
Whether Connectivity Fault Management (CFM) is used on links. Possible values:
|
|
Whether controller debug routines are used involving the gRPC protocol. Possible values:
|
|
Establishing links between VTEPs. Possible values:
|
|
Using all links as a last resort when routing traffic, regardless of the link quality. Possible values:
|
|
Link discovery by groups. Possible values:
|
|
Traffic encryption on links. Possible values:
|
|
Interval in minutes for updating the decryption key on links. |
|
Monitoring of errors on links. Possible values:
|
|
Threshold value of the number of errors per second on links. |
|
Interval in seconds for measuring the number of errors on links and link utilization. |
|
Whether Forward Error Correction (FEC) is used on links. Possible values:
|
|
Ratio of original traffic packets to additional packets with redundant code. Enter a value in the |
|
The maximum time, in milliseconds, during which a traffic packet can stay in the queue for FEC to apply. |
|
Monitoring of jitter on links. Possible values:
|
|
Time threshold of jitter on links, in milliseconds. |
|
Monitoring of latency on links. Possible values:
|
|
Latency threshold on links, in milliseconds. |
|
Interval in seconds for comparing the received monitoring figures with the specified thresholds of latency, jitter, and packet loss on links. |
|
Monitoring of latency, jitter, and traffic packet loss on links. Possible values:
You can specify the monitoring protocol using the |
|
Size in bytes of the additional buffer in each LLDP packet for latency, jitter, and packet loss monitoring figures. This property must be specified if for |
|
Protocol for monitoring of latency, jitter, and traffic packet loss on links. Possible values:
|
|
The multiplier that the controller applies to delay, jitter, and packet loss monitoring figures. This property must be specified if for |
|
Monitoring of traffic packet loss on links. Possible values:
|
|
Threshold value of the traffic packet loss percentage on links. |
|
Interval in seconds for automatic detection of the MTU figure on links. |
|
How long the controller waits for a PMTUD LLDP packet, in milliseconds. If the controller does not receive a PMTUD LLDP packet within this time, the controller concludes that a packet of this size cannot be transmitted over the link. |
|
Interval in seconds for monitoring of link thresholds. |
|
Threshold monitoring on links. Possible values:
|
|
Number of successful checks in a row for a link to be unblocked. A check is performed once per second. |
|
Monitoring of link utilization (bandwidth usage). Possible values:
|
|
Threshold value of link utilization as a percentage of the bandwidth of service interfaces. |
|
Concurrent sending of LLDP packets by the controller for link discovery. Possible values:
|
|
Minimum number of streams for concurrent sending of LLDP packets by the controller. This property must be specified if for |
|
Maximum number of streams for concurrent sending of LLDP packets by the controller. This property must be specified if for |
|
Maximum queue size when the controller is sending LLDP packets concurrently. This property must be specified if for |
|
The reserve service interface becomes reserve again if the old service interface becomes operational again. Possible values:
|
|
Accumulation of physical operations on the controller, such as connecting a switch or a port, to perform the operations when the specified time elapses. Possible values:
You can specify the time using the |
|
Time in seconds after which the physical operations accumulated on the controller are carried out. This property must be specified if for |
|
Time in seconds after which the physical operations accumulated on the controller are carried out. The countdown starts anew whenever a physical operation appears. This property can be specified if for |
|
System property. Editing this property may render the controller inoperable. |
|
System property. Editing this property may render the controller inoperable. |
Editing a controller property
Changes you make to the controller properties with the Runtime change method take effect immediately. Changes you make to controller properties with the Reload change method take effect after the controller is restarted.
To change a controller property:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Properties next to the controller for which you want to change a property.
The controller properties page is displayed. By default, the All properties tab is selected, which displays a table of all controller properties.
- Select the Changeable properties tab.
A table of editable properties of the controller is displayed.
- Click Management → Edit next to the controller property that you want to edit.
- This opens a window; in that window, in the Planned value field, enter the new value of the controller property.
- Click Save.
The new value of a property with the Runtime method is displayed in the Current value column. The new value of a property with the Reload method is displayed in the Planned value column.
Deleting planning values of controller properties
You can delete a planning value to undo a controller property change. This action is applicable only to properties that have the Reload method.
Deleted planning values of controller properties cannot be restored.
To delete planning values of controller properties:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Properties next to the controller for which you want to delete planning values of properties.
The controller properties page is displayed. By default, the All properties tab is selected, which displays a table of all controller properties.
- Select the Changeable properties tab.
A table of editable properties of the controller is displayed.
- Delete the planning values of controller properties in one of the following ways:
- If you want to delete the planning value of an individual property of the controller, click Management → Delete planned value next to that property.
- If you want to delete planning values of all controller properties, in the upper part of the table, click the settings icon
→ Delete all planned values.
- In the confirmation window, click Delete.
The planning values of controller properties are deleted.
Page topResetting controller properties to default values
To reset controller properties to default values:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Properties next to the controller whose properties you want to reset to default values.
The controller properties page is displayed. By default, the All properties tab is selected, which displays a table of all controller properties.
- Select the Changeable properties tab.
A table of editable properties of the controller is displayed.
- Reset the controller properties in one of the following ways:
- If you want to reset an individual property of the controller to its default value, click Management → Reset property next to that property.
- If you want to reset all controller properties to their default values, click the settings icon in the upper part of the table
→ Reset all properties.
- In the confirmation window, click Reset.
The controller properties are reset to their default values.
Page topViewing information about controller nodes
To view information about controller nodes:
- In the menu, go to the Infrastructure section.
This opens the resource management page. By default, the Network resources tab is selected, which displays the table of controllers.
- Click Management → Configuration menu next to the controller for which you want to view information about nodes.
This opens the controller configuration menu. By default, you are taken to the Controller nodes section, which displays a table of controller nodes. Information about controller nodes is displayed in the following columns of the table:
- Address is the IP address of the controller node.
- Status is the status of the controller node:
- Connected (primary) means the node is connected to the controller and is the primary node in the cluster.
- Connected (single) means the node is connected to the controller and is the only node in the cluster.
- Connected (secondary) means the node is connected to the controller and is a secondary node in the cluster.
- Disconnected means the node is not connected to the controller.
- Not in cluster means the node is not added to a cluster.
- Unavailable means the node is not available.
- Unknown means the status of the node is unknown.
- gRPC port is the number of the gRPC port of the controller node.
- JGroups port is the JGroups port number of the controller node.
- Version is the version of the controller node software.
The actions that you can perform with the table are described in the Managing solution component tables instructions.
- If you want to view statistics for a controller node, click Management →Statistics next to the node.
- If you want to view the properties of a controller node, click Management → Node properties next to the node.