EasyManua.ls Logo

Ericsson EFN324 - Page 50

Ericsson EFN324
176 pages
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...
IndexIndex
connect vlan 130 ethernet_port 1 ingress tags 700 flow_selector none egress tag 700 p_tag 5
connect vlan 130 ethernet_port 25 ingress tags 700 flow_selector none egress tag 700 p_tag 5
set connection_flow vlan 130 ethernet_port 1, 25 ingress flow 1 priority high reliability high
With this configuration, the traffic from the business users, from VLAN 500 is
handled as:
frames tagged with p-bit 0 or 1 will be headed to flow 1; the marking in
QoS-Flow_1 is defined Transparent, frames will exit with the original p-
tag, i.e. p-bit = 0 or p-bit = 1
frames tagged with p-bit 2 or 3 will be headed to flow 2; the marking in
QoS-Flow_2 is defined Transparent, frames will exit with the original p-
tag, i.e. p-bit = 2 or p-bit = 3
frames tagged with p-bit 4, 5 will be headed to flow 3; the marking in
QoS-Flow_3 is defined marking 4, so frames will exit with the modified
p-bit = 4
frames tagged with p-bit 6, 7 will be headed to flow 4; the marking in
QoS-Flow_4 is defined marking 6, so frames will exit with the modified
p-bit = 6
For residential users, all traffic on VLAN 600 shall be remarked with p-bit = 0,
while all traffic on VLAN 700 shall be remarked with p-bit = 5.
5.6.2 Examples 2: trusted and untrusted users configuration
This example describes a 3-play configuration where traffic on the user side is
single tagged and on the network side is double tagged; in the upstream
direction the added tag will inherit the p-bit tag from the user’s tag.
Global Setting:
set connection_flow node_level flow 1 priority low reliability low marking transparent
set connection_flow node_level flow 2 priority low reliability low marking transparent