Juniper JUNOSE 11.0.X MULTICAST ROUTING, Руководство по настройке

Страница: 701 / 788

attribute is used by RADIUS CoA messages, such as in a guided entrance service.
See “Guided Entrance Service Example” on page 687 for more information.
Using Mutex Groups to Activate and Deactivate Subscriber Services
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 655.
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.
Activating and Deactivating Multiple Services
The Service Manager mutex service feature enables you to activate and deactivate
multiple services with a single CoA-Request message. A CoA-Request message can
have more than one service activation request—the multiple service requests might
be from the same mutex group or from different groups. The following examples
describe how you might use mutex groups to activate and deactivate multiple services.
■
Example 1—Multiple mutex services of the same mutex group
Service Manager activates the multiple mutex services, which are in the same
group, then deactivates all previously existing services that are also members of
that mutex group. Active services that are members of different mutex groups
are unaffected.
■
Example 2—Multiple mutex services of different mutex groups
Service Manager activates the mutex services, which are members of different
mutex groups. Service Manager then deactivates all previously existing services
that are members of the same mutex groups as any of the newly activated
Using Mutex Groups to Activate and Deactivate Subscriber Services
■ 661
Chapter 27: Configuring Service Manager