Gigamon Visibility Approaches for a Multi-Tenant Solution on Azure Cloud (5.16)

Introduction

The cloud journey in many large enterprises may have started with simultaneous Cloud deployments across various business units or different cloud accounts or tenants within the same cost center. Over time, enterprises prefer to converge these independent deployments for effective and easy roll out of enterprise tools and policies. This is not an easy task with large deployments.

Gigamon Cloud Suite has the Deep Visibility advantage that provides in-depth visibility data to the security and analytic tools from multiple Cloud accounts. By leveraging Gigamon Cloud Suite, customers can reduce the operations cost and administrative overhead required to maintain separate tools for each account and also receive holistic insight into the data which is crucial especially in security installations.

In this GVD, we explain how FM manages multiple Azure accounts and shares Gigamon Fabric nodes between them for obtaining visibility on the Cloud.

We also cover a GVD for similar use case on AWS, kindly refer Deploying GigaVUE Cloud Suite Across Multiple Accounts On AWS Cloud 5.16 for the steps to achieve the same on AWS Cloud.

Design Topology

Design Overview

This design illustrates deploying Gigamon Cloud Suite in an enterprise to monitor the target VMs located across two tenants viz., Sales tenant and Production tenant. The visibility tenant illustrates deployment of Gigamon fabric nodes and visibility traffic processing. The tool tenant illustrates Wireshark tool which receives the processed monitored traffic from V-Series. VNET peering was enabled between the tenants so that the monitored traffic could be forwarded across application and visibility tenants.

This design presumes monitoring all the target VMs. Hence, the V Series node(s) would be configured to pass all IPv4 traffic. However, you can choose to monitor specific target VMs either by configuring filtering rules to match the IP address of specific hosts or interfaces or by configuring the inclusion or exclusion maps (refer to the Deployment Steps section)

To learn more about this solution, read complete details on the Gigamon Community: Gigamon Visibility Approaches For A Multi-Tenant Solution On Azure Cloud 5.16