EasyManua.ls Logo

Actelis Networks ML700 - Page 229

Actelis Networks ML700
485 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Identification Rules Definition Ethernet Service Configuration
ML700 User Manual 10-19
Table 42: Edit Advanced Rule Dialog Areas
Rule
Function area
human-readable description and required behavior information of the current rule.
The following fields are provided:
AID - Rule AID
Description - Rule description as appears in the Rules pane. Can be modified.
Service - service to which the Rule belongs (from the pool of predefined service IDs).
Multiple Rules can belong to the same Service. In this case BW Ingress and Shaper
definition are applied on a sum of traffic identified by these rules.
For Rules with Drop behavior - set Service ID to NONE.
Behavior - how to handle frames that match this rule. Values = Pass or Drop (not
supported on all models)
COS bits marking:
Class to COS Marking - COS bits of the frame will be set according to the Queue
where this frame was assigned (HHH,…LLL). Classification Result (HHH , …,LLL)
mapping to COS bits (0 … 7) is configurable per unit.
CoS Propagation - no additional marking applied. Which means that Original frame
priority is kept - when tagged original frame pass through a port with Tagged
membership defined on it). Or Port priority is assigned to the original frame - when
untagged frame pass through a port with Untagged membership defined on it). Or
Original frame Priority is copied to outer tag from inner tag when frame pass
through a port with Stacking membership defined.
None -sets the PBit according to the queue value (1,3,5,7).
Traffic
template
(toward HSL
wire) area
pattern to recognize the traffic. Template defines the offset (relative to the frame 1-st
bit start) where the traffic should be validated with the parameter values for L2, L3,
L4 protocols.
In this area, rule pattern is defined according to templates. These should be inspected
for match. Deeper frame inspection requires more specific templates to be defined.
Each rule can use its own template. For example, in case of mix traffic (expected
either single or dual tagged on the same port) 2 rules should be prepared using
different templates to catch all required traffic.
Layer 2 Template values - Untagged, Single tag, Double tag or unknown.
Layer 3 Template values - Unknown, IpV4, IPV6
Encapsulation (between L2 and L3) values - Unknown, None, PPPoE

Table of Contents