Aggregate Service Fields for Mirroring Traffic

Use the fields in this section to configure aggregate services in the Service Fragment dialog box.

Expression

Subscriber reference expression to specify each mirroring router in the subscriber’s traffic paths and the interface name used to activate the service.
Value—vr="<- substitution.vrNames ->", interfaceName="FORWARDING-INTERFACE"
- FORWARDING-INTERFACE is used to activate the fragment service for the forwarding table. The vrNames substitution must be defined in each separate POP-specific scope.

Service

Mandatory

Specifies whether the fragment service is mandatory.
Value
- false
  - If there is a redundancy group, the application will show the mirroring task as pending until one of the mirroring routers becomes manageable by the SAE.
  - If there is no redundancy group, the application will show the mirroring tasks as pending only when it cannot contact the SAE managing the subscriber.
- true—The application will show the mirroring task as pending until the SAE can activate the fragment service on all the mirroring routers.

Redundancy Group

Group identifier for a redundant service.
Value—Text
Guidelines—Applicable only when Mandatory is false. If there is a redundancy group, then the mirroring task is considered active if the mirroring fragment is activated on at least one of the mirroring routers.

Subscription

Specifies whether a remote subscriber session is required to subscribe to the fragment service.
Value—False.

Substitutions

List of IP addresses for subscribers.
Value—fragSubrIps=subrIps
Guidelines—Note that the fragSubrIps parameter is for the fragment service and can be changed to match the parameter used for the policy in Step 1 of Configuring Services. The subrIps parameter is for the aggregate service and cannot be changed. This substitution is used to resolve the value of the IP address in the context of a subscriber session and to pass the correct value to the fragment service.