Configuring A Mutex Service - Juniper JUNOSE SOFTWARE 11.2.X - BROADBAND ACCESS CONFIGURATION GUIDE 7-20-2010 Configuration Manual

Software for e series broadband services routers broadband access configuration guide
Table of Contents

Advertisement

Configuring a Mutex Service

Copyright © 2010, Juniper Networks, Inc.
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 services. Active
services that are members of different mutex groups are unaffected.
To configure and enable a mutex service, you complete the following steps:
Create the new service definition and configure the service as a member of a mutex
1.
group.
When you create the service definition, include the following service attribute in the
service definition, where groupIndex identifies the mutex group for this service. The
groupIndex can be a number in the range -1 to - 2147483647 or 1 to 2147483646. If
the groupIndex is outside of the acceptable ranges, or if you do not include the
mutex-group statement, the service is not included in a mutex group.
<# env.setResult("mutex-group", "groupIndex" ) #>
For example (the mutex group attribute is highlighted in bold text):
!parameterizes input and output bandwidth
<# tiered(inputBW, outputBW) #>
<# uid := app.servicemanager.getUniqueId #>
<# name := "SM-tiered-" $ uid #>
<# oname := "SM-O-tiered-" $ uid #>
classifier-list matchAll ip any any
rate-limit-profile <# name #> one-rate
committed-rate <# inputBW; '\n' #>
policy-list <# name; '\n' #>
classifier-group matchAll precedence 10000
rate-limit-profile <# name; '\n' #>
traffic-class best-effort
policy-list <# oname; '\n' #>
classifier-group matchAll precedence 10000
traffic-class best-effort
profile <# name; '\n' #>
ip policy secondary-input <# name #> statistics enabled merge
ip policy output <# oname #> statistics enabled merge
qos-profile triplePlayIP
qos-parameter maxSubscBW <# outputBW; '\n' #>
Chapter 27: Configuring Service Manager
649

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.2

Table of Contents