Table of Contents
Advertisement
UVID
Conflicts
Auto refresh
Refresh
2
.
3
.
4
5
V
L
A
N
2
.
3
.
4
5
V
L
A
N
In a private VLAN, communication between ports in that private VLAN is not permitted. A
VLAN can be configured as a private VLAN.
Private VLANs are based on the source port mask, and there are no connections to VLANs.
This means that VLAN IDs and Private VLAN IDs can be identical.
A port must be a member of both a VLAN and a Private VLAN to be able to forward
packets. By default, all ports are VLAN unaware and members of VLAN 1 and Private
VLAN 1.
A VLAN unaware port can only be a member of one VLAN, but it can be a member of
multiple Private VLANs.
Function name:
VLAN – Private VLANs – Private VLAN Membership
Function description:
The Private VLAN membership configurations for the switch can be monitored and
modified here. Private VLANs can be added or deleted here. Port members of each Private
VLAN can be added or removed here.
126
Shows UVID (untagged VLAN ID). Port's UVID
determines the packet's behaviour at the egress side.
Shows status of Conflicts whether exists or not. When a
Volatile VLAN User requests to set VLAN membership or
VLAN port configuration, the following conflicts can occur:
Functional Conflicts between features.
Conflicts due to hardware limitation.
Direct conflict between user modules.
The simple counts will be refreshed automatically on the UI
screen.
The simple counts will be refreshed manually when user use
mouse to click on "Refresh" button.
–
P
r
i
v
a
t
e
V
L
A
N
s
–
P
r
i
v
a
t
e
V
L
A
N
s
–
P
r
i
v
a
t
e
V
L
A
N
M
–
P
r
i
v
a
t
e
V
L
A
N
M
e
m
b
e
r
s
h
i
p
e
m
b
e
r
s
h
i
p
VigorSwitch P2261 User's Guide
Hide quick links:
Advertisement
Table of Contents
