Use the following procedure to configure the global controller with a different rate per link.

In this link control mode, the maximum bandwidth is the sum of links but bandwidth settings can be configured for each link up the maximum bandwidth for all links. When you create a GC in this mode you can configure the aggregate global controller of the link and in addition specify a bandwidth limitation per link. This mode is used when the Cisco SCE serves multiple edge devices and you want to enforce two rules: One aggregate rule on all the links together and one rule per specific link. In this mode, you can enforce bandwidth limitation on the sum of all links and enable separate bandwidth settings for each link. You can control the links in aggregate and set maximum rate per-link which is different between the links.

Use the following procedure to configure global controller as the sum of all links with a different rate per link.

In this link control mode, the maximum bandwidth limitation is configured as sum of all links. When you create a GC in this mode, you can configure the aggregate global controller of the link and configure the maximum rate per link. In this mode, you can enforce bandwidth limitation on the sum of all links and control the links in aggregate and in addition maximum per-link which is equal between all links.

Use the following procedure to configure global controller as the sum of all links with an equal rate per link.

Use the following procedure to configure the global controller with equal rate for all links.

In this mode, you can control each link separately using configured rate templates and default rates. The template rate limits are applied to newly created virtual links. The default rate limits are applied to the default virtual link (virtual link 0).

The Subscriber BW Controllers tab of the Package Settings dialog box has the following configuration parameters:

• Name—A unique name for each BWC.
• CIR (L3 Kbps)—The minimum bandwidth that must be granted to traffic controlled by the BWC.
• PIR (L3 Kbps)—The maximum bandwidth allowed to traffic controlled by the BWC.

  Note	The minimum bandwidth for a subscriber BWC is 16 Kbps with a granularity of 1 Kbps and the maximum bandwidth is 1000000 Kbps.

• Global Controller—The global controller with which this BWC is associated. The global controllers are virtual queues that are part of the bandwidth control mechanism. Direct traffic with similar bandwidth control properties to the same global controller.
• Assurance Level—How fast bandwidth either decreases from the PIR to the CIR as congestion builds or else increases from the CIR to the PIR as congestion decreases. A higher AL ensures a higher bandwidth compared to a similar BWC with a lower AL. The lowest assurance value is 1, the highest is Persistent (10).

  Assurance Level 10 (persistent) never goes below the relevant CIR, unless the total line rate cannot sustain this value.

• Subscriber relative priority—Assurance Level given to the Primary BWC of the subscriber. It determines the assurance given to all the subscriber traffic when competing for bandwidth with subscribers to other packages. The lowest value is 1; the highest is 10.

Note	Subscriber bandwidth control (and accounting and reporting) is based on Layer 3 volume. Global controller bandwidth is based on Layer 1 volume.

You can configure a rule, BWC, and GC together from the Global Policy window.

You can configure the upstream configuration of the global bandwidth controller for IPv6 from the Global Policy window. For details on managing the bandwidth, see the Introduction to Managing Bandwidth“Managing Bandwidth” section.

Relative priority is the level of assurance that an internal BWC (iBWC) receives when competing against other iBWCs for bandwidth.

The relative priority of one of the following modes determines the relative priority of the flow that goes through an iBWC:

• The iBWC—In Global Prioritization Mode
• The subscriber—In Subscriber Prioritization Mode

To use virtual links, you must enable Virtual Links mode.

Note	If you enable or disable Virtual Links mode, all user-defined global controllers are deleted from the service configuration.

The following steps outline configuring a service configuration in Virtual Links mode. The procedure is similar to that for configuring any service configuration, but virtual links must be added using the CLI.

You can limit the total bandwidth passing through the physical link.

The total link limits for upstream and downstream traffic are defined independently.

In Virtual Links mode, bandwidth limitations are applied to the sum of all links.

The following parameters define a package:

• General parameters:
  • Package Name—A unique name for the package
  • Description—(Optional) A description of the package
• Quota Management parameters:
  • Quota Management Mode—Specifies how the subscriber quotas are managed—by external quota manager or replenished periodically by Cisco SCA BB.
  • Aggregation Period Type—The quota aggregation period used when quotas are replenished periodically.
  • Quota Buckets—16 resource buckets used for quota management.
• Subscriber BW Controllers parameters:
  • Subscriber relative priority—The relative priority given to subscribers of the package at times of Network congestion.

    Separate priorities are defined for upstream and downstream flows.

  • Subscriber Bandwidth Controllers—A list of BW controllers (BWCs) that are available to services that are part of the package. Various parameters are defined for each BWC, including a mapping to a global controller.

    Separate BWCs are defined for upstream and downstream flows.

• Advanced parameters:
  • Package Index—The unique number by which the system recognizes a package. Changing the package name does not affect Cisco SCE platform activity. The system provides a default value of the package index. Do not modify this value.
  • Parent Package—The package one level higher in the package hierarchy. The parent package is important when packages share usage counters. The default package is the base of the package hierarchy, and does not have a parent.
  • Package Usage Counter—Used by the system to generate data about the total use by each package. A package can use either an exclusive package usage counter or the package usage counter of the parent package.

    Each usage counter has:

    • A name assigned by the system (based on the package name).

      Note	An asterisk is appended to a package usage counter name whenever the counter applies to more than one package.

    • A unique counter index—The system provides a default value of the counter index. Do not modify this value.
    • Calendar—The calendar used as the basis for the time-based rules of the package.
    • VAS Traffic Forwarding Table—The forwarding table used by the package.

These parameters are defined when you add a new package (see Adding Packages section). You can modify them at any time (see Editing Packages section).

You can view a hierarchy tree of all existing packages, and you can see a list of services for which specific rules are defined for any selected package.

A default package is predefined in the Console installation. You can add additional packages to a service configuration, subject to the limit of 5000 packages per service configuration.

After you have added a new package, you can define rules for the package (see Adding Rules to a Package section).

You can change the index for the package, specify an exclusive usage counter, or select a calendar for the package in the Advanced tab.

Duplicating an existing package is a useful way to create a new package similar to an existing package. It is faster to duplicate a package and then modify it than to define the package from beginning.

A duplicated package is added at the same level in the package tree as the original package.

You can modify the parameters of a package (including the default package) at any time.

You can delete user-defined packages. The default package cannot be deleted.

To add the Add-on Groups, follow the below procedure:

To create an Add-on Template, follow the below procedure:

To create a Package combination, follow the below procedure:

You can view a list of the rules of a package.

The listing for each rule includes an icon, the name of the service or group of services to which the rule applies, whether the rule is enabled or disabled, and a brief description of the rule.

A default service rule is assigned to every package. You can add additional rules to a package.

Adding time-based rules is described in the section How to Add Time-Based Rules to a Rule.

The Control tab of the Add New Rule to Package dialog box allows you to set behavior per traffic flow for sessions that are mapped to the current service.

You can edit any rule, including the default service rule.

Note	You cannot disable the default service rule.

Note	The tabs of the Edit Rule for Service dialog box are the same as the tabs of the Add New Rule to Package dialog box, except for the General tab—you cannot change the service to which the rule applies.

You can delete any user-defined rule. The default service rule cannot be deleted.

Note	You can disable a rule without losing its profile. For details, see Step 4 of “How to Edit Rules” section. This feature allows you to enable the rule again later, without having to reset all its parameters. You cannot disable the default service rule.

You can define a service as the child of another service (the parent service is a service group).

Until you define a separate rule for a child service, the rule of the parent service applies to the child service. A rule that affects any of child services of a service is indicated in the rules list by a different icon, as illustrated for the P2P rule and the FTP rule in.

Figure 52. Rules

You can display all (child) services that are affected by a rule.

Note	The default service rule applies to all services for which a specific rule is not defined.

You can add and define new profiles and edit existing profiles. Additionally, you can add up to 16 new buckets.

You also define the quota buckets associated with the package. Rules can use quota buckets to set limits to the consumption of particular service groups (see “How to Select Quota Buckets for Rules” section).

You can edit the profiles to update the bucket profile.

Note	You cannot edit or remove the default profile.

You can define whether an external quota manager or the Cisco SCA BB performs the quota management for a package.

Select the quota buckets that the flows mapped to a rule uses. The quota buckets are defined during package setup (see “How to Edit Quota Management Settings for Packages” section ). If no quota bucket is appropriate for the rule, add a new quota bucket to the package or edit an existing bucket.

You can define the Cisco SCE platform behavior when an aggregated volume limit or the total number-of-sessions limit is exceeded. You can also notify subscribers when they exceed their quotas.

Tiered subscriber services can be implemented using the Cisco SCA BB Console. Because the definition of such services is open ended, this section describes how to define two of the tiers outlined in the value proposition description. The two tiers are defined as follows:

• Silver
  • Weekly bandwidth limited to 4.2 GB (corresponds to a daily limit of 600 MB)
  • Email and browsing services are limited to 256 kbps
  • Audio and video streaming services are limited to 64 kbps
  • P2P services are limited to 28 kbps
• Gold
  • Weekly bandwidth limited to 5.6 GB (corresponds to a daily limit of 800 MB)
  • Email and browsing services are not bandwidth limited
  • Audio and video streaming services are limited to 128 kbps
  • P2P services are limited to 28 kbps

The following steps are applicable to both the 'Silver' and 'Gold' packages.