Ericsson EFN324, User Manual, Page: 28 / 176

IndexIndex
The flow selector parameter used in the configuration of the connect command
discriminate which flow description is applied.
Four cases are available:
Flow 1 – flow id values p­bits 0, 1 or dscp 0­15
Flow 2 – flow id values p­bits 2, 3 or dscp 16­31
Flow 3 – flow id values p­bits 4, 5 or dscp 32­47
Flow 4 – flow id values p­bits 6, 7 or dscp 48­63
Flow 1 is applied in case the flow selector in the connect vlan command is defined
as p­bits; in this case all frames belonging to the configured vlan and tagged
with p­bit 0 or 1 will experience the configuration defined for Flow 1. Flow 1 is
as well applied in case the
flow selector in the connect vlan command is defined as
dscp; in this case all frames belonging to the configured vlan and tagged with
a dscp between 0 to 15 will experience the configuration defined for Flow 1.
When the
flow selector
in the
connect vlan
command is defined as p­bits; in this
case all frames belonging to the configured vlan and tagged with any p­bit 0­7
will go through the corresponding flows 1­4. There is no configuration possible
that can be specified to discard frames with certain p_bits. The parameter
flows in the connect vlan command does not have any significance in choosing
the flows but it is only used as a validation criteria for defining default flow. This
is because default flow in connect vlan command should be one of the flows
configured.
Same is the case with flow selector as dscp.
Example:
connect vlan 10 ethernet_port 10 ingress flow 1­2 flow_selector p­bits
default_flow 2
connect vlan 10 ethernet_port 10 ingress flow 1­3 flow_selector p­bits
default_flow 2
connect vlan 10 ethernet_port 10 ingress flow 1­4 flow_selector p­bits
default_flow 2
All the above commands do not have any significance for flows parameter. All
the above commands will result in the same behavior of the traffic handling.
connect vlan 10 ethernet_port 10 ingress flow 1­2 flow_selector p­bits
default_flow 4