QoS Rule

Refer to the Flow Classification section for creating rules. You must set a QoS Class [created in QoS Class Manager] as the Target for the rule.

Configuration steps

Step 1: Create Class Managers

Define your traffic classes under the Class Manager menu.

1. Name: Give the class a short name (e.g., VoIP_Fixed, General_Web).
2. Descrition: Give the class description (e.g., VoIP Traffic with Fixed Bandwidth).
3. Priority & DSCP: Select the traffic Priority level and optional DSCP tag.
4. Allocation Type: Select Bandwidth for critical apps or Percentage for general data.
5. Limits: Set your Guaranteed and Maximum values.
   

   

• All the created classes will be listed in QoS Class Manager

  

Step 2: Define Flow Classification Rules

Define one or more Flow Classification Rule for each QoS Class [i.e., Link traffic types to your Classes.]

1. Create a Flow Classification Rule.
2. Define the match criteria (Source/Dest IP, Port, Application, DSCP).
3. Target: Select the Class Manager created in Step 1.
   

   

Step 3: Assign Classes to Interface

Assign one or more QoS Classes to an Interface (under Interface Manager)

1. Select the physical interface.
2. Add the Class Managers you wish to active on this port.
   
3. List the classes that are assigned to the interface.

   

4. Local Overrides (Interface-Specific Settings): Once a Class is added to an interface, its parameters (Bandwidth, Priority, Allocation Type) can be modified directly in this list.
   • Scope: These changes are local to this interface only. They do not alter the original "Global" Class Manager definition.

   

   • Exception: DSCP Marking cannot be overridden locally. It is strictly inherited from the global Class Manager configuration.
5. Activate the changes. The i icon indicates activation is required.
   

   Once activated, the bandwidth allocation logic is applied immediately.

   

6. Enable/Disable QoS globally for the interface.
   Or Individual QoS classes also can be enabled or disabled.

Step 4: Set Interface Capabilities & Bandwidth

The Maximum Bandwidth for an interface acts as the ceiling for all QoS calculations. This value is determined in one of three ways, prioritized in the following order:

1. Dynamic Measurement (NPM): If configured on a WAN interface, the actual measured throughput (via active speed testing) overrides all other values.
   
2. Manual Configuration: The user explicitly sets the Maximum/Guaranteed Bandwidth in the Interface Manager.

   

3. Auto-Detection (Ethtool): During system bring-up, the OS detects the negotiated link speed (e.g., 1000Mbps or 100Mbps).

Note: Make sure all the Bandwidth specified in QoS Class manager is within the limit of an Interface.

Step 5: Configure Network Performance Monitor (NPM)

For WAN interfaces, NPM can be enabled to dynamically measure Bandwidth, Packet Loss, Jitter, and Latency. NPM generates synthetic TCP and UDP load on Port 5206 against a target server.

Prerequisites: Internet Breakout Must be configured on the specific WAN interface to ensure the measurement traffic flows correctly through the Gateway.

Configuration Parameters:

1. Measure Interval: How often the test runs. Default is 12 Hours. Can be customized.
2. Remote Server: The IP address of the target NPM Server.
3. Remote Port: The port the server listens on for control commands. Default is 8766. (Note: The actual data test runs on port 5206).
   

   Firewall Note: If the remote NPM Server is behind a router/NAT, you must forward Ports 8766 (Control) and 5206 (Data) to the server.

4. Enable/Disable: Toggle to activate the feature.
   

NPM States & Operations: On-Demand test can manually triggered by clicking the Play/Run icon.

The status indicator will show:

• PENDING: Waiting for the next scheduled interval or manual trigger.
• NOT READY: Interface is down, NPM is disabled, or current link usage is >50% (tests are
  skipped to avoid disrupting user traffic).
• RUNNING: Speed test is in progress.
• FAILED: Test failed (e.g., server unreachable).
• SUCCESS: Measurement completed.

History: Click the Book icon next to the bandwidth value to view historical performance data.

Utility: CPE as NPM Server

A zWAN CPE can act as an NPM Server for other devices.

• Navigate to: Network --> Utilities --> N/W Perf Monitor
• Action: Enable to Start NPM Server.

Note: NPM Server/Client Mutuality: If a CPE is running as an NPM Server, it cannot simultaneously be an NPM Client. The NPM configuration options in the Interface Manager page will be disabled.

Usage

QoS Class manager is used for Traffic Shaping. Packet belong to particular QoS class can take more precedence and get guaranteed bandwidth when the Interface has more packets to process. QoS class manager helps the Traffic Shaping module to sort the collision and prioritize the packet processing based on priority and bandwidth specified in QoS Class manager.

Known Behaviors & Limitations

1. Oversubscription: If the sum of all Fixed Bandwidth classes exceeds 90% of the Interface Max, the system will clamp (reduce) the bandwidth of the lowest priority fixed class to fit within the limit. A warning will be logged.
2. Minimum Floor: To prevent calculation errors, the minimum allowed bandwidth for any class is 10 Kbps.
3. Atomic Application: When applying QoS changes, the interface may drop packets for a fraction of a second. This is intentional (Atomic Drop) to prevent packet leakage while the kernel switches queuing disciplines.
4. Percentage Calculation: "100%" in a Percentage Class means "100% of the Remaining Bandwidth," not 100% of the total Link.
   Formula: Class Rate = (Total Link - Fixed Classes) * (Class %)

[/vc_column_text][/vc_column][/vc_row]