Navigation
Supported Platforms
Related Documentation
- EX, M, MX, PTX, T Series
- Default Behavior Aggregate Classification Overview
- Configuring Drop Profile Maps for Schedulers
- M, MX, PTX, T Series
- Applying Default Rewrite Rules
- CoS Inputs and Outputs Examples
CoS Inputs and Outputs Overview
Some CoS components map one set of values to another set of values. Each mapping contains one or more inputs and one or more outputs.
Some CoS components map one set of values to another set of values. Each mapping contains one or more inputs and one or more outputs. When you configure a mapping, you set the outputs for a given set of inputs, as shown in Table 1.
Table 1: CoS Mappings—Inputs and Outputs
CoS Mappings | Inputs | Outputs | Comments |
|---|---|---|---|
The map sets the forwarding class and PLP for a specific set of code points. | |||
The map sets the drop profile for a specific PLP and protocol type. | |||
The map sets the code points for a specific forwarding class and PLP. |
Related Documentation
- EX, M, MX, PTX, T Series
- Default Behavior Aggregate Classification Overview
- Configuring Drop Profile Maps for Schedulers
- M, MX, PTX, T Series
- Applying Default Rewrite Rules
- CoS Inputs and Outputs Examples
Published: 2013-08-28
Supported Platforms
Related Documentation
- EX, M, MX, PTX, T Series
- Default Behavior Aggregate Classification Overview
- Configuring Drop Profile Maps for Schedulers
- M, MX, PTX, T Series
- Applying Default Rewrite Rules
- CoS Inputs and Outputs Examples
