Qos Interface Considerations; Trusted And Untrusted Interfaces - Avaya 8800 Planning And Engineering, Network Design

QoS interface considerations

Four QoS interface types are explained in detail in the following sections. You can configure an
interface as trusted or untrusted, and for bridging or routing operations. Use these parameters to
properly apply QoS to network traffic.
QoS interface consideration navigation
•

Trusted and untrusted interfaces

• Bridged and routed traffic
• 802.1p and 802.1Q recommendations
Trusted and untrusted interfaces
You can set an interface as trusted (core) or untrusted (access).
Use a trusted interfaces (core) to mark traffic in a specific way, and to ensure that packets are
treated according to the service level of those markings. Use a core setting when control over
network traffic prioritization is required. For example, use 802.1p-bits to apply desired CoS attributes
to the packets before they are forwarded to the access node. You can also classify other protocol
types ahead of IP packets if that is required.
A core port preserves the DSCP and 802.1p-bits markings. The switch uses these values to assign
a corresponding QoS level to the packets and sends the packets to the appropriate egress queues
for servicing. The following figure illustrates how packets are processed through a core port.
Figure 148: Core port QoS actions
June 2016
on page 295
on page 296
on page 297
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
QoS interface considerations
295