Case 2. Applying Policies to Channels, Session Policing for Channels and Subscribers [Документация VAS Experts]

Case 2. Applying Policies to Channels, Session Policing for Channels and Subscribers

This interface provides a full list of channels created to date, allowing:

  1. Viewing the current status of all types of policies on the channel.
  2. Adding or removing policies for an individual channel or multiple channels in group editing mode.
  3. Enabling or disabling a channel or group of channels.

Applying Session Policing to Multiple Channels

This interface displays the current status of session policing on channels, allowing new protocols to be added for policing or existing policies to be edited.

Step 1. Checking for Existing Session Policing

In this table you can see that session policing is disabled on Default_Channel.
If session polyscing is enabled, you can view the current composition of policies by pressing the edit button on the channel.

Step 2. Adding a New Policy

For example, limiting bittorrent to 1 Mbps.

  1. Select several channels for the policy by ticking the checkbox.
  2. Go to the TOOLS section, then “Set Per-Session Policing”
  3. Check for existing session polices already configured on all selected channels by clicking “Upload Common Policings” (optional). This option allows checking for similar or previous policies. Only policies that match fully for the selected channels will be displayed. If such policies exist, they can be enabled/disabled or edited directly from this list.
  4. If, after all checks, the new policy is still relevant, add it in the interface.

    After pressing “Add,” this new policy will appear in all selected channels from Step 1. If a different policy existed for this protocol on any of these channels, it will be overridden (in this case, bittorrent will be limited to 1 Mbps everywhere).
Session policing can be carried out by protocol, protocol group, or custom protocol group.
Creating a custom protocol group is described in Case 7. Custom Protocol Groups.

Step 3. Disabling or Deleting Policing on Channels

Policies can be disabled similarly to adding and enabling them. The simplest way is to do this from the list available via the “Upload Common Policies” button.

It is also possible to disable or delete all policies on the selected channels:

Global WEB FILTER Blacklist

The current status (on/off) is visible, and it can be changed for the channel from this interface. Group editing is unavailable.

WEB FILTER Exceptions List

The current status (on/off) is visible, and it can be changed for the channel from this interface. Group editing is unavailable.

IPv6 Blocking

The current status (on/off) is visible, and it can be changed for the channel from this interface. Group editing is unavailable.

Class-based Policing

The current status (presence of policing + on/off) is visible, and it can be edited and enabled for the channel from this interface. Group editing is unavailable.

DNS Response Substitution

The current status (on/off) is visible, and it can be edited and enabled for the channel from this interface. Group editing is unavailable.

Additional Information

In addition to main functions, the interface displays:

  • The number of IP prefixes comprising the channel.
  • The presence and number of WEB filter rules applied to the channel, with a hyperlink for editing these rules.
  • The option to edit the channel.
  • The option to delete the channel.