Identification Rules Definition Ethernet Service Configuration
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.
For a newly defined basic rule, the template is pre-defined in advance as Layer 2
Template – Single Tag and Layer 3 Template – IPv4.
If traffic ingressing the ML device differs from this template (i.e. is double tagged,
IPv6, or PPPoE encapsulated), use the Advanced Rule dialog.
ML700 has some rules pre-defined with hard-coded template (as in the example
above, for CESoETH).
Traffic Template for such rules will appear grayed-out and cannot be changed in any
(basic or advanced) dialog.
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
Rules Filters
(Match
Criteria) area
Defines the content of the rule. A frame is identified as belonging to the rule if the
frame and rule content matches in all specified fields. (Correct offset of fields is
determined using the template of the rule).
Rx Port - port to which this rule is applied. Only service Ethernet ports are
supported (HSL, COLAN and LAG port are not supported).
VID From and To - Allows to fill in VLAN ID to search for match. Either explicit
values or range (using BINARY mask) can be searched for match. See
Calculating the Range Covered by a Rule (on page 10-21).
By Layer 2 (COS) From and To - Allows to fill in COS to search for match. Either
explicit values or range (using BINARY mask) can be searched for match. See
Calculating the Range Covered by a Rule (on page 10-21).
By Layer 3 (DSCP/TOS) From and To - Allows to fill in Tag Type (Eth.Type) to
search for match. Either explicit values or range (using BINARY mask) can be
searched for match. See Calculating the Range Covered by a Rule (on page
10-21).
NOTE: If the FROM and TO fields display ****, you may view the configuration by
using TL1 commands, or perform reset via the MAV GUI dialog.