cisco — Control Policy Configuration Overview

The figure below illustrates how each control policy contains a list of events that are considered applicable to the subscriber life cycle. Within each event type is a list of control classes with different match criteria for subscriber identity, and under each class is a list of actions to be executed. Figure 1: Control Policy Structure Control Policy Configuration Overview Control policies express system functionality in terms of an event, a condition, and an action. There are three steps in defining a control policy: 1. Create one or more control classes—A control class specifies the conditions that must be met for a control policy to be activated.

A control class can contain multiple conditions, each of which will evaluate as either true or false. Match directives specify whether all, any, or none of the individual conditions must evaluate true for the class to evaluate true. Or, you can specify the default control class which does not contain any conditions and always evaluates true. 2. Create a control policy—A control policy contains one or more control policy rules. A control policy rule consists of a control class, an event that causes the class to be evaluated, and one or more actions. Actions are numbered and executed sequentially. 3. Apply the control policy—A control policy is activated by applying it to an interface.

Configuring Identity Control Policies Control Policy Configuration Overview Configuring Identity Control Policies 3