Examples- Configuring Application Intelligence Solution with Other Applications

This sections provides information on how applications like Application Filtering Intelligence, Application Metadata Intelligence and Application Metadata Exporter can be used with other applications in the monitoring session.

Refer to the following topics for more detailed information:

Slicing and Masking with Application Filtering Intelligence

When the traffic passes through the Application Filtering Intelligence, application metadata is created. You can use the Slicing and Masking application along with Application Filtering application slice, mask, or slice and mask the filtered packets before sending them to the destination tunnel endpoint.

Note:  When combining Slicing and Masking operations, the offset range of the Masking must be lesser than the offset value entered for the Slicing operation, as the Slicing operation is performed first.

Follow the steps below to configure Application Filtering Intelligence with Masking and Slicing:

  1. Drag and drop New Map / Application Filtering from New to the graphical workspace.
  2. Click the map and select Details. The Application quick view appears.
  3. Configure Application Filtering Intelligence using the steps given inConfigure Application Filtering Intelligence for Virtual Environment
  4. Drag and drop Slicing from Applications to the graphical workspace.
  5. Click the application and select Details. The Application quick view appears.
  6. Configure Slicing application using the steps given in Slicing
  7. Drag and drop Masking from Applications to the graphical workspace.
  8. Click the application and select Details. The Application quick view appears.
  9. Configure Masking application using the steps given in Masking.
  10. Drag and drop New Tunnel from New to the graphical workspace.
  11. Click the tunnel and select Details. The Application quick view appears.
  12. Select the Type as L2GRE/VXLAN. Select the Traffic Direction as Out. Refer to Create Ingress and Egress Tunnelfor step-by-step instructions on how to configure Tunnels.
  13. Enter Source L4 Port and Destination L4 Port.
  14. After placing the required items in the canvas, hover your mouse on the applications, click the red dot, and drag the arrow over to another item (map, application, or tunnel).

The filtered traffic will be sent to the Slicing application, the sliced traffic will be sent to Masking application and then to the destination tunnel Endpoint.

De-duplication with Application Metadata Intelligence

Duplicate packets are common in network analysis environments where both the ingress and egress data paths are sent to a single output. Using de-duplication with Application Metadata Intelligence lets you eliminate the duplicate packets in the Application Metadata output, only forwarding a packet once and thus reducing the processing load on your tools.

Follow the steps below to configure Application Metadata Intelligence with De-duplication:

  1. Drag and drop Application Metadata from Applications to the graphical workspace.
  2. Click the application and select Details. The Application quick view appears.
  3. Configure Application Metadata Intelligence using the steps given in Configure Application Metadata Intelligence for Virtual Environment.
  4. Drag and drop dedup from Applications to the graphical workspace.
  5. Click the application and select Details. The Application quick view appears.
  6. Configure de-duplication application using the steps given in De-duplication.
  7. Drag and drop New Tunnel from New to the graphical workspace.
  8. Click the tunnel and select Details. The Application quick view appears.
  9. Select the Type as UDP.
  10. Enter Source L4 Port, Destination L4 Port, and Destination IP. Refer to Create Ingress and Egress Tunnelfor step-by-step instructions on how to configure Tunnels.
  11. After placing the required items in the canvas, hover your mouse on the map, click the red dot, and drag the arrow over to another item (map, application, or tunnel).

The duplicate packets are removed before sending the traffic to AMI. This will reduce the load on Application Metadata application which in turn can avoid exporting the duplicated Metadata to the tool.