Allied Telesis AlliedView-EMS 4.0.2 VLAN-Manager - Manual (Page 72)

AlliedView™-EMS 4.0.2 VLAN MANAGER USER’S GUIDE Page 72 of 77
Input Field Valid Values Length
Name (cannot be
modified)
- Alphanumeric characters
- Underscore ("_")
- Dash ("-")
Note - VLAN names must contain at least one (1)
alphabet character.
Note - "ALL" is a reserved word and cannot be used as
a VLAN name.
1 - 32 characters
Identifier (cannot
be modified)
1 - 4094 -
Operation Mode
(cannot be
modified)
- Normal
- Private
- Nested
-
6.18.3 Notes
•
When adding/modifying a Nested VLAN, specifying a port that is already a member
of an existing Normal VLAN will not generate any error. However, the specified
port will be ignored. In addition, during modification, existing member ports having
the same status (tagged/untagged) as the specified port will be deleted.
•
When importing the default VLAN, VLAN Manager disregards the values specified
for Untagged Ports.
•
During an Import VLAN operation, VLAN Manager will ignore the values specified
for certain fields depending on the value specified for the Operation Mode field:
o
If Operation Mode is "Normal" - Uplink Port, Private Ports, Core Ports
and Customer Ports
o
If Operation Mode is "Private" - Core Ports and Customer Ports
o
If Operation Mode is "Nested" - Tagged Ports, Untagged Ports, Uplink Port
and Private Ports
•
User-created VLANs are classified as Multiple Type VLANs. There are three
possible VLAN associations for a Multiple Type VLAN: IP Subnet, Protocol and Port.
Currently, VLAN Manager only supports Port association. As a result, when
attempting to modify a VLAN with an association other than Port, VLAN Manager
automatically changes the association of that VLAN to Port.
•
When adding/modifying a Nested VLAN, specifying 2 or more core ports where one
of the specified ports is already a member of an existing Nested VLAN will result
in the error message: "Must return port <n> to the default VLAN as untagged port
based."
6 Device Support