Stp Configuration; Stp Overview; Table 32 Configuration: Switch Configuration: Priority Queue - ZyXEL Communications 1 User Manual

Element management system
Hide thumbs Also See for 1:
Table of Contents

Advertisement

The following table describes the labels in this screen.

Table 32 Configuration: Switch Configuration: Priority Queue

LABELS
Priority Queue
Assignment
Priority Level
Level 7
Level 6
Level 5
Level 4
Level 3
Level 2
Level 1
Level 0
Apply

11.4 STP Configuration

This section discribes STP and how to configure STP.

11.5 STP Overview

The switch supports STP. STP detects and breaks network loops and provides backup links
between switches, bridges or routers. It allows a device to interact with other STP-aware
devices in your network to ensure that only one path exists between any two stations on the
network.
Refer to the user's guide that comes with your switch for more information.
Chapter 11 Switch Configuration
DESCRIPTION
IEEE 802.1p defines up to 8 separate traffic types by inserting a tag into a
MAC-layer frame that contains bits to define class of service. Frames
without an explicit priority tag are given the default priority of the ingress
port. Use these fields to configure the priority level-to-physical queue
mapping. The switch has 8 physical queues that you can map to the 8
priority levels. On the switch, traffic assigned to higher index queues gets
through faster while traffic in lower index queues is dropped if the network
is congested. See also
Section 13.7 on page 131
The following descriptions are based on the traffic types defined in the
IEEE 802.1D standard (which incorporates 802.1p). Select a level from the
drop-down list box(es).
Typically used for network control traffic such as router configuration
messages.
Typically used for voice traffic that is especially sensitive to jitter (jitter is the
variations in delay).
Typically used for video that consumes high bandwidth and is sensitive to
jitter.
Typically used for controlled load, latency-sensitive traffic such as SNA
(Systems Network Architecture) transactions.
Typically used for "excellent effort" or better than best effort and would
include important business traffic that can tolerate some delay.
This is for "spare bandwidth".
This is typically used for non-critical "background" traffic such as bulk
transfers that are allowed but that should not affect other applications and
users.
Typically used for best-effort traffic.
Click Apply to save your changes back to the switch.
NetAtlas Enterprise 1.00 User's Guide
for related information.
102

Advertisement

Table of Contents
loading

This manual is also suitable for:

Netatlas enterprise 1.00

Table of Contents