Date: Fri, 29 Mar 2024 05:37:30 +0500 (YEKT) Message-ID: <208900302.31636.1711672650195@jira> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_31635_903694089.1711672650194" ------=_Part_31635_903694089.1711672650194 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Successfully pass the free certification exam at IW Academy and become a= n Infinet Certified Engineer.
Before you begin to configure the VLA= N settings on the switch groups please refer to the information in the = following sections:
Let's consider the situation at which the subscriber terminal connects t= o the base station via a trunk mode:
The main issue of such situation is in the subscriber terminal&nbs= p;switch groups #1001 and 1002 setting, as it is necessary to s= pecify the rules by which the traffic would be filtered and distributed bet= ween these two groups.
How to do this please refer to the procedure below.
1) In order to separate VLAN manag= ement from the rest virtual networks set the filter on both devices that wo= uld receive traffic from VLAN-tag 10.
switch group 1 = vlan 10=20
2) Configure the switch group#2 on the base station
switch group 2 = add eth0 rf5.0 switch group 2 start=20
switch gr= oup 2 trunk on=20
switch list LST= numrange add 2-9 11-4094=20
all VLANs except 10.
switch group 2 = vlan LST=20
3) Configure the switch groups #1001 and 1002 on the subscriber terminal=
switch group 10= 01 add eth0 rf5.0 switch group 1001 start switch group 1002 add eth0 rf5.0 switch group 1002 start=20
switch group 10= 01 in-trunk 2 on switch group 1002 in-trunk 2 on=20
At this stage we got two identical groups. In order to equally distribut= e the traffic between them rules must be added. As we deal with VLAN-tags, let's review two situations:
1) Traffic egresses and ingresses to the subscriber terminal with VLAN-tag
In this case it is enough to specify the VL= AN for the switch group
switch group 10= 01 vlan 1001 switch group 1002 vlan 1002=20
CAUTION
This situation intends the availability of the configured tag on t= he end device or an additional switch that assigns the required VLAN-tag. Otherwise, all traffic will be= dropped since none of the switch groups will not receive it.
2) Traffic egresses from the subscriber terminal with VLAN-tag through the radio interface "rf5.0"
This situation does not require additional configuration on the end devi= ces or the availability of the tagging switch. The required VLAN-tag would be assigned to the traffic that have been = passing through the subscriber terminal from "eth0" interface to t= he radio interface "rf5.0". The tag should be reset in case of the= traffic passing in reversed order. However, despite the convenience = of this situation, the rules should be assigned to the switch groups under = which they will receive the traffic. As the filtering on the switch g= roup over VLAN number &nb= sp;is not applicable, other methods should be used for the traffic distribu= tion (please review the section "swi= tch command").
The following is an example of the traffic distribution:
switch group 10= 01 add eth0:0 rf5.0:1001 switch group 1002 add eth0:0 rf5.0:1002=20
In this case the egress and ingress traffic will reset VLAN-tag in "eth0" and assign it in "rf5.0".
1) by the used interfaces
In case your device (R5000) has two different Ethernet-interfaces, each = of them can be configured to a separate group
switch group 10= 01 add eth0:0 rf5.0:1001 switch group 1002 add eth1:0 rf5.0:1002=20
2) based on a network
For this the list should be created and assigned to the required group= p>
switch list IPN= ET match add =E2=80=98net 192.168.1.0/24=E2=80=99 switch group 1001 rule 1 match IPNET permit=20
3) by MAC= -address of the transmitter and receiver
switch list MAC= NET mac add 00:01:02:03:04:05 00:11:12:13:14:15 switch group 1001 rule 2 src MACNET permit switch group 1001 rule 2 dst MACNET permit=20
4) by the protocol number of the Ethernet= level
switch list PRO= TONET proto add 23 switch group 1001 rule 3 proto PROTONET=20
NOTE
The system provides the flexible configuration of the filters that= allows to combine them with each other to get the desired result.
NOTE
If it would satisfy your needs it is enough to configure the rules = just on the one switch group. In case the packets are not in accordance wit= h the rules of one switch group they will be sent via another, but it is ne= cessary to consider the priority of the switch groups.