> - Downloads
> - Configuring Service Fragments for an Aggregate Service (SRC CLI)
> - Related Topics
> - Overview of SRC Aggregate Services
> - How Parameters Are Passed from Aggregate Service to Fragment Service
> - Configuring Service Fragments for an Aggregate Service (C-Web Interface)
> - Using Python Expressions in a Subscriber Reference Expression

> # Configuring Service Fragments for an Aggregate Service (SRC CLI)

> Use the following configuration statements to configure an aggregate service in the global service scope:

> `
> services global service name aggregate fragment name {
>   expression expression ;
>   service service ;
>   mandatory;
>   redundancy-group redundancy-group ;
>   subscription-required;
>   substitution [ substitution... ];
> }
> `

> Use the following configuration statements to configure an aggregate service in a service scope:

> `
> services scope name service name aggregate fragment name {
>   expression expression ;
>   service service ;
>   mandatory;
>   redundancy-group redundancy-group ;
>   subscription-required;
>   substitution [ substitution... ];
> }
> `

> To configure service fragments for an aggregate service:

> 1. From configuration mode, enter the service aggregate configuration. In this sample procedure, the service called MirrorAggregate is configured in the scope configuration.
>    `
>    user@host# edit services scope TM service MirrorAggregate aggregate fragment 0
>    `
> 2. Configure the subscriber reference expression that identifies the remote subscriber session that will host the fragment.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set expression expression
>    `
> 3. Configure the name of the service to be included in the aggregate service as a fragment service.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set service service
>    `
> 4. (Optional) Specify whether the fragment service must be active for the aggregate service to become active.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set mandatory
>    `
> 5. (Optional) Configure the group name to be applied to each fragment service that is to be part of a redundancy group.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set redundancy-group redundancy-group
>    `
> 6. (Optional) Specify whether a remote subscriber session is required to subscribe to the fragment service.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set subscription-required
>    `
> 7. (Optional) Configure the list of substitutions that are used as arguments for the fragment to become active.
>    `
>    [edit services scope TM service MirrorAggregate aggregate fragment 0]
>    user@host# set substitution [ substitution... ]
>    `
> 8. (Optional) Verify your configuration.

>        [edit services scope TM service MirrorAggregate aggregate fragment 0]
>        user@host#  show
>        expression
>        "vr=\"<- substitution.vrNames ->\", interfaceName=\"FORWARDING_INTERFACE\"";
>        service MirrorFragment;
>        substitution fragSubrIps=subrIps;

> #### Published: 2009-09-22

> Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.