Configuring a Mutex Service

To configure and enable a mutex service, you complete the following steps:

  1. Create the new service definition and configure the service as a member of a mutex 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' #>
    <# env.setResult("mutex-group", “12” ) #> 
    <# env.setResult("activate-profile", name) #>
    <# env.setResult("secondary-input-stat-clacl", "matchAll") #>
    <# env.setResult("output-stat-clacl", "matchAll") #>
    <# endtmpl #>
  2. Activate the mutex service

    Use a RADIUS COA-Request message and the new service definition to create the mutex service. The new service is considered a mutex service because it belongs to a mutex group.

    Service Manager activates the new service and deactivates any existing active service that is a member of the same mutex group as the new service.

  3. (Optional) Verify the status of the new service.
    host1# show service-management subscriber-session client1@isp.com interface ip 192.168.0.1
    User Name: CLIENT1@ISP.COM, Interface: ip 192.168.0.1
     Id: 1
     Owner: AAA 4194326
     Non-volatile: False
     State: Active
     ServiceSessions:
           Name             mutex  Owner/Id     State              Operation
    ----------------------- -----  ----------- ------------------  ---------
    tiered(2000000,3000000)  12   AAA 4194326  ConfigApplySuccess  Activate
           Name             Non-volatile
    ----------------------- ------------
    tiered(2000000,3000000)   False
    

Related Documentation