[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Example: Parameter Value Substitution

This section provides an example of how to use parameters and substitutions. It contains the following sections:

Setting Up a Service That Uses Parameters

In this example, we will create a value-added service that provides a gold-level quality of service. We will then subscribe this service to a department subnet in an enterprise network and be able to track and charge the department for the volume of bandwidth used. Figure 43 shows the network in our example.


Figure 43: Network Used in Parameter Substitution Example

From the service provider's perspective, the service provider's network is on the inside, and the enterprise network is on the outside. Ingress traffic flows from the enterprise network to the service provider's network. Egress traffic flows from the service provider's network to the enterprise network. The engineering department subnet in the enterprise network is the subnet that we will subscribe to the gold-level service and track.

The example uses two types of parameters (note that SDX Admin uses the term role in place of type):

Summary of Procedure

The following is a summary of the procedure we will use to set up the example.

  1. Create a policy group called tierpolicy that classifies packets based on source and destination subnets and applies a rate limit action to those packets. The tierpolicy policy group contains three local parameters:
  1. Create a value-added service called GoldMetered, and assign tierpolicy as the policy group. In the GoldMetered service, configure the following parameter substitution:
  1. Create an enterprise subscriber, and configure the following parameter substitution:
  1. Subscribe the subscriber to the GoldMetered service, and configure the following parameter substitution:

Creating a Policy Group

Use Policy Editor to create a policy group.

  1. Create a policy group called tierpolicy.
  2. Create the following local parameters, which are parameters that will be used only with tierpolicy.
  1. Create two policy lists, one for the ingress side of the interface, and one for the egress side of the interface.
  2. Create two policy rules, one for ingress traffic and one for egress traffic.
  3. In the egress policy rule, which applies to traffic coming from the service provider network to the enterprise, create a condition that matches IP packets on source and destination networks:
  1. Also in the egress policy rule, create a rate-limit action that does the following:
  1. In the ingress policy rule, which applies to traffic coming from the enterprise network, create a condition that matches IP packets on source and destination networks:
  1. Also in the ingress policy rule, create a rate-limit action that does the following:

The policy group should now look like this:

Creating a Value-Added Service

Use SDX Admin to create a value-added service.

  1. Create a value-added service called GoldMetered, and assign tierpolicy as the policy group.
  2. Select the Parameter tab of the GoldMetered service, and add the following parameters to the substitution table:

Creating an Enterprise Subscriber

The next step is to create an enterprise subscriber. Within the subscriber definition, create a parameter called eng that is parameter type (role) network, and set the value of eng to 192.0.2.22/28.

You create a subscriber by using SDX Admin or another directory client. You can create the eng parameter with SDX Admin or the sample enterprise service portal.

  1. In SDX Admin, create an enterprise subscriber called ABCInc.
  2. Create the eng parameter as part of the subscriber definition. You can perform this step by using either SDX Admin or the sample enterprise service portal.

Subscribing ABCInc to the GoldMetered Service

Next, subscribe the ABCInc subscriber to the GoldMetered service. You can perform this step by using SDX Admin or the sample enterprise service portal.

In the sample enterprise service portal:

  1. Select ABCInc. in the navigation pane.
  2. Select the Services tab.

The Services pane appears.

  1. Click Subscribe in the GoldMetered service row.
  2. Select the Subscriptions tab.

The Subscriptions pane appears.

  1. In the dept= field of the Service Parameters box, set the value of the dept parameter to eng.

Acquiring the Parameter Values

Once the SRC software has gone through the parameter value acquisition process, the three original parameters in the tierpolicy policy group have the following values:

This value was acquired from the global parameter any that was defined in the service definition.

This value was acquired as follows:

This value was acquired from the service definition where the value of qos was set to 50% of the interface_speed parameter. An interface_speed value of 1,000,000 was acquired from the router. If qos=50% of the interface speed, then the qos value is 500,000.

The rest of the rate-limit values are calculated based on the 500,000 value of qos.

Figure 44 shows the values of the ingress and egress policies that are applied to the router in our sample network.


Figure 44: Policies Applied to the Sample Network

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]