Create a New Map ( VMware ESXi)

If you're a new user, the free trial lasts for 30 days. After that, GigaVUE‑FM asks you to buy a license. For details, refer to GigaVUE Licensing Guide.

A map filters traffic that flows through GigaVUE V Series Nodes. It includes one or more rules, each defining what traffic to match. Traffic can match one or more rules in the map.

Parameters to create a map

Parameter

Description

Rules

A rule (R) includes filtering conditions that traffic must match. It also defines traffic direction (ingress or egress) and target.

Priority

Sets the rule execution order. Use values from 1 (highest) to 5 (lowest).

Pass

Sends traffic from the VM to the destination.

Drop

Drops the traffic from the virtual machine when passing through the map.

Traffic Filter Maps

A set of maps to match traffic and perform various actions on the matched traffic.

Inclusion Map

An inclusion map determines the instances to be included for monitoring. This map is used only for target selection.

Exclusion Map

An exclusion map determines the instances to be excluded from monitoring. This map is used only for target selection.

Automatic Target Selection (ATS)

A built-in feature that automatically selects the cloud instances based on the rules defined in the traffic filter maps, inclusion maps, and exclusion maps in the Monitoring Session.

The below formula describes how ATS works:

Selected Targets = Traffic Filter Maps ∩ Inclusion Maps - Exclusion Maps

Below are the filter rule types that work in ATS:

  • ● mac Source
  • ● mac Destination
  • ● ipv4 Source
  • ● ipv4 Destination
  • ● ipv6 Source
  • ● ipv6 Destination
  • ● VM Name Destination
  • ● VM Name Source
  • ● VM Tag Destination - Not applicable to Nutanix.
  • ● VM Tag Source - Not applicable to Nutanix.
  • ● VM Category Source - Applicable only to Nutanix.
  • ● VM Category Destination - Applicable only to Nutanix.
  • ● Host Name -Applicable only to Nutanix and VMware.

The traffic direction is as follows:

  • ● For any rule type as Source - the traffic direction is egress.
  • ● For Destination rule type - the traffic direction is ingress.
  • ● For Hostname - As it doesn't have Source or Destination rule type, the traffic direction is Ingress and Egress.
Notes:
  • For OpenStack environment, Subnet Name Source and Subnet Name Destination are the exclusion filters available as part of Exclusion Maps with Traffic Acquisition method as OVS Mirroring in the Monitoring Domain.
  • If no ATS rule filters listed above are used, all VMs and vNICS are selected as targets. When any ATS rule results in a null set, no target is selected and V Series Node does not receive traffic from any VM or vNIC.

Group

A group is a collection of pre-defined maps saved in the map library for reuse.

Rules and Notes:

  • Directional rules do not work on single NIC VMs running a Windows UCT-V.
  • Loopback captures bidirectional traffic from both ingress and egress. To prevent duplicate tapping, only egress tapping is permitted.
  • If you are running GigaVUE Cloud Suite on OpenStack, you can add a subnet to the exclusion map. To do this, create an exclusion map and select the Subnet name in the ruleset.
  • If a packet is fragmented, then all the fragments are destined to the same application end point. You can find the stats of mapped fragmented traffic in GigaVUE-FM.For details, refer to Review Map Statistics with Map Rule Counters.

Create a Map

To create a map,

  1. Drag and drop New Map from the New expand menu to the graphical workspace. The Map quick view appears.
  2. On the new Map quick view, select the General tab and enter the required information as described below.

    • Name: Name of the new map

    • Description: Details of the map

    • Application Filtering: Enable this option if you wish to use Application Filtering Intelligence. Enabling this option allows you to filter traffic based on Application name or family. For details, refer to Application Filtering Intelligence.

    • Selected Virtual Machines: Using this option, you can select an individual Network adapter of a virtual machine as a target. Both ingress and egress traffic of the network adapter chosen are redirected for monitoring. You can also view and filter the list of virtual machines available. When using this option, you cannot use Automatic Target Selection (ATS)

    • Virtual Machine List: Save the list or filter.

      To save,

      • Select Virtual Machine List. 

        The Virtual Machine List quick view opens. 

      • Select the virtual machines you wish to use as the target. 

      • Select Apply in the Virtual Machine List quick view to save your changes.

      To filter,

      • Select Filter and select one of the following criteria:

        • Data Center

        • Cluster

        • Host Name

        • VM Name

        • VM Tag Category

        • VM Tag Name

      • After selecting the details, select Apply in the filter dialog box to apply the filters. 

        The list of virtual machines appears based on the filter criteria. 

      • Select the virtual machines you wish to use as the target, and select Apply in the Virtual Machine List quick view to save your changes.

    • VMware tools are not required to discover targets, as GigaVUE‑FM can discover targets with ATS using the tags attached to the VMs.

    • Targets are selected when you provide the VM's node name or the hostname as selection criteria. A host is selected when the hostname matches all the active targets.

    • Pass and Drop rule selection with Automatic Target Selection (ATS) differs with the Map type as follows:

      • Traffic Map—Only Pass rules for ATS

      • Inclusion Map—Only Pass rules for ATS

      • Exclusion Map—Only Drop rules for ATS

  3. Select the Rule Sets tab and perform the following:
    1. Create a new rule set:
      1. Click Actions > New Ruleset.
      2. Enter a Priority value from 1 to 5 for the rule with 1 being the highest and 5 is the lowest priority.
      3. Enter the Application Endpoint in the Application EndPoint ID field.
      4. Select a required condition from the drop-down list.
      5. Select the rule to Pass or Drop through the map.
    2. Create a new rule:
      1. Click Actions > New Rule.
      2. Select a required condition from the drop-down list.
      3. Select and select Add Condition.
      4. Select the rule to Pass or Drop through the map.
  4. Select Save.

Through the map, packets is dropped or passed based on the highest to lowest rule priority. You can add 5 rule sets on a map. Use the + and - buttons to add or remove a rule set in the map. Each rule set can have only 25 rules per map and each rule can have a maximum of 4 conditions.

You must select at least one rule condition to add ATS rules for an Inclusion/Exclusion map. For details, refer to Example- Create a New Map using Inclusion and Exclusion Maps.

You can also perform the following actions on the Monitoring session canvas.

  • To edit a map, select the menu button of the required map on the canvas and select Details, or click Delete to delete the map.
  • To apply the threshold template to maps, select the required map on the canvas and select Details. The quick view appears, select the Thresholds tab. For more details on how to create or apply threshold templates, refer to Monitor Cloud Health.
  • Hover over the rules and apps buttons on the map to view the rules and applications configured for the selected map.
  • Select the rules and apps buttons to open the quick view menu for RULESETS.

Example- Create a New Map using Inclusion and Exclusion Maps

Consider a Monitoring Session with 5 cloud instances. Namely target-1-1, target-1-2, target-1-3, target-2-1, target-2-2.

  1. Drag and drop a new map template to the workspace. The New map quick view appears.
  2. In the GENERAL tab, enter the name as Map 1 and enter the description. In the RULESETS tab, enter the priority and Application Endpoint ID.
  3. Select the condition as VM Name and enter the target. This includes the instances target-1-1, target-1-2, target-1-3, target-2-1, and target-2-2.
  4. Select the Expand icon at the bottom of the Monitoring session canvas. The Inclusion Maps and Exclusion Maps section appears.
  5. Drag and drop a new map template to the Inclusion Maps region. The New Map quick view appears. Enter the Name and Description of the map.
    1. In the GENERAL tab, enter the name as Inclusionmap1 and enter the description. In the RULESETS, enter the priority and Application Endpoint ID.
    2. Select the condition as VM Name and enter the VM Name as target-1. Then the instance with VM name target-1-1, target-1-2, and target-1-3 will be included.
  6. Drag and drop a new map template to the Exclusion Maps region. The New Map quick view appears. Enter the details as mentioned in the above section.
    1. In the GENERAL tab, enter the name as Exclusionmap1 and enter the description. In the RULESETS tab, enter the priority and Application Endpoint ID.
    2. Select the condition as VM Name and enter the VM Name as target-1-3. Then the instance target-1-3 will be excluded.

    Based on this configuration, the Automatic Target Selection will select the instances target-1-1 and target-1-2 as target.