- Print
- PDF
Setting Up a Policies Configuration Job
You can set up different elements (filters, bandwidth regulators, CoS profiles and bandwidth regulator sets) and assign them to a traffic policy, thereby defining the new service and its attributes.
To set up a Policies Job
Access the page Commission ▶ Jobs.
Set all common configuration job settings, as described in "Creating Configuration Jobs in GUI Mode" and in "Creating Configuration Jobs Using Data Sets".
Select Policies in the left pane. The Policies tab is displayed.
Complete all fields in the Policies tab as required. For more information on specific parameters, see the table below.
Use the Add button or Duplicate button to add Policies as required.
Note: When duplicating a row, always select the row to duplicate before clicking the Duplicate button.
Click Apply, then click Close.
Click the Refresh button to refresh the user interface.
Policies tab (Commission ▶ Jobs)
Policy general
Parameter | Description |
---|---|
Enable | Select this box to activate the policy. |
Traffic list | Name of the traffic policy. |
Entry index | The position of the rule in the policy list. |
Flow name | This parameter is only used on the FSX Skylight element. On the FSX, a flowmeter instance is called a flow. The Flow name is the unique identifier for a flow on the FSX. Enter a name that contains a maximum of 31 alphanumeric characters. Note: If the FSX will include both Layer-2 and IPv4 (Layer-3) filters, it is recommended that flow names include a prefix that indicates the type of filter it uses. |
Outgoing port | The egress port assigned to this policy. |
Queuing Profile | A drop-down list with options for the queuing profile associated with this outgoing port. By default, default queuing-profile is selected. |
Filter
Parameter | Description |
---|---|
Filter type | The filter type (Layer-2 filter, IPv4 filter, IPv6 filter or VID set ) used to classify traffic. |
Filter name | The name of the filter. You must select a filter name from the drop-down list. Note: The catch-all filter enables you to monitor all traffic on a port. |
Action | The action applied to traffic that matches the filter. Make a selection from the drop-down list:
|
Monitor
Parameter | Description |
---|---|
Enable | Enable or disable the monitoring port. |
Monitor type | The type of monitor port for this NE:
|
Monitor port | The port to which traffic is forwarded for monitoring. |
EVC mapping
Parameter | Description |
---|---|
Encapsulation | Select one of the following encapsulation methods:
|
Ethertype Second Ethertype | The Ethertype of the VLAN to be added (if any). Possible values:
|
VLAN ID Second VLAN ID | VLAN ID of the VLAN to be added (if any). Possible values range between 0–4,095. |
CoS mapping
Parameter | Description |
---|---|
PCP action | The PCP (Priority Code Point) action to perform. Possible values are:
Note: The choices may vary depending on the Encapsulation option and on the PCP action you selected. |
CoS 1 enable CoS 2 enable | Enable or disable the first and second traffic mapping choices. |
CoS 1 profile CoS 2 type | The type of Layer-2 traffic mapping to perform for the first and second choices. Possible values are:
|
CoS 1 profile CoS 2 type | CoS profile to apply from the list. The list includes the default CoS profile and the ones you created. |
CoS 1 regulator CoS 2 regulator | The bandwidth regulator set to apply from the list. The list includes the bandwidth regulator sets you created. |
Default mapping
Parameter | Description |
---|---|
Pre-marking Green CFI/DEI Green PCP Yellow CFI/DEI Yellow PCP | Pre-mark, with a specific color, the traffic that does not match the first and second traffic mapping choices. This option has no effect if the enabled bandwidth regulator is color-blind. In addition, if no bandwidth regulator has been enabled, this option selects the default green/yellow CFI & PCP values to be used in the outgoing frames.
The traffic color affects how the regulator handles the traffic. |
Regulator enable | Activates a default bandwidth regulator. If the PCP action is Map and the traffic does not match the configured maps, direct default mapping is used. |
Regulator | The bandwidth regulator associated with the traffic matched by this policy. |
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks