QoS
QoS in netverdict is a policy and packet-metadata model. It can classify traffic, mark DSCP, and preserve configured policy intent for labs and config review. It is not a queueing ASIC simulator.
Support level
Section titled “Support level”| Area | Level | Notes |
|---|---|---|
| Classification | Behaviour model | Class maps match ACLs/protocols where implemented. |
| Marking | Supported | DSCP/precedence metadata can be set on packets. |
| Policy maps | Supported | Class/action structure is parsed and emitted. |
| Service policy | Supported | Interface attachment is represented. |
| Policing/shaping | Config model | Parsed/stored; detailed queue timing is not modelled. |
| Scheduling | Not modelled | No hardware queue simulation. |
Standards coverage
Section titled “Standards coverage”| Standard | Coverage | Notes |
|---|---|---|
| RFC 2474 | Behaviour model | DSCP marking field semantics. |
| Cisco MQC | Behaviour model | Class-map / policy-map / service-policy structure. |
Feature matrix
Section titled “Feature matrix”| Feature | Status | Notes |
|---|---|---|
class-map | Supported | Match criteria container. |
policy-map | Supported | Action container. |
match access-group | Supported | ACL-based classification. |
set dscp | Supported | Packet metadata marking. |
police | Config model | Stored for config fidelity. |
shape | Config model | Stored for config fidelity. |
service-policy input/output | Supported | Interface attachment. |
Vendor command matrix
Section titled “Vendor command matrix”| Command | IOS-style | Junos-style | VyOS-style | Notes |
|---|---|---|---|---|
class-map match-any VOICE | Supported | n/a | Partial | Classification. |
policy-map WAN-OUT | Supported | n/a | Partial | Policy container. |
set dscp ef | Supported | Partial | Partial | Marking. |
service-policy output WAN-OUT | Supported | Partial | Partial | Interface attachment. |
show policy-map interface | Supported | Partial | Partial | Policy view. |
Behaviour notes
Section titled “Behaviour notes”QoS actions affect packet metadata that other parts of the engine can carry. Queue occupancy, serialization delay, and scheduler fairness are intentionally not inferred from configured bandwidth statements.
Examples
Section titled “Examples”Canonical example
configure terminalclass-map match-any VOICE match access-group name VOICE-RTPpolicy-map WAN-OUT class VOICE set dscp efinterface GigabitEthernet0/0 service-policy output WAN-OUTendshow policy-map interface GigabitEthernet0/0Vendor styles
IOS-style
class-map match-any VOICE match access-group name VOICE-RTPpolicy-map WAN-OUT class VOICE set dscp efinterface GigabitEthernet0/0 service-policy output WAN-OUTJunos-style
set class-of-service classifiers dscp VOICE forwarding-class expedited-forwarding loss-priority low code-points efset class-of-service interfaces ge-0/0/0 unit 0 rewrite-rules dscp WAN-OUTVyOS-style
set qos policy shaper WAN-OUT class 10 match VOICE ip dscp efset qos interface eth0 egress WAN-OUTKnown limits
Section titled “Known limits”LLQ/WFQ scheduler behaviour, WRED curves, shaping token buckets, hierarchical queue timing, and platform ASIC differences are not modelled.