Connect to Azure

After creating a environment create a connection between the Azure and GigaVUE‑FM. Refer to the following step given below for detailed information on how to create a new connection.

(missing or bad snippet)

To connect to Azure, select or enter the following details:

Field

Description

Name

Name used to identify the connection.

Credential

Select your credentials from the drop-down menu. Refer Create Credentials for detailed information on how to create credentials.

Subscription ID

Select the subscription ID.

Region Name

The Azure region for the connection. For example, East Asia.

Resource Groups

The Resource Groups created in Azure for communication between the controllers, nodes, and GigaVUE-FM. A Resource Group must contain the VMs that needs to be monitored.

Traffic Acquisition Method

Select a Tapping method. The available options are:

● UCT-V: If you select UCT-V as the tapping method, you must configure the UCT-V Controller to monitor the UCT-Vs.
● Tunnel: If you use select Tunnel as the tapping method, you can select the tunnel as a source where the traffic is directly tunneled to V Series nodes without deploying UCT-Vs or UCT-V Controllers.
MTU

The Maximum Transmission Unit (MTU) is the maximum size of each packet that the tunnel endpoint can carry.

Note:  The default MTU is 1450. You can edit the MTU value according to your requirements. The valid range is between 1450 to 9000.

In the Azure Virtual Node Deployment page, select or enter the following details and click Save:

Field

Description

Centralized Virtual Network

Alias of the centralized VNet in which the UCT-V Controllers, V Series Proxies, and the GigaVUE V Series nodes are launched.

Authentication Type

Select SSH Public Key as the Authentication Type to connect with the Centralized VNet.

SSH Public Key

The SSH public key for the GigaVUE fabric nodes.

Security Groups

The security group created for the GigaVUE fabric nodes.

Configure a V Series Proxy (optional)

Enable the Configure a V Series Proxy toggle button if you wish to deploy V Series nodes using a proxy.

Enable Custom Certificates

Enable this option to validate the custom certificate during SSL Communication. GigaVUE-FM validates the Custom certificate with the trust store. If the certificate is not available in Trust Store, communication does not happen, and an handshake error occurs.

Note:  If the certificate expires after the successful deployment of the fabric components, then the fabric components moves to failed state.

Certificate

Select the custom certificate from the drop-down menu. You can also upload the custom certificate for GigaVUE V Series Nodes, GigaVUE V Series Proxy, and UCT-V Controllers. For more detailed information, refer to Install Custom Certificate.

In the UCT-V Controller section, select or enter the following details:

Field

Description

Controller Version(s)

The UCT-V Controller version you configure must always be the same as the UCT-Vs’ version number deployed in the VM machines.

If there are multiple versions of UCT-Vs deployed in the VM machines, then you must configure multiple versions of UCT-V Controllers that matches the version numbers of the UCT-Vs.

Note:  If there is a version mismatch between UCT-V Controllers and UCT-Vs, GigaVUE-FM cannot detect the agents in the instances.

To add UCT-V Controllers:

a. Under Controller Versions, click Add.
b. From the Image drop-down list, select a UCT-V Controller image that matches with the version number of UCT-Vs installed in the instances.
c. From the Size drop-down list, select a size for the UCT-V Controller. The default size is Standard_B1s.
d. In Number of Instances, specify the number of UCT-V Controllers to launch. The minimum number you can specify is 1.

Management Subnet

IP Address Type: Select one of the following IP address types:

■  Select Private if you want to assign an IP address that is not reachable over Internet. You can use private IP address for communication between the UCT-V Controller instances and GigaVUE-FM instances in the same network.
■  Select Public if you want the IP address to be assigned from Azure’s pool of public IP address. The public IP address gets changed every time the instance is stopped and restarted. On selecting Public IP address type, you must select all the required Public IPs.

Subnet: Select a management subnet for UCT-V Controller. The subnet that is used for communication between the UCT-V Controllers and the UCT-Vs, as well as to communicate with GigaVUE-FM.

Every fabric node (both controllers and the nodes) need a way to talk to each other and GigaVUE-FM. So, they should share at least one management subnet.

Note:  Some instance types are supported in Azure platform. Refer to Microsoft Azure documentation to learn on supported instance types.

Additional Subnets

(Optional) If there are UCT-Vs on subnets that are not IP routable from the management subnet, additional subnets must be specified so that the UCT-V Controller can communicate with all the UCT-Vs.

Click Add to specify additional data subnets, if needed. Also, make sure that you specify a list of security groups for each additional subnet.

Tags

(Optional) The key name and value that helps to identify the UCT-V Controller instances in your Azure environment. For example, you might have UCT-V Controllers deployed in many regions. To distinguish these UCT-V Controllers based on the regions, you can provide a name that is easy to identify such as us-west-2-uctv-controllers. To add a tag:

a. Click Add.
b. In the Key field, enter the key. For example, enter Name.
c. In the Value field, enter the key value. For example, us-west-2-uctv-controllers.

Agent Tunnel Type

The type of tunnel used for sending the traffic from UCT-Vs to GigaVUE V Series nodes. The options are GRE, VXLAN, and Secure tunnels (TLS-PCAPNG).

Agent Tunnel CA

The Certificate Authority (CA) that should be used in the UCT-V Controller for connecting the tunnel.

Note:  In a connection, you can configure multiple versions of a UCT-V Controller and you can only configure one version of a V Series Proxy.

In the V Series Proxy section, select or enter the values for the fields as described in the previous UCT-V Controller configuration table. The fields of the V Series Proxy configuration are similar to UCT-V Controller configuration.

In the V Series Node section, select or enter the following details:

Fields

Description

Image

From the Image drop-down list, select a V Series node image.

Size

From the Size down-down list, select a size for the V Series node. The default size for V Series configuration is Standard_D4s_v4.

IP Address Type

Select one of the following IP address types:

■  Select Private if you want to assign an IP address that is not reachable over Internet. You can use private IP address for communication between the V Series node instances and GigaVUE-FM instances in the same network.
■  Select Public if you want the IP address to be assigned from Azure’s pool of public IP address. On selecting Public IP address type, you must select the number of Public IPs defined in the Maximum Instance.

Management Subnet

Subnet: Select a management subnet for V Series node. The subnet that is used for communication between the UCT-Vs and the V Series nodes, as well as to communicate with GigaVUE-FM.

Every fabric node (both controllers and the nodes) needs a way to talk to each other and GigaVUE-FM. So, they should share at least one management subnet.

Data Subnets

The subnet that receives the mirrored VXLAN tunnel traffic from the UCT-Vs.

Select a Subnet and the respective Security Groups. Click Add to add additional data subnets.

Note:  Using the Tool Subnet checkbox you can indicate the subnets to be used by the V Series node to egress the aggregated/manipulated traffic to the tools.

Tag(s)

(Optional) The key name and value that helps to identify the V Series node instances in your Azure environment. For example, you might have V Series node deployed in many regions. To distinguish these V Series node based on the regions, you can provide a name that is easy to identify. To add a tag:

a. Click Add.
b. In the Key field, enter the key. For example, enter Name.
c. In the Value field, enter the key value.

Use the following buttons to manage your Azure connections :

Button

Description

CreateUse to create new connection.
Actions

Provides the following options:

  • Edit Connection - Use to edit a connection. You can also use this option to deploy your node after creating the connection.
  • Edit Node - If you have already deployed your node, then use this option to edit your node. You can also use this option to add more nodes into your existing connection.
  • Delete Connection - Use to delete a connection.
  • Delete Node - Use to delete a node.
  • Force Delete - This option is enabled when an upgrade fails due to infrastructure issues. Use this option to force delete the connection.
  • Upgrade Fabric - Use to upgrade your fabric components.
Refresh InventoryUse to refresh the selected connection.
ExportUse to export the details from the Connections page into an XLS or a CSV file.

To create Application Intelligence sessions, refer to Application Intelligence Session.