Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring External Parent Groups for JunosE Devices (SRC CLI)

 

Configuring external parent groups requires completion of these tasks:

Creating External Parent Groups in SRC Policies (SRC CLI)

You use external parent group folders to organize external parent groups. To create an external parent group, first create the external parent group folder (or use an existing folder), then create the external parent group. Use the following configuration statement to create an external parent group folder and external parent group:

To create an external parent group folder and external parent group:

  1. From configuration mode, enter the edit external-parent-group-folder statement. For example, to create an external parent group called epg1-folder and a group called epg1:

  2. (Optional) Enter a description for the external parent group.

  3. (Optional) Verify your external parent group configuration.

Configuring Rate-Limit Actions for External Parent Groups (SRC CLI)

Use the following statement to configure rate-limit profiles for external parent groups:

To configure rate-limit profiles for external parent groups:

  1. From configuration mode, specify the name of the external parent group for which you want to configure the rate-limit profile. For example, to configure the rate-limit profile for an external parent group called epg1:

    Specify the rate-limit options:

    • Specify that the rate-limit is either one rate or two rate. The rate-limit type determines the options that you can configure for a rate-limit action.

    • (Optional) Configure the target rate for the traffic that the policy covers.

    • (Optional) Configure the amount of bandwidth allocated to burst traffic in bytes.

    • (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to excess traffic flow over the committed rate.

    • (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to burst traffic in excess of the peak rate.

    • (Optional) Set the rate-limit to color aware for the rate-limit to process color values set in the TOS byte of the packet header.

  2. (Optional) Verify your configuration.

Configuring Hierarchical Rate-Limit Actions (SRC CLI)

You configure parent groups to create a hierarchy of rate-limits actions.

The type of action that you can create depends on the type of policy rule. See Policy Information Model.

Use the following configuration statements to configure rate-limit actions:

To configure a parent group:

  1. From configuration mode, create a parent group in a policy list—for example, PGShared.

  2. Configure a rate limit for the parent group.

    • Specify that the rate limit is either one rate or two rate. The rate-limit type determines the options that you can configure for a rate-limit action.

    • (Optional) Configure the target rate for the traffic that the policy covers.

    • (Optional) Configure the amount of bandwidth allocated to burst traffic in bytes.

    • (Optional) For two-rate rate-limit profiles, specify the amount of bandwidth allocated to excess traffic flow over the committed rate.

    • (Optional) For two-rate rate limit profiles, specify the amount of bandwidth allocated to burst traffic in excess of the peak rate.

    • (Optional) For one-rate rate limit profiles, specify the amount of bandwidth allocated to accommodate burst traffic.

    • (Optional) Set the rate-limit to color aware for the rate-limit to process color values set in the TOS byte of the packet header.

  3. (Optional) Configure the rate-limit actions for traffic flows that:

    • Do not exceed the committed rate and burst size

    • Exceed the committed rate but remain below the peak burst size

    See Configuring Types of Actions for Rate-Limit Actions (SRC CLI).

  4. Enter a description for the parent group.

  5. Step up one level in the edit hierarchy.

  6. (Optional) Configure the parent group to reference an external parent group. For example, to add a reference called epg1-ref:

    • Specify the name of the external parent group that you want to reference. For example, to reference the external parent group epg1:

    • Specify the name of the hierarchical policy parameter for the external parent group. For example, to associate the hierarchical policy parameter called hpp1:

    • Specify the attributes of the hierarchical policy parameter that you are referencing.

      For information about configuring the attributes of the hierarchical policy parameter, see Configuring Hierarchical Policy Parameters for External Parent Groups (SRC CLI).

  7. (Optional) Return to the rate-limit action configuration and verify the configuration.

  8. (Optional) Create another parent group within this parent group. For example:

  9. (Optional) Follow the instructions in this procedure for configuring the parent group.

Configuring Types of Actions for Rate-Limit Actions for External Parent Groups (SRC CLI)

When you configure a rate-limit action or a rate-limit hierarchy, you specify types of actions for conformed traffic, committed traffic, and exceed traffic.

Before you configure the various types of actions, configure the rate limit or parent group (for rate-limit hierarchies) that is to include the actions. See:

Use the following configuration statements to configure rate-limit actions from the [edit policies external-parent-group-folder name external-parent-group name ] hierarchy level:

To specify types of actions for rate-limit actions:

  • Specify an action for a rate-limit action or a rate-limit hierarchy:

    Note

    The following examples show the configuration for a committed action. You can configure the same actions for committed actions, conformed actions, and exceed actions.

    • Filter (drop packet).

    • Forward.

    • (For rate-limit hierarchies only) Forward conditionally.

    • (Rate-limit hierarchies only for committed and conformed actions) Forward unconditionally.

    • (For rate-limit hierarchies only) Forward and exit from the rate-limit hierarchy.

    • Mark. If you select mark, enter the mark values.

      Make sure that masks configured with a rate-limit action are the same for different mark actions.

    • Parameter. Before you assign a parameter, you must create a parameter of the packetOperation type and commit the parameter configuration.

Configuring Hierarchical Policy Parameters for External Parent Groups (SRC CLI)

Use the following statement to configure hierarchical policy parameters for external parent groups:

To configure hierarchical policy parameters for external parent groups:

The hierarchical policy parameter consists of three possible attributes:

  • numeric-aggregation-node—Specifies the JunosE aggregation node numerically in the range of 0 through 65,535. The default value of 0 indicates that the numeric-aggregation-node is not configured.

  • level-aggregation-node—Specifies the level where the specified external parent group needs to be grouped. Set this attribute to one of the values listed in Table 13.

    Table 13: Supported Values for the level-aggregation-node Attribute

    level-aggregation-node

    Notes

    (Default) The level-aggregation-node is not configured.

    Forwarding

    Vlan

    Atm

    Svlan

    When svlan is chosen as the level-aggregation-node, you must also configure the value for the level-aggregation-node-id, which represents the svlanID. The range is from 0 through 4095.

    atm-vc

    atm_vp

    When atm-vp is chosen as the level-aggregation-node, you must also configure the value for the level-aggregation-node-id attribute, which represents the atm-vpId. The range is from 0 through 255.

    Ethernet

    fr-vc

    ppp-interface

    Note

    Set the hierarchical policy parameter to either numeric-aggregation-node or level-aggregation-node. You should configure only one value for this policy parameter; if you configure both values, the level-aggregation-node takes higher priority.

    Note

    Values for the numeric-aggregation-node and level-aggregation-node attributes can be set in the SRC software as global parameters or configured as values directly in an internal parent group or classify-traffic condition.

  • level-aggregation-node-id—Specifies the JunosE aggregation node ID. You specify this parameter only if the level-aggregation-node option is set to svlan or atm-vp. In this case, it is mandatory to set this parameter.

    • When you specify svlan as the level-aggregation-node, this parameter represents the svlanID in the range of 0 through 4095.

    • When you specify atm-vp as the level-aggregation-node, this parameter represents the atm-vpId in the range of 0 through 255.

  1. From configuration mode, specify the name of the external parent group for which you want to configure the hierarchical policy parameter. For example, to configure the hierarchical policy parameter for an external parent group called epg1:

  2. Configure the value for the level-aggregation-node option. For example, to configure the level-aggregation-node for vlan:

  3. (Optional) Configure the value for the level-aggregation-node-id option. For example, to configure the level-aggregation-node-id for 10:

  4. (Optional) Configure the value for the numeric-aggregation-node option. For example, to configure the numeric-aggregation-node for 5:

  5. (Optional) Verify the configuration for the hierarchical policy parameter.