Filter
Top Products
(Revised 2010-9-27) Page 20 of 159
Each of these three QOS methods below is included or not based on the settings on the relevant browser
page:
1) Force High Priority (Port Based),
2) IEEE802.1p (Tagged QOS), or
3) DSCP (differentiated services code points) (RFC 2474).
When Force High Priority is enabled, the port based priority is included in the decision for all ports and all
frames received on a port will use the default QOS priority for that port in the decision. For example, if it is
desired to have ingress frames on a port egress to the highest priority transmit queue regardless of other
factors, then enable Force High Priority and set the port's Default Port Priority to 7.
Virtual LAN
The switch provides support for setting up tagged Virtual LANs (Local Area Networks). A port may belong
to any number of Virtual LANs. The VLAN membership of a device is determined by the VLAN(s) that
have been defined for the port to which the device is connected. If a device should move from one port to
another, it loses its current VLAN membership and inherits that of the new port it is connected to.
VLANs facilitate easy administration of logical groups of devices that can communicate as if they
were on the same LAN. Traffic between VLANs is restricted, unless the ports are explicitly configured
as overlapping VLANs. Switches forward unicast, multicast, and broadcast traffic only on LAN segments
that serve the VLAN to which the traffic belongs.
A Default Virtual LAN (VID=1) exists to which a port, which is not a member of any other Virtual LAN,
will belong. This allows the switch to operate as a ‗normal‘ switch when it is used in a network. A port is
automatically removed from the Default VLAN when it is reconfigured to belong to another Virtual LAN,
because that is the most common operation. But, if desired, the port can be included in VLAN 1 by
configuring VLAN 1 last.
If switch ports are configured to transmit and receive untagged frames, end devices are able to communicate
throughout the LAN. Using Tagged VLANs, the switch has the ability to take non-tagged packets in some
ports, add a VLAN tag to the packet and send it out tagged ports on the switch. The VLANs can also be
configured to accept tagged packets in tagged ports, strip the tags off the packets, and send the packets back
out other untagged ports. This allows a network administrator to set up the switch to support devices on the
network that do not support VLAN Tagged packets. The administrator can also set up the ports to discard
any packets that are tagged or to discard any packets that are untagged based on a hybrid VLAN of both
tagged and untagged ports, and using the VLAN Ingress Filter on the switch.
For each switch port there is one and only one PVID (port VLAN ID) setting. If an incoming frame is
untagged and untagged frames are being accepted, then that frame will inherit the tag of the PVID value for
that port. Subsequent switch routing and treatment will be in accordance with that VLAN switch map. By
configuring PVIDs properly and configuring for all frames to exit untagged, the switch can achieve a ‗port
VLAN‘ configuration in which all frames in and out can be untagged, thus not requiring external devices to
be VLAN cognizant.
To understand how a VLAN configuration will perform, first look at the port on which the frame enters the
switch, then the VLAN ID (if the frame is tagged) or the PVID (if the frame is untagged). The VLAN
defined by the VID or PVID defines a VLAN group with a membership of ports. This membership
determines whether a port is included or excluded as to frame egress from the switch.
The 710FX2 Series switch also has the ability to allow overlapping VLANs. Overlapping VLANs give