Home » LucidView knowledge base » Saturation Manager

What is the Saturation Manager?

LucidView’s Saturation Manager is a powerful cloud based utility which allows you to control the bandwidth utilized by certain categories. You have the ability to designate custom entries such as URLs or IP addresses and ranges.

This Module is particularly helpful when managing streaming services which as we know, will ramp up to full resolution and impact more latency sensitive applications.

The Saturation Management categories offered are powered by LucidView’s Cloud Artificial Intelligence platforms.

Depending on your configuration of the Saturation Manager, lists will be pushed by the LucidView Cloud to your Enforcer profile, after which mangle rules and queue trees will be utilized to deliver the shaping experience.

Please note that the configuration on RouterOS to effectively utilize the Saturation Manager requires the relevant respective knowledge.

We recommend having RouterOS knowledge in the following areas.

  • L2TP Client configuration
  • Packet mangling, packet and connection tracking.
  • Queue trees
  • Multi gateway routing / multiple routing tables based on routing marks.
  • File management on RouterOS

Please see this use case as an example of a custom shape list.

Configuration

The Saturation Management Module is accessible from the Enforcer Profile, when the module has been enabled for that profile.

Log into the Enforcer profile, and find the section labelled “Saturation Manager” available from the home screen. Alternatively, you may access the Saturation Manager from any time, by using the drop down menu from the right side of the Navigation Bar.

From the configuration menu of the Saturation Manager, please select the categories of content that you would like to be able to shape. Additionally, you may enter URL, or IP addresses/ranges to also be pushed to your Enforcer Profile.

Please note that there may be up to a 10 minute delay before your shaping lists are updated by the LVCloud.

Please configure the mangle rules so that the correct traffic may be managed by the queue trees on the MikroTik itself. It is there that you may start to configure bandwidth allowances for each list.