Packet flow through Vyatta NOS
How packets travel through Vyatta NOS and interact with key entities.
- Ingress interface
- As the packets arrive at the ingress interface the system can separate them into specifically identified vLAN traffic, and all other traffic (non-vLAN).
- Forwarding lookup
- The system uses forwarding lookup to identify the appropriate egress interface to use. Then, the system will apply any QoS policy that is attached to the egress interface or virtual interface (VIF) to the packets.Note: We use VIFs to identify and configure specific vLAN attributes on an interface.
- Virtual interfaces VIFs
- Class/profile
- Classification splits the packet stream across 32 profile queues.
- 32 profile queues
- The system maps each profile queue to one of four traffic classes.
- Four traffic classes, each with eight WRR queues
- The scheduling part of the QoS profile determines the sequence by which the system will pull packets from the profile queues. The system will use the weighted round robin (WRR) scheduling method to pull packets from the eight queues in each traffic class.
- Strict priority TC0>TC1>TC2>TC3
- The system will pull packets from the four traffic classes in the profile in strict priority order.
- Fair Queuing Interface VIFs
- The system services each profile fairly.
- Fair queuing across the vLANs
- The system services each vLAN fairly.
- Egress interface
- We can attach a QoS policy to each interface at egress.
- You do not have to configure each interface to have a QoS policy attached to it.
- You can attach the same QoS policy to multiple interfaces or VIFs — but each policy instance operates independently.