Dynamic services data trigger capture SAP

In the same way as an Enhanced Subscriber Management (ESM) capture SAP is configured, a dynamic services data trigger capture SAP is configured in a VPLS service and captures frames for authentication. A dynamic service data trigger capture SAP does not forward traffic within the VPLS service, and no MAC learning occurs.

A VPLS capture SAP becomes a dynamic services data trigger capture SAP when a dynamic services policy is configured and the dynamic-services context is enabled (no shutdown). The dynamic services policy specifies the authentication mechanism to be used as detailed in the authentication sections below.

For example:

configure
    service
        vpls 10 customer 1 create
            sap 1/1/4:1214.* capture-sap create
                description "Dynamic Services Data Trigger capture-sap"
                dynamic-services
                    dynamic-services-policy "dyn-svc-1"
                    no shutdown
                exit
                no shutdown
            exit
            no shutdown
        exit
    exit

The trigger-packet type needs to be configured. A dynamic services data trigger capture-sap captures any valid Ethernet frames, including non-IP frames.

Valid dynamic services data trigger capture SAPs are:

dot1q-encapsulated Ethernet, anchoring, satellite ports or LAGs
- sap x/y/z:*
- lag-x:*
- pxc-x.a:*
- esat-x/y/z:*
qinq-encapsulated Ethernet, anchoring, satellite ports or LAGs:
- sap x/y/z:*.*
- sap lag-x:*.*
- sap x/y/z:tag.*
- sap x/y/z:*.tag
- sap lag-x:tag.*
- sap lag-x:*.tag
- pxc-x.a:*.*
- pxc-x.a:tag.*
- esat-x/y/z:*.*
- esat-x/y/z:tag.*

Enhanced Subscriber Management (ESM) and dynamic services data trigger cannot be enabled simultaneously on a single capture SAP: a no shutdown command of the dynamic-services CLI context is mutually exclusive when configuring an ESM trigger-packet type.

Use the following CLI commands to display capture SAP statistics:

To display the number of data trigger packets forwarded to the CPM and dropped on the IOM:

# show service id <service-id> sap <sap-id> sap-stats
===============================================================================
Service Access Points(SAP)
===============================================================================
--- snip ---
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Last Cleared Time     : N/A
                        Packets                 Octets
CPM Ingress           : 108                     6696
Forwarding Engine Stats
Dropped               : 6144                    405504

Table: Data trigger packets forwarded/dropped counters
Counter	Description
CPM Ingress	Number of dynamic service data triggers received on the capture SAP that are forwarded to CPM
Forwarding Engine Stats Dropped	Number of dynamic service data triggers is received on the capture SAP that are dropped on IOM

To display the dynamic services capture SAP control plane statistics (data triggers received and data trigger drop reason counters):

# show service id 10 dynamic-services capture-sap 1/1/4:1214.* statistics
===============================================================================
Dynamic Services Capture SAP 1/1/4:1214.* Statistics
===============================================================================
Data packets received by SAP                               : 3
-------------------------------------------------------------------------------
Drop Reason Counters
-------------------------------------------------------------------------------
No policy configured at capture SAP level                  : 0
No authentication configured in policy                     : 0
Data-trigger already exists                                : 0
Lockout is active                                          : 0
Reached data-trigger system limit                          : 0
No memory available                                        : 0
Unsuccessful authentication                                : 1
No data-trigger SAP-id in authentication                   : 0
Corresponding dynamic SAP is not created                   : 0
===============================================================================

Table: Data triggers received/dropped reason counters
Counter	Description
Data packets received by SAP	Number of dynamic service data triggers received on the capture-sap that reached the CPM
No policy configured at capture SAP level	No dynamic services policy configured at the capture-sap; required to determine the authentication destination.
No authentication configured in policy	The authentication section in the specified dynamic services policy is missing or incomplete.
Data-trigger already exists	A new data trigger frame is received for an existing data trigger that is authenticated, but the corresponding dynamic SAP is not yet created. The new data trigger packet is dropped.
Lockout is active	The data trigger for this managed SAP is currently in a lockout state because of previous authentication failures.
Reached data-trigger system limit	The maximum number of dynamic service data triggers supported on the system is reached. Additional data triggers are dropped.
No memory available	There is not enough system memory available to process the data trigger.
Unsuccessful authentication	The authentication for a data trigger on this capture SAP failed or timed out.
No data-trigger SAP-id in authentication	The dynamic services data trigger SAP ID is not provided in authentication. This is a mandatory parameter.
Corresponding dynamic SAP is not created	The data trigger successfully authenticated but the corresponding dynamic SAP was not created. This is typically caused by a dynamic services script error.

to clear the dynamic services capture SAP control plane statistics:

# clear service id <service-id> dynamic-services capture-sap <sap-id> statistics