Chapter 11 Layer 3 QoS
CAR and WRED Overview
Implications of Engine Type
Engine type refers to different hardware architectures. From a management perspective, the engine type determines what functionality is available to the client. Currently, this only applies to Layer 3 QoS. The following is a summary of how engine type affects Layer 3 QoS:
•
•
•
•
Cisco 12000/10720 Router Manager will detect the engine type applicable to a given module (line card) and prevent operations that are not applicable.
Note
CAR and WRED in Cisco 12000/10720 Router Manager
CAR and WRED are modeled as objects in Cisco 12000/10720 Router Manager. There are two types of CAR objects: CAR policies and access lists. There is two types of WRED objects: CoS (Class of Service) queue groups and ToFab policies.
When you create these objects in Cisco 12000/10720 Router Manager, you can work within the Layer 3 QoS view to create, apply, delete or edit Layer 3 QoS objects. Created CAR policies are placed under the CAR Policies container in the Layer 3 QoS view. Created access lists are placed under the Access List container in the Layer 3 QoS view. Created CoS queue groups are placed under the
Tip Access lists are only supported within the realm of CAR and do not function as
It is important to note that Layer 3 QoS CAR and WRED objects (access lists, policies, CoS queue groups, ToFab policies) are global, meaning they can be applied to any module/interface object within Cisco 12000/10720 Router Manager. For example, the CosQ groups are applied to interfaces whereas the ToFab policies are applied to modules (line cards).
Cisco 12000/10700 v3.1.1 Router Manager User Guide
|
|
| |
|
|
