Create a Monitoring Domain

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

GigaVUE-FM provides you the flexibility to monitor 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. Click Check Permissions and validate whether you have the required permissions.
  4. 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:

    ■  UCT-V: UCT-Vs are deployed on your VMs to acquire the traffic and forward the acquired traffic to the GigaVUE V Series nodes. If you select UCT-V as the tapping method, you must configure the UCT-V Controller to communicate to the UCT-Vs from GigaVUE-FM.
    You can also configure the UCT-V Controller and UCT-Vs from your own orchestrator. Refer to Configure GigaVUE Fabric Components using AWS Orchestrator 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 UCT-Vs and UCT-V 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 for detailed information.
    • UCT-V 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 (AWS) 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 UCT-Vs and UCT-V Controllers. The user is responsible for creating this tunnel feed and pointing it to the GigaVUE V Series node(s).

    Note:  When using Application Metadata Exporter (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 UCT-V to the GigaVUE V Series node.

    The default value is 8951.

    When using IPv4 tunnels, the maximum MTU value is 8951. The UCT-V tunnel MTU should be 50 bytes less than the agent's destination interface MTU size.

    When using IPv6 tunnels, the maximum MTU value is 8931. The UCT-V tunnel MTU should be 70 bytes less than the agent's destination interface MTU size.

    Use FM to Launch Fabric

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

    Enable IPv6 Preference

    (This appears only when Use FM to Launch Fabric is disabled and Traffic Acquisition Method is UCT-V)

    Enable this option to create IPv6 tunnels between UCT-V and the GigaVUE V Series Nodes.

    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

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

Related links:

Configure GigaVUE Fabric Components in GigaVUE-FM