Using The Deactivate-Service Attribute; Using Mutex Groups To Activate And Deactivate Subscriber Services - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

JunosE 11.3.x Broadband Access Configuration Guide

Using Mutex Groups to Activate and Deactivate Subscriber Services

658
the service-volume threshold. Instead, Service Manager checks the volume in 10-second
intervals and deactivates a service session at the end of the 10-second period in which
the output byte count reaches the volume threshold. For example, if a threshold is
reached 4seconds into the 10-second interval, the session continues for the remaining
6 seconds in the measuring period and is then terminated. Therefore, the total volume
equals the threshold plus the volume during the additional 6 seconds.
When the output byte count reaches the threshold, RADIUS deactivates the service
session. You must use tags to associate threshold attributes with the Activate-Service
attribute for the service session.

Using the Deactivate-Service Attribute

You can also include the Deactivate-Service attribute in the subscriber's RADIUS record.
The format for this attribute is the same as the format of the Activate-Service
attribute—the name of the service, including parameters. The Deactivate-Service attribute
is used by RADIUS CoA messages, such as in a guided entrance service. See "Guided
Entrance Service Example" on page 684 for more information.
Service Manager supports two methods that use RADIUS CoA-Request messages to
activate and deactivate subscriber services and that can also dynamically change a
service that is currently provided to a subscriber.
In the first method, you use a CoA message with the Activate-Service VSA to activate
the new service; you can optionally include the Deactivate-Service VSA to deactivate
the subscriber's existing service. This method is described in "Using RADIUS to Activate
Subscriber Service Sessions" on page 653.
The second method uses mutual exclusion (mutex) groups to create mutex services.
With this method, you group services together in a mutex group. When you use a CoA
message to activate a service that is in a mutex group, Service Manager activates the
new service and implicitly deactivates any existing service that it is a member of the same
mutex group as the newly activated service. Service Manager does not deactivate an
existing service that is a member of a different mutex group or is not a member of a mutex
group.
Using mutex services results in an more reliable activation and deactivation process than
the original CoA-Request method. With mutex services, Service Manager always activates
the new service before deactivating the existing service. This ensures that the subscriber
is never without an active service. In the original CoA-Request method, the order of
activation and deactivation is random—in some cases the existing service might be
deactivated before the new service is activated, or the new activation might fail. In these
cases, the subscriber might be without an active service.
If statistics are enabled when you activate a mutex service, Service Manager sends a
RADIUS Acct-Stop message for the deactivated service.
Copyright © 2010, Juniper Networks, Inc.