
The SAF FreeMile Series Full Outdoor Unit Technical Description and Configuration Guide • Rev. 1.3
© SAF Tehnika JSC 2012
48
VLAN
A
is
the
Access
type
VLAN
with
ports
1
&
2
membership
with
removing
and
inserting
VLAN
tags
while
packet
is
being
transmitted
to
ports
1
and
2,
respectively.
VLAN
B
is
the
Management
type
VLAN
with
ports
2
&
3
membership
with
removing
and
inserting
VLAN
tags
while
packet
is
being
transmitted
to
ports
3
and
2,
respectively.
Limitations
and
rules
on
using
VLAN:
Supports
up
to
16
full
range
VLAN
IDs.
If
hardware
VLAN
table
is
full,
software
responds
with
the
error
message:
“
Error:
VLAN
table
is
full.
”
Only
one
VLAN
with
unique
IDs
is
allowed.
When
adding
a
different
VLAN
with
the
same
IDs,
the
old
VLAN
is
deleted
(also
the
other
types
of
VLANs).
Simultaneous
use
of
Access
and
Trunk
type
VLANs
is
not
allowed.
Use
the
“
Access
”
VLAN
type
only
for
remote
FODU,
because
after
setting
the
“
Access
”
VLAN
type,
access
to
the
management
CPU
from
LAN
port
is
blocked
!
In
order
to
pass
untagged
packets
through
the
link,
“
Ethernet
vlan
0
traffic
”
should
be
added
Steps
required
for
VLAN
configuration:
1)
Configure
switches
for
VLAN
tag
encapsulation
on
both
ends
of
the
link;
2)
Set
preferable
VLAN
configuration
in
“VLAN
configuration”
of
remote
link
side
FreeMile
FODU
Web
management;
3)
Set
preferable
VLAN
configuration
in
“VLAN
configuration”
of
local
link
side
FreeMile
FODU
Web
management.
Examples
of
VLAN
usage:
Figure
4.27.
VLAN
configuration
with
VLAN
tag
encapsulation
on
the
ISP
side
(!)
Attention!
VLAN
tagging
already
must
be
configured
on
the
switch
and
known
to
you;
otherwise,
incorrect
VLAN
configuration
may
disable
access
to
management
port.