1. Click the Provision control (+) in the Managed Services table. The system displays the Create Managed Service dialog, shown in the following figure.

   

2. Assign a name to the managed service.
3. (Optional) Provide a text description of the managed service.
4. Select the switch and interface providing the service.
   The Show Managed Device Switches Only checkbox, enabled by default, limits the switch selection list to service node appliances. Enable the Show Connected Switches Only checkbox to limit the display to connected switches.
5. Select the action from the Action selection list, which provides the following options.
   • Application ID
   • Deduplication: Deduplicate selected traffic, including NATted traffic.
   • GTP Correlation
   • Header Strip: Remove bytes of packet starting from zero till selected Anchor and offset bytes
   • Header Strip Cisco Fabric Path Header: Remove the Cisco Fabric Path encapsulation header
   • Header Strip ERSPAN Header: Remove Encapsulated Remote Switch Port Analyzer Encapsulation header
   • Header Strip Genev1 Header: Remove Generic Network Virtualization Encapsulation header
   • Header Strip L3 MPLS Header: Remove Layer 3 MPLS encapsulation header
   • Header Strip LISP Header: Remove Locator Separation Protocol Encapsulation header
   • Header Strip VXLAN Header: Remove Virtual Extensible LAN Encapsulation header
   • IPFIX: Generate IPFIX by selecting matching traffic and forwarding it to specified collectors.
   • Mask: Mask sensitive information as specified by the user in packet fields.
   • NetFlow: Generate a NetFlow by selecting matching traffic and forwarding it to specified collectors.
   • Pattern-Drop: Drop matching traffic.
   • Pattern Match: Forward matching traffic.
   • Session Slice: Slice TCP sessions.
   • Slice: Slice the given number of bytes based on the specified starting point in the packet.
   • TCP Analysis
   • Timestamp: Identify the time that the service node receives the packet.
   • UDP Replication: Copy UDP messages to multiple IP destinations, such as Syslog or NetFlow messages.
6. (Optional) Identify the starting point for service actions.
   Identify the start point for the deduplication, mask, pattern-match, pattern-drop services, or slice services using one of the keywords listed below.

   • packet-start: add the number of bytes specified by the integer value to the first byte in the packet.
   • l3-header-start: add the number of bytes specified by the integer value to the first byte in the Layer 3 header.
   • l4-header-start: add the number of bytes specified by the integer value to the first byte in the layer-4 header.
   • l4-payload-start: add the number of bytes specified by the integer value to the first byte in the layer-4 user data.
   • integer: specify the number of bytes to offset for determining the start location for the service action relative to the specified start keyword.
7. To assign a managed service to a policy, enable the checkbox on the Managed Services page of the Create Policy or Edit Policy dialog.
8. Select the backup service from the Backup Service selection list to create a backup service. The backup service is used when the primary service is not available.

1. Define an identifier for the managed service by entering the following command:

   controller-1(config)# managed-service DEDUPLICATE-1
   controller-1(config-managed-srv)#

   This step enters the config-managed-srv submode, where you can configure a DMF-managed service.

2. (Optional) Configure a description for the current managed service by entering the following command:

   controller-1(config-managed-srv)# description “managed service for policy DEDUPLICATE-1”

   The following are the commands available from this submode:

   • description: provide a service description
   • post-service-match: select traffic after applying the header strip service
   • Action sequence number in the range [1 - 20000]: identifier of service action
   • service-interface: associate an interface with the service
3. Use a number in the range [1 - 20000] to identify a service action for a managed service.
   The following summarizes the available service actions. See the subsequent sections for details and examples for specific service actions.

   • dedup {anchor-offset | full-packet | routed-packet}
   • header-strip {l4-header-start | l4-payload-start | packet-start }[offset]
   • decap-cisco-fp {drop}
   • decap-erspan {drop}
   • decap-geneve {drop}
   • decap-l3-mpls {drop}
   • decap-lisp {drop}
   • decap-vxlan {drop}
   • mask {mask/pattern} [{packet-start | l3-header-start | l4-header-start | l4-payload-start} mask/offset] [mask/mask-start mask/mask-end]}
   • netflow Delivery_interface Name
   • ipfix Delivery_interface Name
   • udp-replicate Delivery_interface Name
   • tcp-analysis Delivery_interface Name

   Note: The IPFIX, NetFlow, and udp-replicate service actions enable a separate submode for defining one or more specific configurations. One of these services must be the last service applied to the traffic selected by the policy.

   • pattern-drop pattern [{l3-header-start | l4-header-start | packet-start }]
   • pattern-match pattern [{l3-header-start | l4-header-start | packet-start }] |
   • slice {packet-start | l3-header-start | l4-header-start | l4-payload-start} integer}
   • timestamp

   For example, the following command enables packet deduplication on the routed packet:

   controller-1(config-managed-srv)# 1 dedup routed-packet

4. Optionally, identify the start point for the mask, pattern-match, pattern-drop services, or slice services.
5. Identify the service interface for the managed service by entering the following command:

   controller-1(config-managed-srv)# service-interface switch DMF-CORE-SWITCH-1 ethernet40

   Use a port channel instead of an interface to increase the bandwidth available to the managed service. The following example enables lag-interface1 for the service interface:

   controller-1(config-managed-srv)# service-interface switch DMF-CORE-SWITCH-1 lag1

6. Apply the managed service within a policy like any other service, as shown in the following examples for deduplication, NetFlow, pattern matching (forwarding), and packet slicing services.

1. Select the Monitoring > Managed Services option.
2. On the DMF Managed Services page, select IPFIX Templates.
   The system displays the IPFIX Templates section.

   

3. To create a new template, click the provision (+) icon in the IPFIX Templates section.

   

4. To add an IPFIX key to the template, click the Settings control in the Keys section. The system displays the following dialog.

   

5. Enable each checkbox for the keys you want to add to the template and click Select.
6. To add an IPFIX field to the template, click the Settings control in the Fields section. The system displays the following dialog:

   

7. Enable the checkbox for each field you want to add to the template and click Select.
8. On the Create IPFIX Template page, click Save.

1. Create an IPFIX template.

   controller-1(config)# ipfix-template IPFIX-IP
   controller-1(config-ipfix-template)#

   This changes the CLI prompt to the config-ipfix-template submode.

2. Define the keys to use for the current template, using the following command:

   [ no ] key { ethernet-type | source-mac-address | destination-mac-address | dot1q-vlan-id | dot1q-priority | ip-version | ip-protocol-identifier | ip-class-of-service | ip-diff-serv-code-point | ip-ttl | sourceipv4-address | destination-ipv4-address | icmp-type-code-ipv4 | source-ipv6-address | destination-ipv6-address | icmp-type-code-ipv6 | source-transport-port | destination-transport-port }

   The keys specify the attributes of the flows to be included in the flowset measurements.

3. Define the fields to use for the current template, using the following command:
   [ no ] field { packet-delta-count | octet-delta-count | minimum-ip-total-length | maximum-ip- total-length | flow-start-seconds | flow-end-seconds | flow-end-reason | flow-start-milliseconds | flow-end-milliseconds | minimum-layer2-total-length | maximum-layer2-total- length | minimum-ttl | maximum-ttl }

   The fields specify the measurements to be included in the flowset.

1. Configure the IP address on the delivery interface.
   This IP address should be the next-hop IP address from the DANZ Monitoring Fabric towards the NetFlow collector.

   CONTROLLER-1(config)# switch DMF-DELIVERY-SWITCH-1
   CONTROLLER-1(config-switch)# interface ethernet1
   CONTROLLER-1(config-switch-if)# role delivery interface-name NETFLOW-DELIVERY-PORT ip-address 172.43.75.1 nexthop-ip 172.43.75.2 255.255.255.252

2. Configure the rate-limit for the NetFlow delivery interface.

   CONTROLLER-1(config)# switch DMF-DELIVERY-SWITCH-1
   CONTROLLER-1(config-switch)# interface ethernet1
   CONTROLLER-1(config-switch-if)# role delivery interface-name NETFLOW-DELIVERY-PORT ip-address 172.43.75.1 nexthop-ip 172.43.75.2 255.255.255.252
   CONTROLLER-1(config-switch-if)# rate-limit 256000

   Note: The rate limit must be configured when enabling Netflow. When upgrading from a version of DMF before release 6.3.1, the Netflow configuration is not applied until a rate limit is applied to the delivery interface.
3. Configure the NetFlow managed service using the 1 netflow command followed by an identifier for the specific NetFlow configuration.

   
   CONTROLLER-1(config)# managed-service MS-NETFLOW-SERVICE CONTROLLER-1
   (config-managed-srv)# 1 netflow NETFLOW-DELIVERY-PORT CONTROLLER-1
   (config-managed-srv-netflow)#

   The following commands are available in this submode:

   • active-timeout: configure the maximum length of time the NetFlow is transmitted before it is ended (in minutes).
   • collector: configure the collector IP address, and change the UDP port number or the MTU.
   • inactive-timeout: configure the length of time that the NetFlow is inactive before it is ended (in seconds).
   • max-flows: configure the maximum number of flows managed.

   An option exists to limit the number of flows or change the inactivity timeout using the max-flows or active timeout, or inactive timeout commands.

4. Configure the IP address of the NetFlow collector using the following command:

   collector <ip4-address>[udp-port<integer>][mtu <integer>][records-per-interface]
   

   The IP address, in IPV4 dotted-decimal notation, is required. The MTU and UDP port are required when changing these parameters from the defaults. Enable the records-per-interface option to allow identification of the filter interfaces from which the Netflow originated. Configure the Arista Analytics Node to display this information, as described in the DMF User Guide.

   The following is an example of changing the Netflow UDPF port to 9991.

   collector 10.181.19.31 udp-port 9991

   Note: The IP address must be in the same subnet as the configured next hop and unique. It cannot be the same as the Controller, service node, or any monitoring fabric switch IP address.
5. Configure the DMF policy with the forward action and add the managed service to the policy.
   Note: A DMF policy does not require any configuration related to a delivery interface for NetFlow policies because the DMF Controller automatically assigns the delivery interface.

   The example below shows the configuration required to implement two NetFlow service instances (MS-NETFLOW-1 and MS-NETFLOW-1).

   ! switch
   switch DMF-DELIVERY-SWITCH-1
   !
   interface ethernet1
   role delivery interface-name NETFLOW-DELIVERY-PORT-1 ip-address 10.3.1.1
   nexthop-ip 10.3.1.2 255.255.255.0
   interface ethernet2
   role delivery interface-name NETFLOW-DELIVERY-PORT-2 ip-address 10.3.2.1
   nexthop-ip 10.3.2.2 255.255.255.0
   ! managed-service
   managed-service MS-NETFLOW-1
   service-interface switch DMF-CORE-SWITCH-1 interface ethernet11/1
   !
   1 netflow NETFLOW-DELIVERY-PORT-1
   collector-ip 10.106.1.60 udp-port 2055 mtu 1024
   managed-service MS-NETFLOW-2
   service-interface switch DMF-CORE-SWITCH-2 interface ethernet12/1
   !
   1 netflow NETFLOW-DELIVERY-PORT-1
   collector-ip 10.106.2.60 udp-port 2055 mtu 1024
   ! policy
   policy GENERATE-NETFLOW-1
   action forward
   filter-interface TAP-INTF-DC1-1
   filter-interface TAP-INTF-DC1-2
   use-managed-service MS-NETFLOW-1 sequence 1
   1 match any
   policy GENERATE-NETFLOW-2
   action forward
   filter-interface TAP-INTF-DC2-1
   filter-interface TAP-INTF-DC2-2
   use-managed-service MS-NETFLOW-2 sequence 1
   1 match any

1. Create a managed service using the managed-service service name command.
2. Add slice action with packet-start anchor and an offset value between the supported range as reported by the show switch all property command.
3. Configure the service interface under the config-managed-srv submode using the service-interface switch switch-name interface-name command as shown in the following example.

   > enable
   # config
   (config)# managed-service slice-action-7280-J2-J2C
   (config-managed-srv)# 1 slice packet-start 101
   (config-managed-srv)# service-interface switch 7280-J2-J2C Ethernet10/1

This feature requires the service interface to be in MAC loopback mode.

4. To set the service interface in MAC loopback mode, navigate to the config-switch-if submode and configure using the loopback-mode mac command, as shown in the following example.

   (config)# switch 7280-J2-J2C
   (config-switch)# interface Ethernet10/1
   (config-switch-if)# loopback-mode mac

Once a managed service for slice action exists, any policy can use it.

5. Enter the config-policy submode, and chain the managed service using the use-managed-service service same sequence sequence command.

   (config)# policy timestamping-policy
   (config-policy)# use-managed-service slice-action-7280-J2-J2C sequence 1

Controller# show policy packet-slicing-policy
Policy Name: packet-slicing-policy
Config Status: active - forward
Runtime Status : installed
Detailed Status: installed - installed to forward
Priority : 100
Overlap Priority : 0
# of switches with filter interfaces : 1
# of switches with delivery interfaces : 1
# of switches with service interfaces: 1
# of filter interfaces : 1
# of delivery interfaces : 1
# of core interfaces : 0
# of services: 1
# of pre service interfaces: 1
# of post service interfaces : 1
Push VLAN: 1
Post Match Filter Traffic: -
Total Delivery Rate: -
Total Pre Service Rate : -
Total Post Service Rate: -
Overlapping Policies : none
Component Policies : none
Runtime Service Names: packet-slicing-7280
Installed Time : 2023-08-09 19:00:40 UTC
Installed Duration : 1 hour, 17 minutes
~ Match Rules ~
# Rule
-|-----------|
1 1 match any

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Filter Interface(s) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# DMF IF Switch IF Name State Dir Packets Bytes Pkt Rate Bit Rate Counter Reset Time
-|------|------|-----------|-----|---|-------|-----|--------|--------|------------------------------|
1 f1 7280 Ethernet2/1 uprx0 0 0-2023-08-09 19:00:40.305000 UTC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Delivery Interface(s) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# DMF IF Switch IF Name State Dir Packets Bytes Pkt Rate Bit Rate Counter Reset Time
-|------|------|-----------|-----|---|-------|-----|--------|--------|------------------------------|
1 d1 7280 Ethernet3/1 uptx0 0 0-2023-08-09 19:00:40.306000 UTC

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Service Interface(s) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Service nameRole Switch IF NameState Dir Packets Bytes Pkt Rate Bit Rate Counter Reset Time
-|-------------------|----|------|------------|-----|---|-------|-----|--------|--------|------------------------------|
1 packet-slicing-7280 pre7280 Ethernet10/1 uptx0 0 0-2023-08-09 19:00:40.305000 UTC
2 packet-slicing-7280 post 7280 Ethernet10/1 uprx0 0 0-2023-08-09 19:00:40.306000 UTC

~ Core Interface(s) ~
None.

~ Failed Path(s) ~
None.

Controller# show managed-services
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Managed-services ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Service NameSwitch Switch Interface Installed Max Post-Service BW Max Pre-Service BW Total Post-Service BW Total Pre-Service BW
-|-------------------|------|----------------|---------|-------------------|------------------|---------------------|--------------------|
1 packet-slicing-7280 7280 Ethernet10/1 True400Gbps 400Gbps80bps 80bps

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Actions of Service Names ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Service NameSequence Service Action Slice Anchor Insert original packet length Slice Offset
-|-------------------|--------|--------------|------------|-----------------------------|------------|
1 packet-slicing-7280 1slicepacket-start False 101

1. To configure or edit a managed service, navigate to the DMF Managed Services page from the Monitoring menu and click Managed Services.

   

   

2. Configure a managed service interface on a switch that supports packet slicing. Make sure to deselect the Show Managed Device Switches Only checkbox.

   

3. Configure a new managed service action using Add Managed service action. The action chain supports only one action when configuring packet slicing on a switch.

   

4. Use Action > Slice with Anchor > Packet Start to configure the packet slicing managed service on a switch.

   

5. Click Append to continue. The slice action appears on the Managed Services page.

   

Interface Loopback Configuration

The managed service interface used for slice action must be in MAC loopback mode.

6. Configure the loopback mode in the Fabric > Interfaces page by clicking on the configuration icon of the interface.

   

   Note: The image above has been edited for documentation purposes. The actual output will differ.
7. Enable the toggle for MAC Loopback Mode (set the toggle to Yes).

   

8. After all configuration changes are done Save the changes.

Policy Configuration

9. Create a new policy from the DMF Policies page.

   

10. Add the previously configured packet slicing managed service.

    

11. Select Add Service under the + Add Service(s) option shown above.

    

    

12. Click Add 1 Service and the slice-managed service (packet-slicing-policy) appears in the Create Policy page.

    

13. Click Create Policy and the new policy appears in DMF Policies.

    

    Note: The images above have been edited for documentation purposes. The actual outputs may differ.

1. Select Monitoring > Policies and click the Provision control (+) to create a new policy.
2. Configure the policy as required. From the Services section, click the Provision control (+) in the Managed Services table.

   

3. Select the primary managed service from the Managed Service selection list.
4. Select the backup service from the Backup Service selection list and click Append.

1. Identify the first managed service.

   managed-service MS-SLICE-1
   1 slice l3-header-start 20
   service-interface switch CORE-SWITCH-1 lag1

2. Identify the second managed service.

   managed-service MS-SLICE-2
   1 slice l3-header-start 20
   service-interface switch CORE-SWITCH-1 lag2

3. Configure the policy referring to the backup managed service.

   policy SLICE-PACKETS
   action forward
   delivery-interface TOOL-PORT-1
   filter-interface TAP-PORT-1
   use-managed-service MS-SLICE-1 sequence 1 backup-managed-service MS-SLICE-2
   1 match ip

1. Create a managed service and enter the service interface.
2. Choose the app-id managed service using the <seq num> app-id command.
   Note: The above command should enter the app-id submode, which supports two configuration parameters: collector and l3-delivery-interface. Both are required.
3. To configure the IP address of the IPFIX collector, enter the following command: collector ip-address.
   The UDP port and MTU parameters are optional; the default values are 4739 and 1500, respectively.
4. Enter the command: l3-delivery-interface delivery interface name to configure the delivery interface.

managed-service ms
service-interface switch core1 ethernet2
!
1 app-id
collector 192.168.1.1
l3-delivery-interface app-to-analytics

1. Create a managed service and enter the service interface.
2. Choose the app-id managed service using the <seq num> app-id-filter command.
   Note: The above command should enter the app-id-filter submode, which supports three configuration parameters: app, app-category, and filter-mode. The category app is required, while app-category and filter-mode are optional. The option filter-mode has a default value of forward.
3. Enter the command: app application name to configure the application name.
   Tip: Press the Tab key after entering the app keyword to see all possible application names. Type in a partial name and press the Tab to see all possible choices to auto-complete the name. The application name provided must match a name in this list of app names. A service node must be connected to the Controller for this list to appear. Any number of apps can be entered one at a time using the app application-name command. The following is an example of a (partial) list of names:

   dmf-controller-1 (config-managed-srv-app-id-filter)# app ibm
   ibm ibm_as_central ibm_as_dtaqibm_as_netprt ibm_as_srvmap ibm_iseries ibm_tsm
   ibm_app ibm_as_databaseibm_as_fileibm_as_rmtcmd ibm_db2 ibm_tealeaf

4. Filter applications by category using the app-category category name command. Currently, the applications contained in these categories are not displayed.

   dmf-controller-1(config-managed-srv-app-id-filter)# app-category
   <Category> <String> :<String>
   aaaCategory selection
   adult_contentCategory selection
   advertisingCategory selection
   aetlsCategory selection
   analyticsCategory selection
   anonymizer Category selection
   audio_chat Category selection
   basicCategory selection
   blog Category selection
   cdnCategory selection
   certif_authCategory selection
   chat Category selection
   classified_ads Category selection
   cloud_services Category selection
   crowdfunding Category selection
   cryptocurrency Category selection
   db Category selection
   dea_mail Category selection
   ebook_reader Category selection
   educationCategory selection
   emailCategory selection
   enterprise Category selection
   file_mngtCategory selection
   file_transferCategory selection
   forumCategory selection
   gaming Category selection
   healthcare Category selection
   im_mcCategory selection
   iotCategory selection
   map_serviceCategory selection
   mm_streaming Category selection
   mobile Category selection
   networking Category selection
   news_portalCategory selection
   p2pCategory selection
   payment_serviceCategory selection
   remote_accessCategory selection
   scadaCategory selection
   social_network Category selection
   speedtestCategory selection
   standardized Category selection
   transportation Category selection
   update Category selection
   video_chat Category selection
   voip Category selection
   vpn_tunCategory selection
   webCategory selection
   web_ecom Category selection
   web_search Category selection
   web_sitesCategory selection
   webmailCategory selection

5. The filter-mode parameter supports two modes: forward and drop. Enter filter-mode forward to allow the packets to be forwarded based on the configured applications. Enter filter-mode drop to drop these packets.
   An example of an app-id-filter configuration that drops all Facebook and IBM Tealeaf packets:

   managed-service MS
   	service-interface switch CORE-SWITCH-1 ethernet2
   	!
   	1 app-id-filter
   		app facebook
   		app ibm_tealeaf
   filter-mode drop

1. Navigate to the Monitoring > Managed Services page. Click the table action + icon button to add a new managed service.

   

2. Configure the Name, Switch, and Interface inputs in the Info step.

   

3. In the Actions step, click the + icon to add a new managed service action.

   

4. To Add the App ID Action, select App ID from the action selection input:

   

5. Fill in the Delivery Interface, Collector IP, UDP Port, and MTU inputs and click Append to include the action in the managed service:

   

6. To Add the App ID Filter Action, select App ID Filter from the action selection input:

   

7. Select the Filter input as Forward or Drop action:

   

8. Use the App Names section to add app names.

   1. Click the + button to open a modal pane to add an app name.

   2. The table lists all app names. Use the text search to filter out app names. Select the checkbox for app names to include and click Append Selected.

   3. Repeat the above step to add more app names as necessary.

   

9. The selected app names are now listed. Use the - icon button to remove any app names, if necessary:

   

10. Click the Append button to add the action to the managed service and Save to save the managed service.

1. Remove all policies containing app-id or app-id-filter. Remove the app-id and app-id-filter managed services from the policies using the command: no use-managed-service in policy config.
   Arista Networks recommends this step to avoid errors and service node reboots during the update process. A warning message is printed right before confirming a push. Proceeding without this step may work but is not recommended as there is a risk of service node reboots.
   Note: Arista Networks provides the specific update file in the command example below.
2. To pull the signature file onto the Controller node, use the command:

   dmf-controller-1(config)# app-id pull-signature-file user@host:path to file.tar.gz
   Password:
   file.tar.gz							5.47MB 1.63MBps 00:03

3. Fetch and validate the file using the command:

   dmf-controller-1(config)# app-id fetch-signature-file file://file.tar.gz
   Fetch successful.
   Checksum : abcdefgh12345
   Fetch time : 2023-08-02 22:20:49.422000 UTC
   Filename : file.tar.gz

4. To view files currently saved on the Controller node after the fetch operation is successful, use the following command:

   dmf-controller-1(config)# app-id list-signature-files
   # Signature-file	Checksum 		Fetch time
   -|-----------------|-----------------|------------------------------|
   1 file.tar.gz	abcdefgh12345	2023-08-02 22:20:49.422000 UTC

   Note: Only the files listed by this command can be pushed to service nodes.
5. Push the file from the Controller to the service nodes using the following command:

   dmf-controller-1(config)# app-id push-signature-file file.tar.gz
   App ID update: WARNING: This push will affect all service nodes
   App ID update: Remove policies configured with app-id or app-id-filter before continuing to avoid errors
   App ID update: Signature file: file.tar.gz
   App ID update: Push app ID signatures to all Service Nodes? Update ("y" or "yes" to continue): yes
   Push successful.
   
   Checksum : abcdefgh12345
   Fetch time : 2023-08-02 22:20:49.422000 UTC
   Filename : file.tar.gz
   Sn push time : 2023-08-02 22:21:49.422000 UTC

6. Add the app-id and app-id-filter managed services back to the policies.
   As a result of adding app-id, service nodes can now identify and report new applications to the analytics node.
   After adding back app-id-filter, new application names should appear in the app-id-filter Controller app list. To test this, enter app-id-filter submode and press the Tab to see the full list of applications. New identified applications should appear in this list.
7. To delete a signature file from the Controller, use the command below.
   Note: DMF only allows deleting a signature file that is not actively in use by any service node, which needs to keep a working file in case of issues—attempting to delete an active file causes the command to fail.

   dmf-controller-1(config)# app-id delete-signature-file file.tar.gz
   Delete successful for file: file.tar.gz

1. Create a managed service and enter the service interface.
2. Choose the sample managed service with the seq num sample command.
   1. There are two required configuration values: max-tokens and tokens-per-refresh. There are no default values, and the service requires both values.
   2. The max-tokens value is the maximum size of tokens in the token bucket. The service will start with the number of tokens specified when first configured. Each packet passed consumes one token. If no tokens remain, packet forwarding stops. Configure the max-tokens value from a range of 1 to the maximum uint64 (unsigned integer) value of 9,223,372,036,854,775,807.
   3. DMF refreshes the token bucket every 10 ms. The tokens-per-refresh value is the number of tokens added to the token bucket on each refresh. Each packet passed consumes one token, and when the number of tokens drops to zero, the system drops all subsequent packets until the next refresh. The number of tokens in the bucket cannot exceed the value of max-tokens. Configure the tokens-per-refresh value from a range of 1 to the maximum uint64 (unsigned integer) value of 9,223,372,036,854,775,807.
   The following example illustrates a typical Sample Service configuration

   dmf-controller-1(config-managed-srv-sample)# show this
   ! managed-service
   managed-service MS
   !
   3 sample
   max-tokens 50000
   tokens-per-refresh 20000

3. Add the managed service to the policy.

DMF-SCALE-R450> show running-config managed-service techpubs

! managed-service
managed-service techpubs
!
1 sample
max-tokens 1000
tokens-per-refresh 500
DMF-SCALE-R450>

1. Navigate to the Monitoring > Managed Services page.

   

2. Under the Managed Services section, click the + icon to create a new managed service. Go to the Actions, and select the Sample option in the Action drop-down. Enter values for Max tokens and Tokens per refresh.

   

3. Click Append and then Save.

1. Create a managed service and enter the service interface.
2. Choose the latency service action with the command: seq num latency
   Note: The above command should enter the latency submode, which supports four configuration parameters: collector, l3-delivery-interface, and left and right tap points. These all are required parameters.
3. Configure the IP address of the IPFIX collector by entering the following command: collector ip-address (the UDP port and MTU parameters are optional; the default values are 4739 and 1500, respectively).
4. Configure the delivery interface by entering the command l3-delivery-interface delivery interface name.
5. Configure the points for latency and drop analysis using left-point and right-point parameters as specified in the following section.

   dmf-controller-1(config)# managed-service managed_service_1
   dmf-controller-1(config)# service-interface switch delivery1 ethernet1
   dmf-controller-1(config)# 1 latency
   dmf-controller-1(config)# collector 192.168.1.1
   dmf-controller-1(config)# l3-delivery-interface l3-iface-1
   dmf-controller-1(config)# left filter-interface left-point-f1
   dmf-controller-1(config)# right filter-interface right-point-f1