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:
- From configuration mode, enter the service aggregate configuration. In this sample procedure, the service called MirrorAggregate is configured in the scope configuration.
- Configure the subscriber reference expression that identifies the remote subscriber session that will host the fragment.
- Configure the name of the service to be included in the aggregate service as a fragment service.
- (Optional) Specify whether the fragment service must be active for the aggregate service to become active.
- (Optional) Configure the group name to be applied to each fragment service that is to be part of a redundancy group.
- (Optional) Specify whether a remote subscriber session is required to subscribe to the fragment service.
- (Optional) Configure the list of substitutions that are used as arguments for the fragment to become active.
- (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;

