Deploying GigaVUE Cloud Suite for Azure using Customer Orchestration (5.14)

Introduction

GigaVUE Cloud Suite is a scalable network traffic visibility solution that acquires, aggregates, optimizes, and distributes selected traffic to the security and monitoring tools. This solution optimizes the bandwidth to the tools and thus, minimizes compute cycles resulting in better performance and fewer tools. The solution seamlessly integrates with Azure APIs and deploys visibility tiers in all VNets for aggregating and optimizing the traffic before monitoring. With Gigamon Cloud Suite, organizations can extend their security posture to Azure and ensure that the cloud environment is available, reliable, and scalable along with compliance. The current version of the solution (v5.14) enables customer orchestration deployment wherein, GigavUE-FM as well as all other visibility fabric nodes can be launched/controlled  by the customer-owned cloud orchestration mechanism (Terraform, Ansible, or any other scripting mechanism of customers' pick).

In this GVD, we will discuss how GigaVUE Cloud Suite can be deployed in Azure using manual orchestration by the customer. In this deployment scenario, GigaVUE Cloud Suite is built by manually launching GigaVUE-FM, G-vTAP Controllers, V Series Proxy, and V Series node first. When G-vTAP is installed in the target workloads, registration configuration is done manually in GigaVUE-FM and all other fabric nodes as the final step of customer orchestration. All these manual operations can be automated later by using the customer's orchestration mechanism. This GVD illustrates the Gigamon Cloud Suite's capability to leverage the customer-orchestrated monitoring domain/session to acquire, optimize, and distribute traffic to security tools within Azure (there is no need for GigaVUE-FM to launch fabric components in order to build up a monitoring domain/session). This allows the analytics and threat management capabilities from the customer side to proactively prioritize, mitigate, and hunt threats across the enterprise. 

NOTE: Please check with your Gigamon Sales contact or Gigamon Support for more information regarding the support for the cloud/virtualization platform that you are considering.

Design Topology

Design Overview

The architectural design for this solution displays an Azure environment being deployed with the Gigamon Cloud Suite. All fabric components in the visibility tier are launched via Azure portal manually instead of via GigaVUE-FM automatically.

Components

GigaVUE-Fabric Manager (GigaVUE-FM): Provides centralized orchestration of the resources and management.

G-vTAP Controllers: Small footprint VM(s), which act as the control plane proxy to manage the GvTAP agents in the environment.

G-vTAPs: Light-weight agents deployed on each VM for mirroring traffic to the V Series Node.

GigaVUE V Series Proxy: Similar to GvTAP controllers, they act as the control plane proxy to manage the V Series nodes in the environment (optional for deployment).

GigaVUE V Series Nodes: Aggregates, optimizes, and distributes the traffic for monitoring.

GigaVUE-Fabric Manager (GigaVUE-FM) can be deployed inside/outside the Azure environment. Only the fabric nodes (GvTap Controller, V-Series proxy and V-Series node) need to be deployed in Azure.

To learn more about this solution, read complete details on the Gigamon Community: Deploying GigaVUE Cloud Suite for Azure using Customer Orchestration 5.14.