Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
    null
Find Matches in This Book
Available Languages

Results

Updated:
November 30, 2017

Chapter: Override Control Support for Group-of-Ruledef

Override Control Support for Group-of-Ruledef

This chapter describes the following topics:

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

  • GGSN

  • P-GW

Applicable Platform(s)

  • ASR 5500

  • VPC - Di

  • VPC - Si

Feature Default

Disabled - Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

  • Command Line Interface Reference

  • GGSN Administration Guide

  • P-GW Administration Guide

Revision History

Important:

Revision history details are not provided for features introduced before releases 21.2 and N5.5.

Revision Details

Release

With this feature enhancement, to apply override control appropriately, override control subscriber map is identified by ruledef and group of ruledefs both. A new CLI command align-with-gor is added in rulebase for the same purpose.

21.3

First introduced.

Pre 21.2

Feature Changes

With this feature enhancement, to apply override control appropriately, ruledef, and group of ruledefs both identifies the override control subscriber map. A new CLI command align-with-gor has been added in rulebase for the same purpose.

Old Behavior:

  1. Earlier, names of ruledefs present in the group-of-ruledefs were not supposed to be same as that of the independent ruledefs. Also, same ruledefs were not supposed to be part of two different group-of-ruledefs.

  2. Exclusion of individual ruledef from override-control parameters was applied to the same ruledef under group-of-ruledefs.

New Behavior:

  1. Now, overlapping of ruledef names across the group-of-ruledefs and standalone ruledefs is allowed.

  2. Exclude-rule received in charging-action or wildcard level override control is applied only to the standalone ruledef or group-of-ruledefs. It is not applied to the rule present inside the GOR.

Configuring align-with-gor Override Control

To enable this feature enhancement, you must configure the align-with-gor along with the override-control CLI command in the rulebase. This CLI keyword when enabled, populates the override control subscriber map with the group information. If group-id is present, it is associated with the ruledef-id.

Once enabled, commit the feature by executing update active-charging override-control rulebase-config. 

configure
     active-charging service <service_name>
        rulebase <rulebase_name>
            override-control [ align-with-gor | with-oc-name [ align-with-gor ] ]
												[ default | no ] override-control [ align-with-gor ]
            end
Notes:

  • default: Configures this command with its default setting. By default, this feature is disabled.

  • no: If previously enabled, disables override control in the current rulebase.

  • align-with-gor: Resolves ambiguity when same ruledefs are defined in multiple Groups of Ruledefs.

  • with-oc-name: Uses the override control name as unique key to identify override control for a session.

Upgrading and Downgrading Information

This section covers the upgrade and downgrade procedures.

Consider the following two configurations:

Configuration A:

GoR G1: R1, R2

GoR G2: R1', R2'

Configuration B:

GoR G1: R1, R2

GoR G2: R1, R2

Currently, configuration A is used to make sure that correct "Charging Action' is applied with application of the override control.

Upgrade Procedure:

Consider two chassis(Active Chassis and Standby Chassis) having StarOS 21.3 installed with configuration A. To upgrade the configuration from 21.3 to 21.4, perform the following steps:
  1. Upgrade Standby to StarOS 21.4.

  2. Perform ICSR switch over.

  3. Upgrade the new Standby to StarOs 21.4.

  4. Perform ICSR switch over.

  5. Enable the feature CLI "override-control align-with-gor" in the rulebase.

  6. Remove the 21.3 workaround, apply new configuration, where same ruledef can be part of multiple GOR, that is, Configuration B on Active and Standby chassis. For updating or deleting chassis ruledef, existing MOP procedure must be used. Note: If the override control was received for R1' and R2', it would not be applied as we remove R1' and R2'.

  7. Commit the feature by executing the CLI command, "update active-charging override-control rulebase-config."

  8. Wait for 20 minutes to ensure smooth transition.

Downgrade Procedure:

Consider two chassis(Active Chassis and Standby Chassis) having StarOS 21.4 installed with configuration B (after optimized configuration). To downgrade the configuration from 21.4 to 21.3, perform the following steps:

  1. Change configuration on both the chassis to configuration A, where same ruledef are not part of the multiple GOR. For updating or deleting ruledef, existing MOP procedure must be used.

  2. Disable the feature by executing the CLI command, "no override-control align-with-gor" in the rulebase.

  3. Commit the new configuration by executing the CLI command "update active-charging override-control rulebase-config."

  4. Wait for 20 minutes to ensure smooth transition.

  5. Downgrade StarOS release 21.4 on Standby chassis to StarOS release 21.3.

  6. Perform ICSR switch over.

  7. Downgrade StarOS release 21.4 on new standby to StarOS release 21.3.

  8. Perform ICSR switch over.

Feature turn on and turn off Procedure

This section covers steps to turn the feature ON and OFF.

Feature is ON and must be turned OFF.

Consider a scenario where the chassis has configuration B(after optimized configuration) and the feature CLI "override-control align-with-gor" is configured in the rulebase. When the feature is ON, to turn it OFF, perform the following steps:

  1. Change the configuration to Config A.

  2. Verify if the configuration is aligned with the following:

    Ruledef R1 present in the rulebase is not present in any group-of-ruledefs, where the group-of-ruledefs must be disjoint.

  3. Disable the feature using the CLI command, "no override-control align-with-gor" in rulebase.

  4. Commit the new configuration by executing the CLI command "update active-charging override-control rulebase-config.

  5. Wait for 20 minutes to ensure smooth transition.

Feature is OFF and must be turned ON.

Consider a scenario where the chassis has configuration A and the feature CLI "override-control align-with-gor" is configured in the rulebase. When the feature is OFF, to turn it ON, perform the following steps:

  1. Remove the StarOS 21.3 workaround, wherein the new configuration, where the same ruledef can be part of multiple GOR is applied to both active and standby chassis. For updating or deleting ruledef, existing MOP procedure must be used. Note: If the override control was received for R1' and R2', it would not be applied as we remove R1' and R2'.

  2. Commit te feature by executing the CLI command "update active-charging override-control rulebase-config."

  3. Wait for 20 minutes to ensure smooth transition.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco