Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Bandwidth Policies and Services for Enterprise Manager Portal

 

You configure bandwidth-on-demand services to make them available through the Enterprise Manager Portal. Topics in this section include:

Bandwidth-on-Demand Services for Enterprise Manager Portal

You can make bandwidth available on demand to IT managers by creating the following types of services:

  • Basic BoD service—Specifies the bandwidth level available to an access link.

  • BoD service—Classifies traffic and assigns a service level that specifies the forwarding treatment for the traffic class.

BoD and basic BoD services allow billing for subscriptions to supplementary services.

You can create services to provide Junos class of service (CoS) or JunosE quality of service (QoS) by configuring BoD and basic BoD services that interact with each other. You can provide different service levels to different traffic by specifying traffic classification criteria.

You can create any number of basic BoD services and any number of BoD services. Only one basic BoD service, but numerous BoD services can be assigned to an access link.

BoD services can be configured to provision bandwidth provided by basic BoD services for a link. For example, you could provide a basic BoD service that provides 1 Mbps to the access link, and two video services as BoD services, each with different characteristics.

When you configure BoD and basic BoD services, they are available to IT managers through Enterprise Manager Portal

Parameter Values Used by BoD Services

Table 12 lists the parameters for which Enterprise Manager Portal provides values. The parameter names start with “bod” (service’s LDAP attribute parameterSubstitution).

Table 12: Parameters for BoD Services for Enterprise Manager Portal

To Specify This Value

Use This Parameter

Protocol

bodProtocol

TOS byte

bodTosByte

TOS byte mask

bodTosByteMask

Source network

bodSrcIp

Source port

bodSrcPort

Destination network

bodDestIp

Destination port

bodDestPort

TCP flags

bodTcpFlags

TCP flags mask

bodTcpFlagsMask

IP flags

bodIpFlags

IP flags mask

bodIpFlagsMask

Fragmentation offset

bodIpFragOffset

Packet length

bodPacketLength

ICMP type

bodIcmpType

ICMP code

bodIcmpCode

Bandwidth Policies for Different Devices

If you support environments that include both JunosE routers and devices running Junos OS, you can configure policies to have policy rules for JunosE filters and Junos OS filters. This way, if the service is activated on a JunosE router, the JunosE rule is used, and if the service is activated on a device running Junos OS, the Junos OS policies are used.

When Enterprise Manager Portal has JunosE compatibility enabled, the portal allows:

  • Single subnets for source and destination addresses

  • Single ports or single port ranges for source and destination ports

In addition, with JunosE compatibility enabled, Enterprise Manager Portal does not show the following configuration fields for BoD services:

  • TCP flags

  • IP flags

  • Fragment offset

  • Packet length

  • ICMP type

  • ICMP code

You should be familiar with the types of bandwidth management policies available for the type of router for which you are configuring policies. See Policy Management Overview.

Configuring Basic BoD Policies

You can create policies with the Policies, Services, and Subscribers CLI or the Policies, Services, and Subscribers subtasks in the C-Web interface.

To configure a basic BoD policy:

  1. Create a policy group and associated policy rules.

    Typically the policy rules include Junos OS schedulers, Junos OS policers, Junos OS filters, or JunosE filters that specify a traffic classification, and basic rules that define best-effort forwarding and drop behavior.

  2. Include parameters in the classify-traffic conditions of the policer. Use parameter names from table Parameters for BoD Services for Enterprise Manager Portal in Parameter Values Used by BoD Services.

  3. Specify a precedence for the policy rules.

    Structure the precedence for policies to ensure that policy rules for Junos OS schedulers and Junos OS policers have a higher precedence, and therefore a lower number, than default policy rules. If the configuration includes BoD services, the policies to support BoD services should have a higher precedence, indicated by a lower number.

For a sample basic BoD policy, see policyGroupName=basicBod, ou=entjunos, o=Policies, o=umc in the sample data.

Configuring Basic BoD Services

You can create services with the Policies, Services, and Subscribers CLI or the Policies, Services, and Subscribers subtasks in the C-Web interface.

Basic BoD services do not have service parameters.

To configure a service that uses basic BoD:

  1. Create a service.

  2. Specify the following values for the service:

    • Category—basicBod (service’s LDAP attribute sspCategory)

    • Description—Description of the bandwidth provided by the service

      If you plan to integrate a basic BoD service with a BoD service, the description for each basic BoD service should explain the bandwidth provided, and the relationship between this bandwidth level and the BoD service. The description should also explain the relationship between the service name, which is shown on the portal in the Bandwidth Level list, and the bandwidth provided. For example, for a service named 1 Mbps, the bandwidth provided could be 1 Mbps downstream and 500 Kbps upstream.

      This description will appear in the online help for Bandwidth Level in Enterprise Manager Portal. Although there is no limit for the length of the text entered, the portal displays the text in one paragraph.

    • Policy Group—Policy group that supports basic BoD services

For a sample BoD service, see serviceName=1.0 Mbps, l=EntJunos, o=Scopes, o=umc in the sample data.

Configuring BoD Policies

When configuring BoD policies, you create rules that classify traffic. Make sure that the source and destination policy rules correspond to location of the enterprise relative to the subscriber interface that the SRC software manages. When configuring Enterprise Manager Portal, you follow the same rules for defining source and destination fields. See Policy Components.

You can create policies with the Policies, Services, and Subscribers CLI or the Policies, Services, and Subscribers subtasks in the C-Web interface.

To configure a BoD policy:

  1. Create a BoD policy group and associated policy rules.

    You can create some policy rules as Junos OS filters and others as JunosE filters.

    Specify values or parameters for the following for each policy rule for the BoD service:

    • TOS byte in the IP header

    • Mask used for the ToS byte

    • Source TCP/UDP port

    • Destination TCP/UDP port

    • IP address of source

    • IP address of destination

    • TCP flags

    • Fragmentation flags

    • Fragmentation offset

    • ICMP type

    • ICMP code

  2. Specify a precedence for the policy rules.

    If the configuration includes basic BoD services, the policies to support basic BoD services should have a lower precedence, indicated by a higher number.

    For information about policy rules and precedences, see Policy Information Model.

For a sample BoD policy, see policyGroupName=bod, ou=entjunos, o=Policies, o=umc in the sample data. In the sample BoD policies, substitutions in services rename policy parameters to names required by Enterprise Manager Portal.

The sample data is based on a scenario that has the SRC managed interface on a device with egress to the access link that leads to the enterprise.

Configuring BoD Services

You can create services with the Policies, Services, and Subscribers CLI or the Policies, Services, and Subscribers subtasks in the C-Web interface.

Note

If you configure BoD services that use forwarding classes, take into consideration the number of forwarding classes supported on the router.

To configure a service for BoD:

  1. Create a service.

  2. Specify the following values for the service:

    • Category—bod (service’s LDAP attribute sspCategory).

    • Description—Description of how this service will affect traffic.

      If you plan to integrate a basic BoD service with a BoD service, the description for each BoD service should take into consideration how the BoD service interacts with any basic BoD service selected. The description should also provide information about the forwarding treatment for traffic.

      This description will appear in the online help for BoD services in Enterprise Manager Portal. Although there is no upper limit for the length of this attribute, the portal will display the text in one paragraph.

    • Substitutions—Substitutions for the parameter names; these names start with “bod” (service’s LDAP attribute parameterSubstitution).

      Note that the actual parameter names are required to be the service parameter names for Enterprise Manager Portal.

    • Policy Group—Policy group that supports BoD services.

For a sample BoD service, see serviceName=Gold, l=entJunos, o=Scopes, o=umc in the sample data.

Using BoD Services to Assign Traffic to Bandwidth Categories

You can use BoD services to assign different classes of traffic to different bandwidth categories, with each category identified by a specified quantity of bandwidth.

For example, a configuration could provide two services:

  • Silver—Bandwidth of 500,000 Mbps

  • Gold— Bandwidth of 1,000,000 Mbps

Each service has the specified bandwidth available to specified traffic flows, based on the policy rules for traffic classification and policing.

Using BoD and Basic BoD Services Together to Supply Class of Service

You can use BoD and basic BoD services together to provide more sophisticated bandwidth level management to IT managers. For example, you can integrate these types of services to take advantage of the CoS features available on devices running Junos OS.

On the device running Junos OS, policers are applied before schedulers. The type of service defined by these settings is applied to traffic exiting from the device running Junos OS. For information about policing, scheduling, and queuing traffic on the device running Junos OS, see Junos OS Network Interfaces and Class of Service Configuration Guide.

If you want to integrate basic BoD services and BoD services, you can base your configuration on the implementation in the sample data, The sample services and data are designed to work with Enterprise Manager Portal and require little configuration.

You can also create a configuration to meet requirements specific to your environment. If you want to create a configuration that has both basic BoD and BoD services, carefully plan services and associated policies. Ensure that the bandwidth requirements for BoD services are in proportion to the bandwidth provided by the basic BoD services for another way to provide BoD to IT managers.

Note

When configuring services to use Junos OS CoS, take into consideration which interfaces on the router support CoS.

Examples: Setting Up Forwarding Preferences

We provide two examples for setting up forwarding preferences.

Setting Up Forwarding Preferences by Using CoS on Devices Running Junos OS

The sample data provides an implementation that supports CoS features on the device running Junos OS. This implementation provides:

  • Basic BoD services to apply a Junos OS policer only to best-effort traffic

  • BoD services to assign traffic to forwarding classes other than best-effort

  • Policing for best-effort traffic

Table 13 lists the services and policies in the sample data. You can locate the services in l=entJunos, o=Scopes, o=umc. You can customize the policies and services as needed. For general information about configuring policies and services, see Configuring Basic BoD Policies and Configuring BoD Policies.

Table 13: Integrated BoD and Basic BoD Services in Sample Data

Name of Service

Category of Service

Name of Policy Group

Description of Service

1.0 Mbps

basic BoD

basic BoD

Specifies that a bandwidth of 1.0 Mbps be available to a specified access link for best-effort traffic.

3.0 Mbps

basic BoD

basic BoD

Specifies that a bandwidth of 3.0 Mbps be available to a specified access link for best-effort traffic.

5.0 Mbps

basic BoD

basic BoD

Specifies that a bandwidth of 5.0 Mbps be available to a specified access link for best-effort traffic.

Silver

BoD

BoD

Marks associated traffic as belonging to an assured forwarding class.

Gold

BoD

BoD

Marks associated traffic as belonging to an expedited forwarding class.

Billing can be established for traffic in the assured forwarding class and in the expedited forwarding class because the SRC software can account for traffic in each of these forwarding classes separately from other forwarding classes. Traffic in the assured forwarding class and in the expedited forwarding class is not included in the accounting data for the currently selected basic BoD service.

Setting Up Forwarding Preferences by Allocating a Percentage of a Link’s Bandwidth to a Service

The following example shows another way to use BoD and basic BoD services to provide BoD services. In this example, a percentage of an access link’s bandwidth is allocated to a specified service.

This configuration provides:

  • Three bandwidth levels available to access links: 1.0 Mbps, 1.5 Mbps, and 2.0 Mbps.

  • Three service levels defined to use a specified percentage of the bandwidth set for the access link: best effort 20%, Silver 30%, and Gold 50%.

    Each traffic class uses only the bandwidth assigned to it and does not share bandwidth with other traffic classes.

For an SRC configuration to support this scenario, you could create policies such as the following and assign these policies to services:

  • Policies that provide a local policy parameter, bw, whose value is set by the service that references the policy:

    For policy 1.0 Mb, bw=1000000

    For policy 1.5 Mb, bw=1500000

    For policy 2.0 Mb, bw= 2000000

  • The transmission rate, bandwidth allocation, and priority scheduling for specified forwarding classes as shown in Table 14.

    Table 14: Policies to Specify Forwarding Treatment for Specified Traffic Classes

    Forwarding Class

    Transmission Rate

    Exact

    Priority Scheduling

    Best effort

    bw*0.2 bps

    true

    Low

    Silver (assured forwarding)

    bw*0.3 bps

    true

    Medium

    Gold (expedited forwarding)

    bw*0.5 bps

    true

    High

By setting exact to true, you can ensure that the sum of the transmission rates is less than the bandwidth allocated to the access link.