Effortlessly configure, monitor, and report on QoS
Why is QoS Configuration and Monitoring Important
QoS provides security
QoS can stop traffic that appears compromised, comes from a specific country, or fails to meet the policy standards. It can provide special prioritization markers in the IP header for encrypted traffic for further examination.
QoS Prevents Network Congestion
when a segment of the network is at risk of congestion, low-priority packets will be dropped to keep high-priority packets on track. This adjustment is called Weighted Random Early Detection (WRED).
QoS reduces Latency
Without QoS, the device offers best-effort service for each packet. With QoS the highest-priority workloads get through when networks face limited capacity. The reduces latency on Real-time Transport Protocol (RTP) packets like video conferencing, so that network congestion impacts other traffic first.
Improve network and application performance with LiveAction QoS Configuration & Monitoring
QoS Wizard Templates
Select one of several built in best-practice QoS Policy templates Built-in best practice policy templates allow users to leverage the QoS wizard and templates to apply policies across multiple devices
User Friendly GUI
Graphical interface replaces command line with real-time graphs and an easy-to-understand policy viewer that allows for real-time tweaks to policies
Synthetic Traffic Generation and Analysis
Leverage built-in IP SLA technology to graphically generate different types of traffic and measuring the impact of QoS policies
QoS policy reports provide greater detail of configuration settings, performance issues, drops and policy errors with 95th/99th percentile threshold.
DSCP Audit via NetFlow
Audit DSCP values to ensure the priority traffic is using the expected queues and lower priority data is treated properly.
Full Modular QoS Configuration
Support for FIFO, LLQ, CQ, WRED, CBWFQ and Priority Queue. Additionally, use hierarchical policy creation for advanced configurations.
QoS Best Practices Tips
- Provide at least 25% bandwidth for Best Effort traffic in the class default.
- If multiple applications use PQ, use discrete priority queues for each application. ie. VOIP gets its own unique queue, video gets its own queue, etc.
- Hierarchical traffic shaping should use a BC value of less than or equal to 1/100 of the CIR. This may be increased to 2/100 of CIR for immersive video over IP implementations. The BE value should always equal 0.
- Overprovision video over IP queues by 20% to accommodate bursts.
The ability to track, monitor, and make live changes to QoS policy is an essential part of a modern IT strategy.