Deployment Options for GigaVUE Cloud Suite for Azure
This section provides a detailed information on the multiple ways in which GigaVUE Cloud Suite for Azure can be configured to provide visibility for physical and virtual traffic. There are three different ways in which GigaVUE Cloud Suite for Azure can be configured based on the traffic acquisition method and the method in which you want to deploy fabric components. Refer to the Before You Begin section for prerequisites that are required to be configured. For more detailed information and the work flow refer the following topics:
Deploy GigaVUE Fabric Components using Azure
GigaVUE‑FM allows you to use Azure as an orchestrator to deploy GigaVUE fabric nodes and then use GigaVUE-FM to configure the advanced features supported by these nodes. Refer the following table for the step-by-step instructions.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Obtain GigaVUE-FM Image |
|
|
2 |
Install GigaVUE-FM on Azure
|
|
|
3 |
Check and provide permissions and privileges |
|
|
4 |
Install UCT-V Agents Note: When using Azure as your orchestration system you can only use G-TAP Agents. |
For Linux: Linux UCT-V Installation For Windows: Windows UCT-V Installation |
|
5 |
Create Azure Credentials to monitor workloads across multiple Azure subscriptions |
|
|
6 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is disabled. |
|
|
7 |
Configure GigaVUE Fabric Components Note: Select UCT-V as the Traffic Acquisition Method. |
|
|
8 |
Create Monitoring session |
|
|
9 |
Add Applications to the Monitoring Session |
|
|
10 |
Deploy Monitoring Session |
|
|
11 |
View Monitoring Session Statistics |
Deploy GigaVUE Fabric Components using GigaVUE‑FM
You can deploy GigaVUE fabric components using GigaVUE‑FM using one of the following two traffic acquisition methods:
Traffic Acquisition Method as UCT-V
Follow instruction in the below table, if you wish to use UCT-V as your traffic acquisition method. When using UCT-V the traffic from the Virtual Machines are acquired using the UCT-V and it is sent to the GigaVUE V Series Nodes.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Obtain GigaVUE-FM Image |
|
|
2 |
Install GigaVUE-FM on Azure
|
|
|
3 |
Check and provide permissions and privileges |
|
|
4 |
Install UCT-V Agents |
For Linux: Linux UCT-V Installation For Windows: Windows UCT-V Installation |
|
5 |
Create Azure Credentials to monitor workloads across multiple Azure subscriptions |
|
|
6 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is enabled. |
|
|
7 |
Configure GigaVUE Fabric Components Note: Select UCT-V as the Traffic Acquisition Method. |
|
|
8 |
Create Monitoring session |
|
|
9 |
Add Applications to the Monitoring Session |
|
|
10 |
Deploy Monitoring Session |
|
|
11 |
View Monitoring Session Statistics |
Traffic Acquisition Method as Customer Orchestrated Source
Follow instruction in the below table if you wish to use Customer Orchestrated Source as your traffic acquisition method. In this case you can use tunnels as a source where the traffic is directly tunneled to V Series nodes without deploying UCT-V or UCT-V controllers.
| Step No | Task | Refer the following topics |
|---|---|---|
|
1 |
Obtain GigaVUE-FM Image |
|
|
2 |
Install GigaVUE-FM on Azure |
|
|
3 |
Check and provide permissions and privileges |
|
|
2 |
Create a Monitoring Domain Note: Ensure that the Use FM to Launch Fabric toggle button is enabled. |
|
|
3 |
Configure GigaVUE Fabric Components Note: Select Customer Orchestrated Source as the Traffic Acquisition Method. |
|
|
4 |
Create Monitoring session |
|
|
5 |
Create Ingress and Egress Tunnel Endpoints |
|
|
6 |
Add Applications to the Monitoring Session |
|
|
7 |
Deploy Monitoring Session |
|
|
8 |
View Monitoring Session Statistics |
