Ethernet Service Troubleshooting Troubleshooting
Asymmetric Ethernet
Traffic
In case of two different Actelis system
models used in any topology, you may
have asymmetric Ethernet traffic, due to
different Egress (Tx) or Ingress (Rx) Rate
limit configuration on ports of adjacent
Actelis systems (via HSL or Ethernet).
To resolve the problem configure
the systems equally
Forwarding By L2 Priority
works improperly
Original traffic L2 prioritization can be
enforced by Port Priority or higher layers
priority configuration (i.e. configured other
than by L2 priority) or be affected by
improper configuration of L2 classification
table.
Set Port Priority to By L2 Priority
to classify packets according to
their VLAN tag (802.1p priority
field) and configure L2
classification tables properly.
Original traffic L2 priority
is changed
In those VLAN configurations, where
Ethernet port is defined as a stacked port
(on Customer LAN Adjacent Actelis
system), additional external VLAN tag is
added to the original frame, forwarded in
upstream to CO. New VLAN tag priority is
assigned according with result of Priority-
to-Traffic Class classification, applied on
the port.
Original priority is translated to Traffic
Class using Classification table rules
(configurable) and then new priority is
applied according with resulted Traffic
Class (non-configurable). The following
Traffic Class-to-Priority rules are applied:
Highest traffic class - Priority value 6-7,
High - 4-5, Medium - 2-3, Low - 0-1.
There are either forcefully applied
per port traffic class
(Highest/High/Medium/Low), or
"By L2 priority"/"By L3 Priority"
Priority-to-Traffic Class
classification. Use "By L2
Priority" classification to use
original traffic VLAN tag for
traffic classification. Also check
that L2 Priority classification
table (which consist of Priority-to-
Traffic Class rules) is configured
properly.
Forwarding By L3 Priority
works improperly
If original L3 traffic is not pure IP V4/V6
over Ethernet (VLAN tagged or untagged)
but is additionally encapsulated (L2TP,
PPPoE, etc.), then improper L3
classification is applied. Also, L3
prioritization can be enforced by Port
Priority configuration (is configured as
other than by L3 priority) or be affected by
improper configuration of L3 classification
table.
If original traffic is not pure IP
V4/V6 over Ethernet (VLAN
tagged or untagged) then
reconfigure Ethernet Ports priority
(do not use L3 priority).
If original traffic is pure IP V4/V6
then set Port Priority to "By L3
Priority" to classify packets
according to ToS/DSCP field
and/or configure L3 classification
tables properly.
To Next Page