Setting Up a Policies Configuration Job

  • Updated on Oct 29, 2024
  • Published on Jul 8, 2021
  • 6 minute(s) read
  • Jonathan Poole
 Prev Next

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

  1. Access the page Commission â–¶ Jobs.

  2. Set all common configuration job settings, as described in "Creating Configuration Jobs in GUI Mode" and in "Creating Configuration Jobs Using Data Sets".

  3. Select Policies in the left pane. The Policies tab is displayed.
    Setting Up a Policies Configuration Job.png

  4. Complete all fields in the Policies tab as required. For more information on specific parameters, see the table below.

  5. Use the Add PLUS BUTTON.png button or Duplicate DUPLICATE BUTTON.png button to add Policies as required.

Note: When duplicating a row, always select the row to duplicate before clicking the Duplicate DUPLICATE BUTTON.png button.

  1. Click Apply, then click Close.

  2. Click the Refresh REFRESH BUTTON.png 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 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:
  • Drop Traffic: The traffic matching the filter is dropped. Policy statistics are collected as part of this policy.
  • Permit Traffic: The traffic matching the filter is counted in the statistics and then forwarded. Policy statistics are collected as part of this policy.
  • MGMT-OAM: The traffic matching the filter is forwarded to the CPU so that it can be processed. No policy statistics are collected as part of this policy.
  • MGMT-OAM & Drop: The traffic matching the filter is forwarded to the CPU so that it can be processed, then it is dropped. Policy statistics are collected as part of this policy.
  • MGMT-OAM & Forward: The traffic matching the filter is forwarded to the CPU so that it can be processed and forwarded. Policy statistics are collected as part of this policy.

Monitor

Parameter Description
Enable Enable or disable the monitoring port.
Monitor type The type of monitor port for this NE:
  • None: For NEs without a monitor port.
  • Port: For NEs with a standard monitor port.
  • Virtual: For NEs equipped with the vmonitor type of monitor port.
Monitor port The port to which traffic is forwarded for monitoring.

EVC mapping

Parameter Description
Encapsulation Select one of the following encapsulation methods:
  • None: Regulate traffic based on PCP, IP precedence or DSCP values.
  • Push: Add a VLAN tag.
  • Pop: Remove the outer VLAN tag, if any.
  • Replace: Perform an action similar to Push, but rather than adding a new VLAN tag, replace the VLAN tag with the information provided by the Ethertype and VLAN ID.

    Note: This action requires a filter that checks for the presence of at least one VLAN tag.

  • Preserve VLAN - New CFI/PCP: Keep the VLAN tag while allowing the CFI/PCP values to be modified.
  • Push & Preserve: Add a new VLAN tag using the VLAN ID of the inner VLAN, if any.
  • Push & Push: Add two VLAN tags (Q-in-Q).
  • Push & Replace: Add a new outer VLAN tag and replace the inner VLAN tag with the information provided by the Ethertype and VLAN ID.
  • Pop & Replace: Pop the outer VLAN tag and replace the inner VLAN tag with the information provided by the Ethertype and VLAN ID.

    Note: This action requires a filter that checks for the presence of two VLAN tags.

  • Pop & Pop: Pop both the inner and the outer VLAN tags (Q-in-Q).

    Note: The details of this option will vary depending on the available PCP actions.
Ethertype

Second Ethertype

 The Ethertype of the VLAN to be added (if any). Possible values:
  • C-VLAN: 0x8100
  • S-VLAN: 0x88A8 (or 0x9100)
  • T-VLAN: 0x9100 (or 0x88A8)
Note: The values assigned to the S-VLAN and T-VLAN Ethertypes can vary, depending on the S-VLAN Ethertype value selected in the page System â–º Configuration â–º Mode.
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:
  • Preserve: Keep the PCP value or gather its value from the CoS profile.
  • Direct: Use the direct mapping options.
  • Map: Map the PCP/DEI values according to the selected CoS Profile.
For each PCP action, there may be one or two traffic mapping choices. If the frame does not match the first or the second choice, default PCP values are used.

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:

  • PCP VLAN: Priority Code Point (p-bits) in 802.1Q tags.
  • PCP VLANinVLAN: Priority Code Point (p-bits) in 802.1Q-in-Q tags.
  • IP Precedence: IP precedence bits in the IPv4 ToS byte.
  • DSCP: DSCP bits in the IPv4 ToS byte.
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.
  • Green traffic uses tokens from the CIR bucket until depleted, at which time it will be tagged as Yellow data.
  • Yellow traffic uses tokens from either the CIR + EIR buckets or just the EIR bucket, depending on how the coupling flag is set in the regulator. Once the CIR + EIR tokens are depleted, this traffic will be tagged as Red data (red traffic is dropped).
Note: Data cannot be pre-marked as Red if its bandwidth regulator has been disabled. In such circumstances, using Drop Traffic instead may be advisable.

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.

© 2025 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