Implications of engine type, Car and wred in cisco 12000/10720 router manager – Cisco 12000/10700 V3.1.1 User Manual
Page 291
11-5
Cisco 12000/10700 v3.1.1 Router Manager User Guide
OL-4455-01
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:
•
CAR—Supported for Engine 0 and 1
•
CAR—Limited support for Engine 4
•
PIRC—Supported for Engine 2 (see
“Per Interface Rate Control (PIRC) Support” section on
for further details).
•
WRED—Supported for Engine 0, 2, and 4 (see
“Engine Type Support for WRED” section on
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
Auto-detection is not supported for Engine type 4.
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 WRED-MDRR
container in the Layer 3 QoS view. Created ToFab polices are placed under the WRED-MDRR container
in the Layer3QoS view.
Tip
Access lists are only supported within the realm of CAR and do not function as stand-alone
objects.
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).