Avaya P580 - Manual (Page 190)

5-10 Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, v5.3.1
Chapter 5
Assigning VLANs to a Port and Associated Issues
There are two ways to assign VLANs to ports on the Avaya
Multiservice Switch. You configure the Port(s) to the VLAN desired
for the individual port(s), or entire module. Assigning the VLAN this
way enables the port(s) to receive information for the assigned
VLAN and causes all untagged frames arriving on this port to be
assigned to the specified VLAN. The port(s) will still assign incoming
tagged packets to the VLAN indicated by the tag.
In the current release of software, a non-trunk port only supports a
single VLAN per port. Multiple VLANs per port is NOT
recommended and can have adverse effects on network
performance.
The second way is to assign the VLAN to a port is by using the
following CLI command in Enable/Configure mode:
<configure># set VLAN <vlan-id or name> <options>
By selecting the VLAN name or VLAN ID, you can bind the selected
VLAN to additional ports. When binding VLANs this way, the port is
part of the flooding domain of the selected VLAN. This is an
alternative to using the binding types “bind to all” and “bind to
receive”, that allows you to add a port(s) to a subset of VLANs in the
switch.
* Note: This configuration should only be used under special
circumstances and with the assistance of customer
support as undesirable results may occur (e.g.
destination unknown unicast storms).
See Chapter 4, “Using VLANs, Spanning Tree, Hunt Groups, and
VTP Snooping”, for a description of the parameters that will be
displayed when viewing VLAN information with the Web Agent and
the CLI command syntax.
Although this method of adding VLANs to a port could be thought
to support the request for multiple VLANs per port (also referred to
as overlapping VLANs), it is NOT recommended on clear (non
trunked) ports due to the impact it has on the network. The impact
is that destination unknown unicast packets are flooded on the
VLAN in which the source host is located. This causes all ports
assigned to this VLAN to receive the destination unknown unicast. If
enough of these destination unknown unicast packets are being sent
it could have a major impact on the network.