When you configure the priority queues and CBWFQ queues on different subinterfaces and pvcs, they all combine to service the same physical interface hardware-ring.
If you have two separate priority queues on two different PVCs, they will be effectively combined when it comes to send the packets out the physical interface.
If you're talking frame relay, you can skip using FRTS on a per-pvc basic, and apply a generic MQC configuration directly to the interface with the service-policy command if you would like to do the QoS across multiple PVCs.
"If you send all voip traffic using one pvc, interactive traffic with anether pvc, best-effort traffic with another pvc, how can you reserve bandwidth for different classess ? "
If using CBWFQ, first, insure your PVCs' bandwidths don't oversubscribe the physical interface bandwidth. Second, enforce the PVCs bandwidth allowances. (For FR, can be done with shapers, for ATM, can be done by the hardware.)
You might also want dedicated PVCs for real-time traffic so that your CIR is the same as the expected real-time traffic demand.
I also recall there's a technique to use a special two level queue for FR to insure multiple PVCs real-time traffic always goes first, but I haven't used that feature.
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application Engineered...
Internet security is important with the increasing attacks that are happening every day. Many internet and browsing security solutions exist, but some are not very easy to use or maybe the question is how can I enable them?
Cisco Software Manager Server
This document describes the programmatic interfaces, RESTful APIs, which are supported by Cisco Software Manager Server (CSM Server).
CSM Server supports a set of finite RESTful APIs. The fir...