Create an Application Intelligence Session in Physical Environment
To create an Application Intelligence Session:
|
1.
|
On the left navigation pane, select Traffic > Solutions > Application Intelligence. |
|
2.
|
Click Create New. The Create Application Intelligence Session page appears. |
Note: If the Create button is disabled, check whether a valid license for Application Metadata Intelligence or Application Filtering Intelligence is available.
|
3.
|
In the Basic Info section complete the following: |
|
■
|
Enter the name and description (optional). |
|
■
|
Select Physical in the Environment field. |
|
■
|
Select the node from the list of nodes. |
|
4.
|
In the Configurations section, view the following: |
|
Option
|
Mandatory
|
Default
|
Notes
|
|
Monitoring
|
No
|
Enabled
|
AppViz is enabled by default. It can be disabled when not required. Disabling it can improve the performance.
|
|
Export Interval
|
Yes
|
300s (5 minutes)
|
Configures the interval of the records to be exported to GigaVUE-FM for AppViz.
This is not user configurable from 6.4 onwards.
|
|
Fast Mode
|
No
|
Disabled.
|
Note:
It supports exporting limited HTTP attributes. GigaVUE FM automatically enables selecting only the supported attributes
Note: The Fast Mode option can be enabled or disabled only when creating a new application intelligence session.
|
|
5.
|
Select a GigaSMART Group. You can also choose to create a new GigaSMART Group. |
|
•
|
Provide a name in the Alias field. |
|
•
|
Select a port or multiple ports from the Port List. |
|
•
|
Set Application Session Filtering Buffer Size |
|
•
|
Set Metadata Export Buffer Size |
|
6.
|
In the User Defined Applications section, select the template from the inventory where it was created. Refer Configure User Defined Application to know more about configuration steps. |
|
7.
|
If you are unable to view the required port in the Port field, perform these steps: |
|
o
|
Click Port Editor. Select the Type as Tool from the drop-down list for the required Port Id. Select OK. |
The selected Port appears in the list.
|
o
|
IPv4 - to allow the traffic in IPv4 interface. |
|
o
|
IPv6 - to allow the traffic in IPv6 interface. |
|
o
|
Provide the IP Address, IP Mask, Gateway, and MTU. Provide the IP address corresponding to the IP interface selected. |
|
8.
|
In the DestinationSettings, enter the destination IP address. The version of IP address in the Destination field should be same as the version of IP address defined in the IP-interface (applicable only when IP interface is selected). By default, the IP address of the GigaVUE-FM interface is displayed. |
|
9.
|
In the Source Traffic section, select a source port that require application monitoring in the Source ports field. Source port can be a single port, multiple ports, and port groups. |
Note: Ports already used as source ports in the intent-based orchestrated solution will not be listed in the drop-down.
|
10.
|
Click Save. The session created is added in the list view. |
|
11.
|
In the created session, click Edit to perform operations related to Application Filtering, De-duplication and Application Metadata. |
|
12.
|
Configure the rules for filtering the required traffic in the L2-L4 Rules fields. To configure a rule: |
|
a.
|
Click Select Conditions. Select the required parameters from the drop-down list. |
|
b.
|
Select the value for the parameters from the drop-down. |
|
c.
|
Select the required options: |
|
•
|
Pass or Drop - Based on the parameter selected in the Conditions fields, the traffic that matches the conditions will either be passed or dropped. |
|
•
|
Bidirectional - Allows the traffic in both directions of the flow. |
Note: Click “+” to create multiple rules for filtering the required traffic, and click “+ New Source Traffic” to create multiple sources with filtering options.
Refer to the Map Rules section in Inner Header and MPLS Header Filtering.
You can configure Inner Header qualifiers and MPLS Header qualifiers for GIgaVUE-TA400 device. Refer to Inner Header and MPLS Header Filtering
The total applications participating in the network traffic are displayed in the Application Intelligence Dashboard. For more information about the dashboard, refer to the View the Application Intelligence Dashboard.
If the session configuration is unsuccessful, troubleshoot the error notified (refer to
View the Health Status of a Solution). Click the Reapply all pending solutions button 
in the dashboard to redeploy the configuration.
You can also filter the traffic based on the applications. For more information, see Create Application Filtering Intelligence for Physical Environment.
Note: Users may want to filter traffic upfront based on VLAN, subnet, and host IP address. Filtering traffic upfront can also reduce the load on the DPI engine. Application Intelligence supports configuring L2-L4-based rules to filter such traffic.
