Create a Monitoring Domain

GigaVUE-FM connects to the VPC through the EC2 API endpoint. HTTPS is the default protocol which GigaVUE-FM uses to communicate with the EC2 API. For more information about the endpoint and the protocol used, refer to AWS service endpoints.

GigaVUE-FM provides you the flexibility to connect to multiple VPCs. You can choose the VPC ID and launch the GigaVUE Cloud Suite for AWS components in the desired VPCs.

Note:  To configure the monitoring domain and launch the fabric components in AWS, you must be a user with fm_super_admin role or a user with write access to the Physical Device Infrastructure Management category.

To create a Monitoring Domain:

  1. Go to Inventory > VIRTUAL > AWS , and then click Monitoring Domain.
  2. On the Monitoring Domain page, click the New button. The Monitoring Domain Configuration page appears.
  3. Enter or select the appropriate information as shown in the following table.

    Field

    		Action

    Monitoring Domain

    An alias used to identify the monitoring domain.

    Use V Series 2Select Yes to configure GigaVUE V Series 2 node.

    Traffic Acquisition Method

    Select a tapping method. The available options are:

    ■  G-vTAP: G-vTAP Agents are deployed on your VMs to acquire the traffic and forward the acquired traffic to the GigaVUE V Series nodes. If you select G-vTAP as the tapping method, you must configure the G-vTAP Controller to communicate to the G-vTAP Agents from GigaVUE-FM.
    You can also configure the G-vTAP Controller and G-vTAP Agents from your own orchestrator. Refer to Configure GigaVUE Fabric Components in AWS for detailed information.
    ■  VPC Traffic Mirroring: If you select the VPC Traffic Mirroring option, the mirrored traffic from your workloads is directed directly to the GigaVUE V Series nodes, and you need not configure the G-vTAP Agents and G-vTAP Controllers.
    For more information on VPC Peering, refer to VPC peering connections in the AWS Documentation. Peering is required to send mirrored traffic from other VPCs into a centralized GigaVUE V Series deployment.
    You can choose to use an external load balancer for VPC Traffic Mirroring. Select Yes to use load balancer. Refer to Configure an External Load Balancer on GigaVUE Cloud Suite for AWS for detailed information.
    • G-vTAP Controller configuration is not applicable for VPC Traffic Mirroring.
    • VPC mirroring does not support cross-account solutions without a load balancer.
    • For VPC Traffic Mirroring option, additional permissions are required. Refer to the Permissions and Privileges topic for details.
    • After deploying the Monitoring Session, a traffic mirror session is created in your AWS VPC consisting of a session, a filter, sources, and targets. For more details, refer to Traffic Mirroring in AWS Documentation.
    ■  Customer Orchestrated Source: If you use select Customer Orchestrated Source as the tapping method, you can use the Customer Orchestrated Source as a source option in the monitoring session, where the traffic is directly tunneled to the GigaVUE V Series nodes without deploying G-vTAP Agents and G-vTAP Controllers. The user is responsible for creating this tunnel feed and pointing it to the GigaVUE V Series node(s).

    Note:  When using Observability Gateway (AMX) application, select the Traffic Acquisition Method as Customer Orchestrated Source.

    Traffic Acquisition Tunnel MTU

    The Maximum Transmission Unit (MTU) is the maximum size of each packet that the tunnel endpoint can carry from the G-vTAP Agent to the GigaVUE V Series node.

    The default value is 8951. The G-vTAP Agent tunnel MTU should be 50 bytes less than the agent's destination interface MTU size.

    Use FM to Launch Fabric

    Select Yes to Configure and Deploy GigaVUE Fabric Components in GigaVUE-FM or select No to Configure GigaVUE Fabric Components in AWS.

    Connections

    Note:  You can add multiple connections in a monitoring domain. Refer to Create AWS Credentials for more information on adding multiple AWS Basic Credentials.

    Name

    An alias used to identify the connection.

    Credential

    Select an AWS credential. For detailed information, refer to Create AWS Credentials.

    Region

    AWS region for the monitoring domain. For example, US West.

    Accounts

    Select the AWS accounts

    VPCs

    Select the VPCs to monitor

  4. Click Save. The AWS Fabric Launch Configuration page appears.

Managing Monitoring Domain

You can view the details of the monitoring domain that are created in the list view. The list view details can be viewed based on:

You can also filter the monitoring domain based on a specified criterion. In the monitoring domain page there are two filter options as follows:

■   Right filter - Click the Filter button on the right to filter the monitoring domain based on a specific criterion.
■   Left filter - Click the to filter the monitoring domain based on the domain and connections. You can click + to create a new monitoring domain. This filter once applied also works even when the tabs are swapped.

To edit or delete a specific monitoring domain, select the monitoring domain, click the ellipses .

When you click a monitoring domain, you can view details of it in a split view of the window. In the split view window, you can view the details such as Configuration, Launch Configuration and V Series configuration.

Monitoring Domain

The list view shows the following information in the monitoring domain page:

■   Monitoring Domain
■   Connections
■   Tunnel MTU
■   Acquisition Method
■   Centralized connection
■   Management Network

Note:  Click the to select the columns that should appear in the list view.

Use the following buttons to manage your Monitoring Domain:

Button Description

New

Use to create new connection

Actions

You can select a monitoring domain and then perform the following options:

● Edit Monitoring Domain- Select a monitoring domain and then click Edit Monitoring domain to update the configuration.
● Delete Domain - You can select a monitoring domain or multiple monitoring domains to delete them.
● Edit Fabric -You can select one fabric or multiple fabrics of the same monitoring domain to edit a fabric. You cannot choose different fabrics of multiple monitoring domains at the same time and edit their fabrics
● Deploy Fabric - -You can select a monitoring domain to deploy a fabric, you cannot choose multiple monitoring domains at the same time to deploy fabrics. This option is only enabled when there is No FABRIC (launch configuration) for that specific monitoring domain and GigaVUE-FM orchestration is enabled.. You must create a fabric in the monitoring domain, if the option is disabled
● Upgrade Fabric-You can select a monitoring domain or multiple monitoring domains to upgrade the fabric. You can upgrade the V-Series nodes using this option.
● Delete Fabric- You can delete all the fabrics associated with the monitoring domain of the selected Fabric.

 

Filter

Filters the monitoring domain based on the list view options that are configured:

● Tunnel MTU
● Acquisition Method
● Centralised Connection
● Management Subnet

You can view the filters applied on the top of the monitoring domain page as a button. You can remove the filters by closing the button.

Connections Domain

To view the connection related details for a monitoring domain, click the Connections tab.

The list view shows the following details:

■   Connections
■   Monitoring Domain
■   Status
■   Fabric Nodes
■   User Name
■   Region

Fabric

To view the fabric related details for a monitoring domain, click the Fabric tab.

The list view shows the following details:

■   Connections
■   Monitoring Domain
■   Fabric Nodes
■   Type
■   Management IP
■   Version
■   Status - Click to view the upgrade status for a monitoring domain.
■   Security groups

G-vTAP Agents

To view all the G-vTAP agents associated with the available monitoring domains click the G-vTAP Agents tab.

The list view shows the following details:

■   Monitoring Domain
■   IP address
■   Registration time
■   Last hearbeat time
■   Agent mode
■   Status

Refer to Configure the OpenStack Settings, for information regarding Settings.