Create Monitoring Domain

To create a monitoring domain in Third Party Orchestration:

  1. Go to Inventory > VIRTUAL > Third Party Orchestration, and then click Monitoring Domain. The Monitoring Domain page appears.
  2. In the Monitoring Domain page, click New. The Monitoring Domain Configuration page appears.

  3. Select or enter appropriate information as described in the following table:

    Field

    Description

    Monitoring Domain

    An alias used to identify the monitoring domain. A monitoring domain consists of set of connections.

    Connection Alias

    An alias used to identify the connection.

    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. The default MTU value is 1450.
    ● Customer Orchestrated Source: If you select the Customer Orchestrated Source option, the mirrored, tunneled or the raw 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.
    Uniform Traffic Policy
    (When Traffic Acquisition Method is Customer Orchestrated Source)

    Enable this option if you wish to use the same monitoring session configuration for the the V Series Node deployed under this monitoring domain. Enable this check box when using packet mirroring configuration for GCP.

    Note:  Once the monitoring session is deployed for the monitoring domain you cannot enable or disable this option.

    Traffic Acquisition Tunnel MTU

    (When Traffic Acquisition Method is UCT-V)

    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 MTU values for the respective platforms when using IPv4 tunnels:

    AWS - 8950

    Azure - 1450

    OpenStack - 1450

    Nutanix - 1250

    When using IPv4 tunnels, the MTU must be 50 bytes less than the native MTU of the respective platform.

    The MTU values for the respective platforms when using IPv6 tunnels:

    AWS - 8930

    Azure - 1430

    OpenStack - 1430

    Nutanix - 1230

    When using IPv6 tunnels, the MTU must be 70 bytes less than the native MTU of the respective platform.

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