Содержание

Handling traffic by VLAN

The vlan group data has been migrated from UDR to SDR. Global rules for vlan drop, vlan pass, vlan hide, vlan permit, previously set by the legacy CLI command vlan group, have been converted and migrated from UDR to SDR with removal from UDR.
  1. Drop traffic without analysis from a specific VLAN:
    fdpi_cli vlan group <id> drop
  2. Dropping traffic with preliminary analysis, but without transferring it to Netflow statistics from a specific VLAN (Used to deal with asymmetric traffic when a site receives a double of traffic from another site. It is necessary to analyze and drop the traffic so that it is not included in the statistics):
    fdpi_cli vlan group <id> hide
  3. Passing traffic without any analysis from a specific VLAN:
    fdpi_cli vlan group <id> pass
  4. Display existing settings in the UDR:
    fdpi_cli vlan group 0 show all

    Example output of the command:

    fdpi_cli vlan group 0 show all
    <proto> <vlan> <service-name> <policy> <delay>
    all 4000 *  hide 0
    all 4002 *  hide 0
    all 4003 *  hide 0

    In this example, you can see that all protocols belonging to VLAN 4000, 4002, 4003 are affected by hide, that is, traffic from one site is duplicated to another site.

  5. Output all properties for a group with a specific id:
    fdpi_cli vlan group <id> show all

    Here id is the number of the VLAN for which you want to output Service-Name information.

For more information, seeConfiguring Service-Name for VLAN

VLAN Rule

VLAN Rule allows flexible management of network traffic at the VLAN and QinQ level, assigning specific packet processing policies for individual VLANs, VLAN ranges, or QinQ tunnels.

Rule Types

The following rule types are supported:

Syntax for Describing VLAN/QinQ Ranges

Rules apply to ranges specified in the following format:

Rules for regular VLANs (67) and QinQ (67.*) are independent and do not intersect.

Rule Priority

If the ranges of multiple rules intersect, the system determines the final action based on the principle "from general to specific":

  1. Rules with the broadest ranges (e.g., 1-4095 or any.any) are applied first.
  2. Rules with narrower ranges (e.g., 100-200) can then override the action set by general rules.

Example:
The following rules will create a policy: "Disable DHCP for all VLANs in the range 300-700, but enable it for VLAN 645 and the range 430-439".

vlan rule add 300-700 dhcp disable
vlan rule add 645 dhcp enable
vlan rule add 430-439 dhcp enable

Management

When using * in CLI for QinQ ranges, it is recommended to enclose the expression in quotes (e.g., '*.68' ) or use the keyword any (e.g., any.68) to avoid incorrect interpretation of the * character by the bash shell.

Change Application Specifics: Rule changes made by the add, modify, or delete commands are saved to SDR and automatically applied by the system 5 minutes after the last modification. The vlan rule apply command allows forcing their application, but no more than once per minute.